How billing works
Suede's billing model, plan tiers, and the relationship between parent orgs, child orgs, and subscriptions.
Suede bills per child organization. Each child org holds its own Stripe subscription, usage limits, and feature entitlements. The parent org is an administrative hub where you manage subscriptions and view rolled-up billing data across all your child orgs.
When you create a child org, it starts on the Free plan. Upgrading means selecting a child org and changing that org's subscription. There are no shared resource pools between child orgs.
Core billing concepts
Monitored prompts are the primary billing unit. A monitored prompt is a distinct prompt template that Suede runs daily across your enabled AI platforms. Adding an AI platform increases your platform count (a separate billing dimension) but does not consume additional prompts.
Usage dimensions track consumption within each billing period:
- Monitored prompts
- Chat tokens (AI assistant usage)
- MCP calls
- Workflow executions
- Pitch spaces (agency overlay only)
Modules are optional features you can add to a child org's subscription. Some modules are included at certain plan tiers; others are always add-ons. See Modules for the full list.
Allocations cover resources that scale by count rather than consumption: seats, AI platforms, regions, and languages. Each plan includes a base allocation. You can purchase additional units as add-ons on paid plans.
Billing periods and invoicing
Billing periods are monthly, aligned to each child org's subscription start date. Stripe generates one invoice per child org per period, covering the base plan, any active modules, and metered usage.