Launch
A clear starting point for your first production workload.
/ month
$49 base · 1M included
Then $6 / million requests
- Model routing
- Usage visibility
- One shared workspace
- Built for small teams
PRICING
A clear model
for the work ahead.
Start with a shared foundation. Plan around actual request volume, then choose a deployment model that fits your operating needs.
A plan for your next move
Built around your workload.
Set your monthly request volume.
Find the room you need to grow.
requests / month
0M0.5M increments100M
Scale
Room to growMore room for the systems and teams moving with you.
/ month
$149 base · 10M included
Then $4 / million requests
- Everything in Launch
- Multiple environments
- Routing policies
- Team workflow controls
Enterprise
Shape a plan around your architecture and workload.
Let's talk.
Custom quote
Scoped to your requirements
- Workload assessment
- Architecture planning
- Deployment requirements review
- A tailored commercial proposal
Excludes taxes and model-provider charges.
SHARED / FROM $49 PER MONTH
Start considered.
Grow deliberately.
A shared workspace, model routing, request visibility and a familiar API surface. One million requests are included in the monthly base. Additional requests are $6 per million.
Model-provider charges are separate. The estimator shows platform fees only, so you can compare infrastructure cost without hiding what the underlying models cost.
DEDICATED / TALK TO US
An environment
shaped around you.
For teams that need dedicated deployment, tailored access boundaries or an agreed support model. Scope depends on workload, environment and operational requirements.
Bring expected volume, regions, model choices and security requirements. We can use those inputs to define the architecture and a commercial proposal together.
BEFORE YOU START
The practical details.
What counts as a request? A call received by the platform endpoint. Agree how retries, failed requests and batch workloads are counted before enabling a paid production environment.
Can we bring our own model-provider accounts? The architecture supports provider-managed credentials. Review key ownership, access and billing responsibilities during setup.
Can we change the deployment later? Plan the migration around routing policies, credentials and observability exports. A dedicated environment should not require a new application-level API contract.