Skip to main content
Fygment
<- Docs home

Release And Launch Status

Manual

Billing and launch mode

Understand Fygment manual billing, Stripe test-mode foundation, and the gates before self-serve paid billing is live.

Audience
Workspace owners, admins, and launch reviewers deciding how billing should behave during public launch.
Updated
2026-05-20

Public launch uses a workspace effective tier: Solo remains free for the local creator loop, Advanced / Teams unlocks paid collaboration and external import actions, and Enterprise stays support-managed.

Current billing boundary

Fygment has a Stripe billing foundation for hosted Checkout, Customer Portal, webhooks, workspace customers, subscription state, and soft seat gates.

Paid-only mutations now resolve through a workspace effective tier. Solo keeps reads, existing access, local creation/package/install/check basics, and public templates. Advanced / Teams is required for external imports, AI-assisted imports, team sharing, private team registry, approval governance, and external-source update checks.

Enterprise is support-managed in this phase. It can be represented as an entitlement for support and contracts, but SSO, SCIM, on-prem sync, SIEM export, and compliance support remain roadmap claims until implemented.

Self-serve paid billing still depends on live Stripe configuration and preview/live smoke evidence. Billing attention states block new paid-only actions but do not hard-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 unavailable tier-gated features. Sources can be default Solo, Stripe subscription, manual pilot override, enterprise contract, or site-owner override.

Before self-serve paid billing

  1. 1

    Configure Stripe products and prices

    Choose amount, currency, recurring interval, tax, trial, cancellation, and portal behavior intentionally.

  2. 2

    Map price ids to Team entitlement

    Set the monthly and yearly Team price ids for the target environment. Unknown price ids and test/live mismatches fail closed for paid actions.

  3. 3

    Configure webhook endpoint and secret

    Webhooks remain the source of truth for provisioning subscription state.

  4. 4

    Keep enforcement non-blocking until backfill

    Use disabled or observe mode for pricing-tier enforcement until active pilot workspaces are classified and QA evidence is attached.

  5. 5

    Backfill pilot workspaces

    Classify active pilot workspaces as Stripe Team, manual pilot, Enterprise contract, or explicit Solo before production enforcement.

  6. 6

    Run preview and live smoke

    Owner/admin Checkout, return, webhook provisioning, Portal, and seat-gate behavior must be verified before enabling billing broadly.

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 public launch 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.