> ## Documentation Index > Fetch the complete documentation index at: https://docs.stigg.io/llms.txt > Use this file to discover all available pages before exploring further. # Stigg plan limits and usage > [!NOTE] > > This page covers your own Stigg subscription. To learn how to model plans for your customers, see [Plans](https://docs.stigg.io/documentation/modeling-your-pricing-in-stigg/plans/plans.md). ## Overview Stigg offers four plans: **Build**, **Pro**, **Scale**, and **BYOC**. Each plan is measured by the following usage metrics: * **[Managed entities](#managed-entities):** the number of independent scopes that Stigg manages access or usage for. * **[Usage events](#usage-events):** the number of usage events reported to Stigg for metering each month. * **[Ingestion rate limit](#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](https://www.stigg.io/pricing). To view your current plan and usage, or to change your plan, see [Managing your Stigg subscription](https://docs.stigg.io/documentation/managing-your-account/billing/managing-your-subscription.md). > [!NOTE] > > Only usage in your [production environments](https://docs.stigg.io/documentation/managing-your-account/environments/index.md) 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](https://docs.stigg.io/guides/i-want-to/add-multiple-subscriptions.md) under a customer with its own subscription, entitlement, or credit wallet counts as an additional managed entity. * **Governance entity:** a [governance entity](https://docs.stigg.io/documentation/governance/core-concepts.md#entities), such as a team, user, or agent, with its own limit, budget, or entitlement counts as an additional managed entity. | Example | Managed entities | | - | - | | Customer with a subscription | 1 | | Customer with subscriptions on 3 different resources | 3 | | Customer with 1 subscription, 2 credit wallets, and 50 entitlements at the customer level | 1 | | Customer with 3 governed agents, each with its own credit budget | 4 | ### 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 | Plan | Behavior | | - | - | | Build | Once you reach your limit, you can't create additional managed entities until you upgrade. Enforcement for your existing managed entities continues uninterrupted. | | Pro | You can continue adding managed entities beyond your included allowance, and additional managed entities are billed as overage. Pro supports up to 100,000 managed entities. | | Scale | Additional managed entities are billed according to your contract. Scale supports up to 2,000,000 managed entities. For larger deployments, [contact us](mailto:support@stigg.io) about BYOC. | ## 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](https://docs.stigg.io/documentation/getting-usage-data-into-stigg/reporting-raw-events/index.md) and [Reporting calculated usage](https://docs.stigg.io/documentation/getting-usage-data-into-stigg/reporting-calculated-usage.md). Each plan includes a monthly allowance of usage events. ### Exceeding your monthly usage event allowance | Plan | Behavior | | - | - | | Build | Once you reach your allowance, Stigg stops accepting additional usage events until your allowance resets or you upgrade. | | Pro | Ingestion continues, and additional usage events are billed as overage. | | Scale | Ingestion continues, and additional usage is handled according to your contract. | ## 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](https://docs.stigg.io/documentation/getting-usage-data-into-stigg/reporting-raw-events/index.md). If you regularly need more throughput, you can increase your capacity or move to [BYOC](https://docs.stigg.io/documentation/high-availability-and-scale/byoc/overview.md). ## Notifications Stigg notifies you as you approach your managed entity and usage event allowances, and again when you reach them. ## Related topics - [Managing your Stigg subscription](https://docs.stigg.io/documentation/managing-your-account/billing/managing-your-subscription.md) - [Adding entitlements to plans](https://docs.stigg.io/documentation/modeling-your-pricing-in-stigg/plans/assigning-features-plans.md) - [Notifications and webhooks](https://docs.stigg.io/documentation/modeling-your-pricing-in-stigg/plans/overages/notifications.md) - [Metered features](https://docs.stigg.io/documentation/modeling-your-pricing-in-stigg/add-ons/assigning-features-to-add-ons/metered.md) - [Feature inspector](https://docs.stigg.io/documentation/rolling-out-pricing-changes-with-confidence/feature-inspector.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.