Skip to main content
Stigg is the usage runtime that decides what every customer, user, team, and agent is allowed to do, on every request, before it runs. It brings metering, entitlements, credits, and governance into a single enforcement layer, so usage is controlled on the call, not after the bill.
Get started with AIOne command connects your AI coding assistant to Stigg: sign-in, MCP server, and AI skills. Then build pricing, entitlements, and usage tracking in natural language.

Integrate into your codebase

Backend and frontend SDKs for Node, Python, Go, Ruby, Java, .NET, and more.

​
Where Stigg sits

Stigg runs in the request path, between your application and your business stack. Your application asks what a customer or agent wants to do. Stigg decides, in real time, what they are allowed to do. Billing, CRM, and the rest of your stack stay in sync, so Stigg works alongside the systems you already use instead of replacing them.
Your cloud
Your applicationevery request
SDK / Sidecarlocal cache
Access checks, under 10ms
Usage events, up to 1M/sec
Stigg usage runtime
Data plane
Metering pipeline
Credit engine
Entitlements and governance
Control plane
Catalog and provisioning
Workflows
Integrations
Usage and subscriptions, synced
Your business stack
BillingStripe, Zuora, Airwallex
CRMSalesforce, HubSpot
Webhooksnotifications

​
Capabilities

Four capabilities, each adoptable on its own. Contract management and invoicing is an optional add-on, and everything runs on Cloud, BYOC, or BYODB.
Stigg usage runtime
MeteringReal-time metering at 1M+ events per second. Every token, inference call, and agent action, captured and aggregated in the request. Run it in your own cloud for full data ownership.Learn more EntitlementsEntitlement logic lives outside your codebase. Ship a new model, tier, or feature in seconds, without touching a deployment.Learn more CreditsFinancial-grade credit infrastructure: wallets, ledgers, burn-downs, expiry rules, and priority consumption. Every edge case solved, without building it yourself.Learn more GovernanceSelf-serve spend controls, enterprise-ready. Budget caps per user, team, and agent, enforced at call time and configured by your customers, not your support team.Learn more
Optional add-onContract management and invoicingTermed enterprise contracts with commitments and custom pricing, provisioned and invoiced automatically.
Runs onCloudBYOCBYODB

​
The decision path

Every action is checked before it runs, whether it’s a model call, an API request, an agent task, or a premium feature. Stigg checks entitlement, credit balance, and budgets and limits. If all checks pass, access is granted and your application or agent performs the action. Once it completes, Stigg meters the usage, deducts credits, and attributes the cost. If any check fails, access is denied before any cost is incurred.
1makes a request
2EntitlementCredit balanceBudgets and limits
3model call, API request, or feature
4deduct credits, attribute cost
All checks pass: Access granted, the action runs, then its usage is metered
Any failed check: Access denied, before any cost is incurred

​
Cloud, BYOC, or BYODB

The same production APIs, wherever you run the access layer.
Fully hosted by Stigg, and the fastest path to production. The SDK or Sidecar caches entitlements in your cloud, and Stigg pushes updates to it in real time.
Your cloud
Your application
SDK / Sidecarlocal cache
Persistent cacheoptional
Events bucketoptional
Access checks, under 10ms
Usage events, up to 100k/sec via API
Bulk events, up to 1M/sec via object storage
Updates pushed in real time
Stigg’s cloud
Data plane
Edge CDN
Metering pipeline
Credit engine
Entitlements and governance
Control plane
Catalog, workflows, integrations