Stigg

Stigg builds infrastructure for engineering teams to control how customers, users, and agents consume software and AI services. It combines entitlements, usage metering, credits, and spend controls: an application can check whether a user has access to a feature and enough budget before an AI request runs. Its customers include Miro, PagerDuty, and Webflow, whose uses span AI credits, feature access, and monetization infrastructure.

Its credit system handles wallets, grants, deductions, expiration rules, and the order in which different credit balances are consumed. A double-entry ledger accounts for grants and deductions, while customers can see which actions spent their credits and what remains. Stigg also lets customers configure budget caps for users, teams, and agents, enforced when calls occur. Entitlement rules live outside the application codebase, allowing teams to change access to models, features, or tiers without deploying application changes.

Stigg works alongside an existing billing provider through bidirectional synchronization, separating usage and access controls from the billing system. Its August 18, 2026 acquisition of Received.ai expanded that scope into contract management and usage-based invoicing, announced in public beta, including automatic entitlement provisioning from signed contracts. Teams can use Stigg’s hosted API and SDKs or deploy it into their own cloud environment, managed by Stigg. Another deployment option uses the customer’s database and event queue, giving teams ownership of the underlying data layer.