Governance & enterprise
Budgets and quotas
Bound consumption at workspace and service-key level
Octoryn separates enterprise funding from runtime controls. Prepaid contract capacity or Stripe funding establishes capacity; Router budgets, quotas and rate limits decide whether a request may consume it.
Separate capacity from permission
A positive balance does not grant access to every model. Workspace policy, key scope, provider eligibility and budget state must all allow the request.
Set operational limits
Define limits around the ownership boundary that can respond to overruns.
- Workspace spend ceiling
- Product or service-key quota
- Request and token rate limits
- Alerts before hard exhaustion
Fund enterprise capacity
Use contract prepayment for committed enterprise capacity or the authenticated Stripe funding flow in Console. Bank-transfer top-ups and consumer referral balances are intentionally not part of Router.