Pricing
Two line items, nothing else to add up
Put the fee beside the team it replaces, with your own numbers.
Cantora charges for launching and continuously operating one production Agent — not for seats, Tenants, or a stream of usage surprises.
2.3 is a coverage floor rather than a workload estimate: platform, integration, agent engineering, Evaluation operations, on-call, and security each need a share, and a rotation that answers at 2 a.m. needs several named people whatever the ticket volume.
Loaded at 1.4× for payroll taxes, benefits, equipment, and software, then charged for every month of the horizon — a platform team is staffed before the first agent is live and stays staffed after it.
This is arithmetic on your inputs, not a quote and not a forecast. It counts the platform team and the published floors only: it leaves out workflow implementation, data preparation, human review, and incident cost, which both columns carry and which usually move the answer more than the staffing line does. Ask for the full worksheet to run it properly against your own volume and outcome definition.
If the comparison is directionally useful, scope one workflow before you design the whole platform.
The two figures
Model and provider usage is inside the recurring fee. No usage bill, no token bill, and no provider line to reconcile.
It holds while the deployment stays inside its written operating envelope, which every proposal defines along with the monthly allowance, the alert thresholds, and the behavior at the limit.
What the two figures buy
Both are published floors. Custom work changes the written launch price; it is never calculated as a percentage of the recurring fee.
The envelope makes included usage honest
Every proposal fixes five things in writing before Live traffic begins.
- Expected monthly volume
- The included model-usage allowance
- Alert thresholds before the limit
- Pause, degrade, or approval behavior at the limit
- What triggers a new recurring scope
Past the envelope you get a new written scope, not a surprise invoice.
Easy to understand — and to leave
You can export the canonical Agent Configuration and version history, prompts, customer-owned Evaluations, eligible memories and Artifacts, and the integration inventory without live credentials.
Cantora keeps its hosted runtime, observability, connector infrastructure, rollout machinery, and platform source. Migration engineering is scoped separately.
No annual commitment. You stay because the runtime is useful, not because knowledge is trapped — and Cantora has to earn that every month.
Get started
Scope your first agent
Bring one bounded workflow, the systems it needs, and examples of a good answer. Cantora replies with the technically useful next step.