> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alforse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans & Editions

> Commercial packages, feature entitlements, and deployment editions.

Alforse plans are enforced server-side against a shared feature catalog — not a UI-only toggle.
A plan's features are normalized into a boolean map, and backend entitlement checks
(`QuotaService.assertFeatureEnabled`) gate the corresponding endpoints. If an endpoint in the
[API Reference](/api-reference/introduction) mentions a feature flag, that's what it's checking.

## Plans

| Plan          | Intended use                          | Adds on top of the previous tier                                                                                          |
| ------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| `free`        | Trial and small teams                 | Core contract workspace, custom fields, file evidence, audit trail                                                        |
| `team`        | Operational teams                     | OCR intake, workflow automation, notification channels, webhooks                                                          |
| `business`    | Larger SaaS customers                 | SSO, **external API access**, advanced audit export, AI gateway policy controls                                           |
| `enterprise`  | Hosted entry with enterprise controls | Support windows, customer-managed keys, customer data plane, private connector                                            |
| `self_hosted` | Customer-operated runtime             | Customer-managed database, customer-managed object storage, offline-capable license, signed upgrades, self-managed OCR/AI |

If you're integrating directly with the [API Reference](/api-reference/introduction) rather than
through the Deals/Console UI, you need at least a `business` plan.

## The `enterprise_hybrid` edition

`enterprise_hybrid` is a tenant **edition**, not a plan tier: users still sign in through the
Alforse-hosted application, but business data is routed to the customer's own data plane rather
than Alforse's. The system metadata layer may store tenant metadata, subscription state,
license state, feature entitlements, and endpoint health for a hybrid tenant — it must not store
contract originals, OCR text, payment records, dynamic field values, or customer-managed secrets.

## Redemption codes and onboarding

There are two ways a tenant comes into existence:

1. **Assisted onboarding** — Alforse prepares the tenant on the chosen plan, typically for
   sales-assisted onboarding.
2. **Redemption code** — a code issued for a specific plan that a prospective customer redeems
   themselves (`POST /auth/redeem`), which creates the
   tenant, the admin account, and an active subscription for the code's plan in one step.

Public self-service registration without a code (`POST /auth/register`) exists in the API but is
disabled in production (`PUBLIC_REGISTRATION_ENABLED=false`) and is hard-limited to the `free`
plan when it is enabled.

## Deployment modes

| Mode                       | What it is today                                                                                                                                                           |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **SaaS cloud**             | The live product at `*.alforse.com` — Cloudflare-fronted API, managed Postgres, tenant-scoped data with row-level security.                                                |
| **Enterprise self-hosted** | The `self_hosted` plan: customer-operated Postgres, object storage, and license file, deployed under an enterprise self-hosted license. See [Installation](/installation). |
| **Enterprise hybrid**      | The `enterprise_hybrid` edition described above — hosted frontend, customer-owned data plane.                                                                              |

Private cloud and offline-capable packages require an enterprise self-hosted agreement and an
implementation plan with Alforse. Talk to your Alforse contact if you need one of these
deployment models.