On-premise
ArchGraph runs with no identity provider, no gateway and no outbound dependency. Requests resolve to a single local identity, the MCP endpoints are served by the API directly, and an air-gapped host is a supported configuration rather than a workaround.
The complete operator path — the environment file, declaring your code host and your repositories, reading the install check, how refreshing works without inbound webhooks, and what to do when something is wrong — lives with the code it describes:
→ docs/ON_PREM.md in archgraph-api
It is kept there rather than repeated here on purpose. Every number, every environment variable and every YAML example in that document is bound to the code by a test, so a stale line fails CI rather than failing your install. A copy on this site would have no such gate, and a copy that drifts is worse than a link.
The compose file, the sizing profiles and the preflight script are in archgraph-infra.
How it differs from the hosted product
| Hosted | On-premise | |
|---|---|---|
| Identity | Clerk | A single local identity; no provider contacted |
| MCP endpoint | The gateway at mcp.archgraph.dev | The API itself, on your network |
| Authentication on MCP | Bearer token, plan-tiered | None — the network is the control |
| Outbound network | Required | Optional (ARCHGRAPH_OFFLINE=1) |
| Tool set | Tiered by plan | All of them |
The admin surface has no authentication of its own. Restrict it at the reverse proxy before exposing the host.