> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/saas-pricing-subscriptions-and-access.md).

# SaaS pricing, subscriptions & access

SaaS plans, pricing snapshots, entitlements, authentication, onboarding, checkout reconciliation and redirect policy.

SONIC separates identity, workspace context, subscription entitlements, AI Credits and RBAC permissions so pricing changes do not become security changes.

## Access model

```
Authentication identifies the user.
Workspace membership establishes where they operate.
Subscription grants product entitlements.
AI Credits meter AI consumption.
Roles and policies authorize actions.
Redirect policy resolves the next screen.
```

## Plans

The SaaS catalog may expose tiers such as **Free**, **Creator**, **Pro**, **Studio** and **Enterprise**. Exact prices and quotas must come from the current versioned catalog; documentation examples are not pricing authority.

Plan comparison should focus on meaningful limits: AI Credits, model access, projects, storage, collaboration, commercial tooling, analytics, Marketplace capabilities and support level.

## Versioned pricing

Price versions are append-only and include atomic amount, currency, decimals, interval, tax behavior, effective period and catalog version/integrity metadata.

Subscriptions snapshot the commercial values used at purchase or renewal so a later catalog change cannot rewrite history.

## Entitlements vs roles

An entitlement answers **is this feature included in the product plan?** A permission answers **may this user perform this action?**

A Pro creator is not automatically an Admin. A Finance user is not automatically entitled to every premium creator feature.

## Subscription lifecycle

Recommended states include `none`, `trialing`, `active`, `past_due`, `grace_period`, `paused`, `cancelled` and `expired`. Cancellation should preserve access through the paid-through date where applicable. Downgrades can be scheduled for renewal rather than rewriting current entitlements immediately.

## Checkout authority

```
Pricing → CheckoutIntent → provider checkout → verified provider event → subscription transition → entitlement refresh
```

A browser success redirect is informational only. Provider webhook/reconciliation establishes authoritative paid state. Checkout creation and provider event ingestion must be idempotent.

## Redirect resolver

Protected routes resolve session, account status, workspace, membership, subscription, entitlements, permissions, feature state and resource state before rendering.

Missing entitlement should route to an upgrade/plan surface. Missing permission should produce a clear `403`, not a billing prompt.

Approved internal deep links may be carried through login with a validated `returnTo` value. External/open redirect destinations must be rejected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/application-and-website/saas-pricing-subscriptions-and-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.