Billing
Proposed billing configuration; the Billing surface is unavailable in this release
Keva's current plans contain a proposed resolution-based launch model. The Billing surface is unavailable in this release: no Settings > Billing tab is offered. The billing API family is not available under the design-partner release policy; requests in the /api/billing* family do not activate checkout, portal, or billing mutations.
This page documents proposed future work, not an active billing surface, entitlement, checkout flow, portal, or invoice service. Configured provider, deployment, live product, and customer-use checks remain open.
Proposed Launch Configuration
The proposed model uses monthly resolution allowances and overage rates. It is planning configuration only, not an active billing lifecycle or a claim that resolution consumption is currently measured.
| Plan | Proposed Monthly Price | Proposed Resolution Allowance | Proposed Overage Rate |
|---|---|---|---|
| Starter | $79 | 200 | $0.50/resolution |
| Growth | $199 | 1,000 | $0.40/resolution |
| Scale | $499 | 5,000 | $0.30/resolution |
| Enterprise | Custom | Unlimited | Custom |
What Counts as a Resolution?
The canonical billable-resolution definition is not active. The design proposes fields for AI-resolved and customer-confirmed outcomes, but nothing in the live product currently establishes resolution consumption, overage quantities, or charges. Ticket status, a final reply, elapsed time, or customer feedback must not be treated as a billable event until one durable definition and reconciliation lifecycle are approved and confirmed.
Current Release Boundary
No current product surface offers billing diagnosis, checkout, trials, subscription changes, resolution charging, portal access, invoice access, or billing mutations. Creating an account does not start checkout, a paid subscription, resolution metering, or a trial.
Future Work Boundary
The proposed plans, prices, allowances, overage rates, and resolution definition are not active billing entitlements or metering. A future release must first prove canonical measurement, ordered provider reconciliation, configured custody, and audit evidence, followed by deployment, product, and customer-use checks. Until that work is complete, the billing surface and billing API family are not available.