Tenancy
Every subsidiary, isolated by the database itself.
Row-level security on every table. Workspaces and environments per tenant. One installation serves the whole group without a shared row anywhere.
On-prem AI control plane
One install.
Every subsidiary.
Axiplane runs agents, models, budgets and audit for every tenant of your group from one deployment on your own servers. Your models. Your data. Your rules.
Budgets
Spend is authorised before the first token.
Budgets per tenant, agent and period. Soft warnings, hard stops and immutable price versions. Nothing runs that the ledger has not cleared.
Model gateway
Any model. No vendor in the box.
Cloud APIs, local vLLM or a sovereign model behind one OpenAI-compatible endpoint. Each tenant chooses; switching is a configuration change.
Agents and workflows
Agents and graph workflows on LangGraph.
Versioned agents with immutable published releases, handoffs between agents, and human approval steps where the process needs them.
Connectors and knowledge
Your tools and documents, within reach.
Slack, Teams, REST and OpenAPI tools, MCP servers and pgvector knowledge bases, bound per tenant with scoped credentials.
Telemetry and audit
Every token and every action on record.
ClickHouse telemetry, audit events and usage by tenant, agent and model. Grafana dashboards ship with the stack.
Holding, subsidiaries and teams share one installation and nothing else.
Finance sees spend before the model does, per tenant and per agent.
Models, data and keys stay on infrastructure you already operate.
Budgets
Spend is authorised before the first token, not reconciled after the invoice.
Every tenant, agent and period carries a budget. Axiplane prices each run against an immutable price version, warns early and refuses when the limit is reached. Finance sees the number before the model does.
Retail Ops · October · example
€0
Within budget
€080%€2,400 limit
- Period
- Monthly · resets 1 November
- Scope
- Tenant → agent → run
- Price version
- v7 · published 2 October · immutable
- At the limit
- Requests refused · nothing billed
Integrate
A handful of lines. Nothing new to learn.
Your applications keep the SDKs they already use. Axiplane sits behind an OpenAI-compatible endpoint, a REST API and MCP, so onboarding a system is a configuration change rather than a project.
- Base URL
- Point an OpenAI-compatible client at your Axiplane host. Tenant, agent and budget resolve from the key, so the application code stays untouched.
- SDK
- One call from the TypeScript SDK or any HTTP client runs an agent with the tenant's models, tools and policies applied.
- MCP
- Register Axiplane as an MCP server in the tools your teams already use. Every call is scoped, logged and priced.
# nothing else changes in your codetenant retail-ops · agent procurement-assistant v4 · budget 61% · price v7Deploy
Runs where your data already lives.
One Docker Compose stack on your servers or in your cloud account. Databases, storage and secrets management are part of the install, so the first pilot does not start with a procurement round.
PostgreSQL 17pgvectorRow-level securityClickHouseGarage object storageOpenBao TransitValkeyLangGraphOpenTelemetryGrafanaDocker ComposeOpenAI-compatible APIPostgreSQL 17pgvectorRow-level securityClickHouseGarage object storageOpenBao TransitValkeyLangGraphOpenTelemetryGrafanaDocker ComposeOpenAI-compatible API
In the box
- PostgreSQL 17 + pgvector
- Tenancy, catalog and vectors, with row-level security on every table.
- ClickHouse
- Telemetry and usage analytics per tenant, agent and model.
- Garage
- S3-compatible object storage for conversation content and files.
- OpenBao Transit
- Envelope encryption for provider keys, connector secrets and content.
- Valkey
- Queues and caches for the worker plane.
- LangGraph runtime
- Agents, workflows and checkpoints, versioned and immutable once published.
- Grafana + OpenTelemetry
- Dashboards and traces, included in the compose stack.
Stays with you
- Prompts and completions
- Kept out of the relational database by design and stored encrypted in your object store.
- Provider credentials
- Written through Transit, never to logs.
- Model traffic
- Leaves only towards the providers you configured, or nowhere at all.
- The control plane
- No SaaS dependency, no callbacks home, no vendor API in the critical path.
Questions
The questions a CTO and a CFO ask first.
Pilot
Run the pilot on your own servers.
One installation, one or two tenants, a defined use case. Budgets and audit on from day one. We set it up with your team and hand over the keys.