Stigg
The Usage Runtime for AI Products
4.7•12 reviews•1.1K followers
The Usage Runtime for AI Products
4.7•12 reviews•1.1K followers
Stigg is the usage runtime for AI products: the real-time enforcement and governance layer between your app and your billing stack. It decides what every customer, user, team, and agent can do, the moment they try. Sub-millisecond credit checks, zero overdraft, enterprise governance, and modular BYOC. Metering, credits, entitlements, and governance in one runtime. Enforce in the request path instead of reconciling on the invoice. Free forever for AI startups.
This is the 2nd launch from Stigg. View more
Stigg 2.0
Launched this week
Stigg is the usage runtime for AI products: the real-time enforcement and governance layer between your app and your billing stack. It decides what every customer, user, team, and agent can do, the moment they try. Millisecond credit checks, zero overdraft, enterprise governance, and modular BYOC. Metering, credits, entitlements, and governance in one runtime. Enforce in the request path instead of reconciling on the invoice. Free forever for AI startups.
Free Options
Launch Team
How does the BYOC setup actually work in practice, does my billing data leave Stigg's infra at all or do you just push metering events into my own system?
how does this handle usage coming from multiple agents or services hitting the same entitlement at the same millisecond without one of them getting blocked unexpectedly
Congrats on the launch. I hand-rolled entitlements for my own two-plan SaaS last week: one feature flag and a couple of can_use_x? methods (super simple). I assume it ends in tears somewhere around plan number four. Curious where you see the crossover in practice. Is it plan count, team size, or the first customer who asks for a custom contract?
Tested it on a side project and the credit checks really do come back instantly, no extra round trip in front of my API. The entitlements view made it easy to flip a feature on for a test user without touching billing code.
Plugged it into a side project last night and was surprised how fast the entitlement checks land, basically no latency bump. The governance dashboard also made it obvious which test accounts were poking limits.
Love that it enforces in the request path instead of reconciling after the fact. The sub-millisecond credit checks actually feel invisible during testing, which is exactly what you want from this kind of layer.
Plugged the SDK in and the entitlement checks actually fire inside the request path, no more end-of-month reconciliation surprises. The credit burn updates feel instant too.