Skip to main content
This page covers your own Stigg subscription. To learn how to model plans for your customers, see Plans.

​
Overview

Stigg offers four plans: Build, Pro, Scale, and BYOC. Each plan is measured by the following usage metrics:
  • Managed entities: the number of independent scopes that Stigg manages access or usage for.
  • Usage events: the number of usage events reported to Stigg for metering each month.
  • Ingestion rate limit: the number of usage events per second that Stigg accepts from your account.
For the allowances and prices of each plan, see Stigg’s pricing. To view your current plan and usage, or to change your plan, see Managing your Stigg subscription.
Only usage in your production environments counts toward your plan. Development and staging (non-production) environments don’t count.

​
Managed entities

A managed entity is anything in your product that Stigg independently manages access or usage for, such as a customer, workspace, team, user, or AI agent. You’re billed based on the number of entities Stigg manages, not the number of seats, subscriptions, features, or entitlements you configure.

​
How managed entities are counted

Each independent scope that Stigg manages counts as one managed entity:
  • Customer: a customer with an active subscription, entitlement, or credit wallet counts as one managed entity.
  • Resource: a resource under a customer with its own subscription, entitlement, or credit wallet counts as an additional managed entity.
  • Governance entity: a governance entity, such as a team, user, or agent, with its own limit, budget, or entitlement counts as an additional managed entity.

​
What doesn’t increase your managed entity count

  • Additional configuration: features, entitlements, subscriptions, and credit wallets don’t increase your count. For example, a customer with multiple subscriptions, 50 entitlements, and several credit wallets at the customer level still counts as one managed entity.
  • Non-production environments: only managed entities in your production environment count.

​
Reaching your managed entity limit

​
Usage events

A usage event is a single event reported to Stigg for metering, for example tokens consumed, an API request, or an AI action. Both raw events and calculated usage reports count as usage events. For more details on reporting usage, see Reporting raw events and Reporting calculated usage. Each plan includes a monthly allowance of usage events.

​
Exceeding your monthly usage event allowance

​
Ingestion rate limit

Your ingestion rate limit determines how many usage events per second Stigg accepts from your account. When you exceed your rate limit, Stigg returns a 429 Too Many Requests response. Events that receive this response can be retried, so they don’t need to be lost. For more details on retrying events, see Reporting raw events. If you regularly need more throughput, you can increase your capacity or move to BYOC.

​
Notifications

Stigg notifies you as you approach your managed entity and usage event allowances, and again when you reach them.