Team knowledge bases — sharing engineering corpora without losing control

Promote a folder into a billed, shared knowledge base with ghost or open citation modes. How Vevesh handles membership, Stripe billing, and retrieval policy.

Vevesh Team 6 min read

Individual project indexes are powerful. Team knowledge bases are how engineering organizations scale that power—shared standards libraries, methodology packs, and reference corpora that every member can query from chat without copying folders to a shared drive and hoping everyone syncs manually.

Vevesh KBs are first-class products: hosted storage, membership, billing, and retrieval policy—not a shared link duct-taped onto a folder sync.

What a knowledge base actually is

A KB is a promoted corpus with:

  • An owner and Stripe-backed subscription
  • Explicit members (email invite)
  • Extraction settings independent of any single project
  • A visibility mode in chat: sector picker for authorized users

Your underlying folder remains the ingestion source. Settings and membership live in Postgres—never scattered in ad-hoc config files inside the repo.

Ghost vs open disclosure

This is the policy knob serious teams ask about first:

Ghost mode — the KB participates in retrieval but resists casual citation exposure and probing. Useful for sensitive internal standards or pre-release methodology.

Open mode — citations are direct and listable, suitable when the KB is intentionally the canonical reference.

Switching modes is immediate—it changes retrieval and citation policy, not the stored vectors. No re-ingestion required.

Billing that matches usage

Hosting subscriptions cover the KB footprint. Server extraction and embed usage meter per engine—Express through Premium—so teams see cost aligned with document difficulty, not a flat “AI tax.”

Membership without account chaos

Owners invite by email. Members see the KB in their sector list. Project-level overrides (allowedGlobalRagIds) can restrict which KBs appear in a given project context—useful when the same engineer wears different hats on different jobs.

Governance patterns we see in preview

  1. Corporate standards KB — open mode, Structure engine, all engineers.
  2. Client deliverable archive — ghost mode, Premium on scans, limited members.
  3. R&D sandbox — local Express, owner-only until promoted.

Getting started

Knowledge bases are live in private preview. If your team already maintains a folder that should be queryable by twelve people tomorrow—not twelve duplicated copies—reach out for access.

Full platform comparison · More articles