Email content

stigg4

July 2026 💚

Stigg 2.0, Under the Hood: Governance, the Credits Engine, and Metering at 1M+ Events/Second

Last month we announced Stigg 2.0. This issue goes under the hood on the pillars we delivered, with a technical deep dive on each: real-time usage control, double-entry ledger credits, and the metering pipeline underneath them. The through-line is the same across all three: usage decided at runtime, in the request path, before the cost is incurred, not after the invoice lands.

Introducing Governance: The First Milliseconds-Latency Usage Control Layer for AI

AI Usage Governance 4

For the first time, you can give your customers control over their own users' and agents' budget limits. Enforcement runs in the hot path, a decision engine that fires at the moment of truth, before the spend happens. No other platform does this. Read the deep dive to see how it works.

Read more >>

Credits Are a Financial System. We Built It For You, Enforced in the Request Path.

Credits 4

Bill on credits with confidence that every balance holds up, in real time. A credit balance isn't a counter, it's a financial system. Correct under concurrency, current in real time, auditable at close. The deep dive explains why real credits need a double-entry ledger, enforced in the request path before compute runs.

Read more >>

Usage Metering and BYOC: Where the Events Go, and Whose Infrastructure They Go Through

BYOC 3

Know your usage counts are correct after every retry, and keep your data exactly where you want it. Stiggs' metering is built for correctness at 1M+ events per second, and with BYOC the same architecture runs inside your own VPC. The deep dive answers the two questions every integration review asks: is the count still correct after a retry, and where does the data go?

Read more >>

What else has been going on in Stigg

Direct deduction from credit wallets

Synchronous deduction from usage events

Credit entitlement soft limits

Stigg set up using a single command

Stigg is the usage runtime for AI products. It controls what each customer, user, or agent can use: credits, usage limits, metering, and entitlements, enforced on every API call in real time. Stigg is a control layer that runs alongside your existing billing, and can be deployed in your own cloud (BYOC).