Volume pricing
Committed monthly spend earns rates below the public catalog. Pricing is per model, so you are not paying for capacity you do not use.
Enterprise
Run every model through one contract
Teams adopt Openbase to stop maintaining five provider integrations, five sets of credentials and five invoices. The gateway becomes the single place where routing, spend and policy are decided.
What changes at scale
The parts you cannot get on the self-serve plan
Your own provider accounts
Bring your existing OpenAI, Anthropic or Google contracts and route through them. Openbase handles the failover and the accounting while the tokens bill to you.
Dedicated routing policy
Pin providers per model, set regional constraints, or require that certain workloads never fall back. Policy is configured per workspace rather than per request.
Support with a person on it
A shared channel, a named contact and response commitments that match how quickly your traffic actually moves.
Details
Questions procurement always asks
- Can we self-host?
- Yes. Openbase runs as a set of containers against Postgres and Redis, so it deploys into your own infrastructure. We help with the rollout and keep you on a supported version.
- What are the data guarantees?
- Prompts and completions are not retained. Only request metadata, the information needed to bill and debug, is stored. Retention windows can be shortened contractually.
- How does billing work at volume?
- Prepaid balances suit most teams, but invoiced monthly terms with net payment are available once spend is predictable.