Managing usage and spending boundaries across multi-tenant or multi-user applications just got a whole lot more granular. We are excited to announce Resource-Level Credit Pools, allowing you to isolate credit balances, ledgers, and auto-recharge configurations for individual customer resources.

Previously, credit balances were managed at the global customer level. With this update, you can now provision distinct credit wallets for specific resources - such as individual workspaces, or even specific team members under a single customer account.

🆕 What’s new?

When a subscription is assigned to a specific customer resource, Stigg now automatically spins up an isolated, resource-specific credit pool.

Each resource-level credit pool operates as an independent wallet featuring its own:

• Dedicated Credit Grants: Award or sell credits that are strictly locked to a single resource.
• Isolated Credit Ledger & Usage History: Track exactly how, when, and where a specific resource is consuming its credit balance.
• Independent Auto-Recharge Configurations: Set up tailored auto-recharge rules that trigger top-ups only when a specific resource's balance runs low.

The Stigg app has also been updated to give you full visibility into your multi-resource architecture:

• Credits Tab: You can now filter your global credit views using the new Resource ID drop-down menu to view isolated ledgers.
• Subscription View: When viewing any resource-specific subscription, the UI will display the dedicated credit pool history and auto-recharge statuses directly inline.

⭐️ Why it matters

Modern SaaS products frequently require usage enforcement to happen below the billing account level. This is particularly critical for B2B applications offering team plans or usage-heavy developer platforms.

• Implement Per-User Credit Pools: You can now cleanly build a team topology where a corporate customer pays a single invoice, but each individual team member receives a dedicated, non-shareable credit pool for their personal usage enforcement.
• Prevent Resource Starvation: Ensure that a single noisy workspace or rogue API token cannot drain the entire credit balance of a parent customer account.

⚒️ Get started

Resource-level credit pools require no manual initialization - they're automatically generated whenever you provision a subscription and assign it to a specific resource by passing the resource ID.

Credits can be granted to a resource-specific credit pool by passing the resource ID. Similarly, credits can be consumed from a resource-specific credit pool by passing the resource ID when reporting usage events to Stigg.

🍿️ See it in action