Billing and security
Billing and plans
Understand Fygment plans, how workspace billing works with Stripe, and what each tier includes.
- Audience
- Workspace owners and admins deciding how their workspace should be billed.
- Updated
- 2026-05-20
Billing uses a workspace effective tier: Solo remains free for the local creator loop, Advanced / Teams unlocks paid collaboration and external import actions, and Enterprise is support-managed.
How billing works
Fygment bills through Stripe, with hosted Checkout, a Customer Portal, webhooks, workspace customers, subscription state, and soft seat gates.
Paid-only actions resolve through a workspace effective tier. Solo keeps reads, existing access, local creation, package, install, and check basics, and public templates. Advanced / Teams covers external imports, AI-assisted imports, team sharing, the private team registry, approval governance, and external-source update checks.
Enterprise is support-managed and set up through a contract. Contact support to discuss SSO, SCIM, on-premises sync, SIEM export, or SOC 2 Type II support requirements.
Billing attention states block new paid-only actions but do not suspend existing workspace reads.
Entitlement source
What owners see in pricing settings
Workspace pricing settings show the effective tier, source, status, next action, included paid features, and tier-gated features that are not included. Sources can be default Solo, Stripe subscription, manual override, enterprise contract, or site-owner override.
Manage your plan
- 1
Review pricing settings
Open workspace pricing settings to see your effective tier, its source, and the next action available to you.
- 2
Start or change a plan
Owners and admins use Stripe Checkout to start a Team subscription for the workspace.
- 3
Manage payment details
Use the Stripe Customer Portal to update payment details or cancel. Webhooks keep the workspace subscription state in sync.
- 4
Check your seats
Seat gates apply to Team workspaces, so check your member count before inviting more teammates.
Related docs
- Workspaces, members, and access
A workspace is the unit of trust in Fygment. Membership, role, invite, install, report, and billing behavior all resolve through that boundary.
- Security and privacy boundaries
The Fygment trust model is metadata-minimizing: keep customer Skill content, package bodies, prompts, secrets, tokens, and raw local paths out of admin, support, analytics, and billing surfaces.
- Troubleshooting
Start with safe, non-sensitive checks. Fygment support reports should capture bounded diagnostics, not package bodies, secrets, raw prompts, or local paths.