SourceVault Team
The Gateway across every repository and every agent
Starter and Pro put the Gateway in front of one engineer's agents. Team rolls it out across the whole team: every repository, every agent, one policy, with a guided setup and support for the term.
Beyond Pro
Every license already carries the Gateway. What a Team license changes is the shape of the rollout.
Unlimited repositories
No source cap. Index every repository and local folder the team works in, including monorepos, and ask across all of them with Multi-repo Ask.
One policy for the whole team
The access policy, secret redaction, and audit chain apply to every surface the team uses: dashboard, MCP clients, the Hermes plugin, and the signed API. Security-focused file exclusions are worked out with you during onboarding.
Named agents, attributed access
Each agent gets its own scoped token, bound to the surfaces and repositories it may reach. The audit chain records which agent read what, and policy rules can be scoped per agent.
Updates and support for the term
Every release during the term is included, and Team support (the Priority Support service level) comes with the license rather than as an add-on.
Guided setup
An onboarding session and a maintenance runbook written for your deployment: where the stack runs, how models are served, how new repositories and agents are added.
A key that states the deal
The license key records the seat count and the term, verifies offline on every install, and never phones home. Procurement gets a plain invoice with the terms in the memo.
Deployment
Most teams run one shared stack on a server they control, with Docker Compose. The engine, the index, and the dashboard live on that box; teammates connect through the browser from any OS, agents on the server host connect over MCP, and tooling elsewhere on the network uses the signed API, each under its own named agent token. Models are served by Ollama on the same box or a GPU host you point it at. Nothing leaves your network.
- Install covers the one-command install for a single machine and the Compose deployment for a shared one.
- Settings lists every environment variable, including the per-surface secrets a shared deployment should set.
- Air-gapped covers environments with no outbound connectivity, which are an Enterprise engagement with the offline bundle.
- Trust & security is written for the reviewer who has to sign this off.
Pricing
| Term | Annual. One invoice per term, paid by bank transfer or card through Stripe, net 30. Nothing auto-renews or auto-charges. |
|---|---|
| Price | Per seat, from $15,000 a year. The quote depends on seats, repository count, and the rollout you need. |
| A seat | A person who uses SourceVault: through the dashboard, an MCP client, or the Hermes plugin. Agents are not seats; they run under the people who operate them, with their own named tokens. |
| Machines | Unlimited. The same key activates every install the team runs. |
| Renewal | A new invoice and a new key before the term ends. Seats can change at renewal. |
| If a term lapses | The install falls back to the free tier: the engine keeps working on one repository and the Gateway locks until a new key is entered. Nothing indexed is lost, and nothing stops abruptly. |
Starter and Pro remain flat one-time purchases for individuals and small teams; see the pricing grid and the billing & refund policy.
In development for Team
The work in progress is the part a larger rollout asks for first:
- An admin role for today's operator and a member role that can search, read, and ask but not change policy or settings.
- Single sign-on over OIDC against your identity provider, mapped onto those roles.
- Central policy: one install publishes the rule set and the others pull it, so a team runs one policy rather than one per machine.
- A Helm chart beside the Compose deployment, for teams that run on Kubernetes.
These ship as releases inside your term, so a Team license bought now includes them when they land. If you want to shape them, say so when you write: we are working with a small number of design partners this quarter.
Questions teams ask
We bought Pro. Can we move to Team?
Yes. Start on Pro, and when the team outgrows it, write to us with your Pro key; the first Team invoice is scoped to your rollout with that purchase in mind. Nothing is re-indexed and no settings are lost: the new key is pasted over the old one.
Does Team require a server?
No, but it is the usual shape. A shared stack means the models and the index live on one box and every teammate gets the same answers from the same policy. Team also works as individual installs, each activated with the same key.
How are seats counted?
Seats are a contract term, written on the invoice and recorded in the key, and shown on the plan card in the dashboard. They are not enforced by phone-home, because the product has none; per-user roles will make the count visible in the product itself.
Is there a trial for Team?
The free install is the trial: the engine runs free on one repository, with the Gateway on that repository for 7 days, and that is the same governed path a Team license runs across everything. Put it on a real repository, then write to us about the rollout.
What does Team support cover?
The Priority Support service level for the whole term: a committed response time on email, tuning help, a reindex strategy when models are upgraded, and the onboarding session. Security disclosures follow the disclosure process regardless of tier.
Start with Team
Write with the team size, the number of repositories, your git host, and whether the environment is air-gapped. You will get a quote and a proposed rollout, not a sales call.