Plans And Limits
How to interpret TrialStack plan scope, workflow limits, and usage boundaries without confusing packaging with raw billing mechanics.
Separate packaging from operational limits
flowchart LR
Packaging["Pricing and packaging"] --> Limits["Operational limits"]
Limits --> Admin["Admin and usage review"]
Pricing & Packaging explains why a team should choose Ignite, Accelerate, or Scale.
This page explains the boundary conditions that still matter after that choice:
- how tightly scoped the rollout is meant to be
- where governed workflows should not be bypassed
- when usage review is an adoption question rather than a pricing question
Current plan limits at a glance
| Area | Ignite | Accelerate | Scale |
|---|---|---|---|
| Usage | 500,000 tokens / month, 3 users | 2,000,000 tokens / month, 8 users | 8,000,000 included tokens / month, Unlimited users |
| Trials | 1 active, persona feedback No, feasibility review No | 3 active, persona feedback Yes, feasibility review Yes | 10+ / custom active, persona feedback Yes, feasibility review Yes |
| Evidence Packs | 3 active, 3 templates | 15 active, 10 templates | 50 active, Unlimited templates |
| Documents | 12 active, 8 templates | 40 active, 25 templates | 150 active, 50 templates |
| Insights | 3 active | 15 active | 50 active |
| Revisions | 10 active, 1 template | 40 active, 5 templates | 150 active, 15 templates |
| Connections | systems 8, contacts 25, interventions 10, organizations 10, personas 10, sites 5 | systems 20, contacts 100, interventions 25, organizations 30, personas 30, sites 40 | systems 40, contacts 500, interventions 100, organizations 100, personas 100, sites 200 |
| Tools | configurable skills No, rules 5, runs 2 | configurable skills Yes, rules 15, runs 5 | configurable skills Yes, rules 50, runs 10 |
| Support | email Yes, phone No, onboarding No, SLA None | email Yes, phone Business hours, onboarding Yes, SLA < 1 business day | email Yes, phone Priority, onboarding Yes, SLA < 4 business hours |
| Security | SAML No, RBAC No, HIPAA BAA No, SCIM No, 2FA Yes | SAML No, RBAC Yes, HIPAA BAA Optional add-on, SCIM No, 2FA Yes | SAML Yes, RBAC Yes, HIPAA BAA Yes, SCIM Yes, 2FA Yes |
The main limits are workflow limits
The most important limits are often about operating discipline, not raw quota:
- approval-sensitive work should not bypass review
- AI-assisted drafting should not be treated as automatic approval
- plan quotas still matter for tokens, active records, templates, and concurrent runs
- queue-backed work may not behave like an immediate synchronous save
- deleted and restored records follow governed behavior instead of casual file-manager behavior
Read limits in context
When boundary questions appear, first check whether the issue is:
- a packaging question about plan fit
- a workflow question about review, approval, or export behavior
- an admin question about roles, defaults, or oversight
Use these pages when that distinction matters:
- Pricing & Packaging for plan logic and upgrade triggers
- Usage & Billing for adoption and operational oversight
- Users for access and role ownership
- Preferences for workspace defaults and AI settings
Do not confuse usage visibility with entitlement design
Usage views help admins understand adoption and operational load. They are not the source of truth for plan intent, governance depth, or commercial scope.
Those packaging decisions belong in pricing and contract scoping, not in the usage dashboard alone.