Unlimited repositories,
an agreement, and no surprises.
SSO, a negotiated credit allowance, and support with an agreement behind it. Read from the same catalogue the product enforces, so this cannot disagree with what your organization is allowed to do.
- Unlimited repositories
- Unlimited agent keys
- 100 agent requests a second
Install it inside your own network
New on Enterprise. On request we deploy Docs Flowy on hardware you own and keep it upgraded there.
This is three containers and a Postgres database — no Kubernetes, no Redis, no managed service in the path of your documents — which is what makes an install on your hardware a term we can agree rather than a product we have to rewrite.
Nothing changes about how it reads a repository. The GitHub App stays read-only, nothing is ever cloned, and on your own install the encryption keys are yours and Ask reaches whichever model provider you configure, still off until somebody turns it on.
It is arranged in the agreement rather than switched on in settings, so the date is one we set with you.
apiFastAPI, reading your repositories over the wire.workerSync, polling and housekeeping, in its own process.consoleThe Next.js reader and every settings screen.postgresDocuments, status and audit trail. One store, no extensions.
- Install it on your infrastructure, behind your TLS terminator.
- Ship upgrades on a cadence you set, with the migration rehearsed first.
- Hand over the keys, the backups and the runbook with it.
Built, running, and in the product today
Everything in this section you could turn on this afternoon.
IP allowlist
Refuse every request from an address you did not name, reaching machine credentials as well as browsers. An API key is checked at the door before the request is dispatched.
Required GitHub sign-in
Withdraw documents from anybody without a GitHub identity, so reading follows an account your organization can see and revoke.
Audit log with a 365-day window
Every security and product change with who and when, written inside the same transaction as the change, filterable and exportable.
Agent keys at enterprise rate
Unlimited keys, each scoped to one project, each optionally carrying a minimum review state so an agent only ever sees documents somebody validated.
Session policy and revocation
Set session lifetime, see where members are signed in, and sign everybody out in one action.
Roles, teams and nothing implicit
Membership is the organization, access is the project. Joining hands out no documents, and a Guest never sees the project list at all.
What an agreement covers that the product does not yet do
Above the call to action rather than below it, because the worst way to learn any of this is after signing.
- SSO and SAML
- Part of the agreement and not part of the product today — the card exists in security settings and is not wired to an identity provider. If your rollout depends on it, the honest answer is a date we agree together, not a toggle you will find after signing.
- A negotiated credit allowance
- Every other plan sells a fixed monthly pool. Enterprise sets one per agreement, which is why no figure appears on the pricing page — a negotiated number published is a negotiated number nobody negotiates again.
- Support with terms behind it
- Response times and escalation written down rather than implied. Today that is a direct line to the people who built it, which is a real answer at this size and will need replacing at a larger one.
The four questions your reviewer will ask
Answered here so the first call is about whether this solves your problem, rather than about a questionnaire.
- Can it write to our repositories?
- No, and it cannot be configured to. The GitHub App is read-only, nothing is ever cloned, and no agent tool can reach a repository document — what an agent writes is an artifact, in a namespace the sync worker does not own, under a scope granted separately from reading.
- What security testing runs against it?
- Every change is scanned before it merges and again every week: ruff's flake8-bandit rules over the whole Python tree, pip-audit and pnpm audit against the dependency graphs, gitleaks across the entire git history rather than the tip, and Trivy against both container images for OS and language CVEs. The security page names what that does not cover, in the same detail.
- Where is data processed?
- On infrastructure we operate — our servers, our encryption keys, and no third-party processor anywhere in the path of your documents — or on your own servers, if the agreement says so. The one exception is Ask: document text reaches a model provider only for an organization that switched it on, it is off by default, and enabling it is written to the audit log.
- What happens to our documents if we leave?
- They were never ours. The markdown stays in your repositories; disconnecting stops us reading it and revoking the app makes it impossible.
Start on a paid plan today and talk about the rest.
Nothing about Enterprise is a prerequisite for using this. Connect a repository, put it in front of your team, and bring us the list of what your approval process needs.