# Plans & Licensing

> **Sentinel v2 (beta):** This page documents Sentinel v2, a beta rewrite that may change before the stable release. It does not apply to Sentinel v1, the current stable version: see the [Sentinel v1 documentation](/docs/sentinel.md).

<Callout type="warning" title="Only trial licenses during the beta">

Sentinel v2 is in beta and isn't meant for production use yet. Until v2 reaches general availability, only [trial licenses](#trial) are available; the paid plans below describe the licensing at general availability. For production deployments, use [Sentinel v1](/docs/sentinel/plans/).

ALTCHA Sentinel is self-hosted: you run it on your own infrastructure, and hosting is never part of the license. The license enables the challenge, verification, and detection APIs, raises the capacity limits, and unlocks the enterprise integrations. This page explains what each plan includes. To install a license, see [Configure the license](/docs/sentinel/v2/configure/licensing/); for current prices and checkout, see [Pricing](/pricing/#sentinel).

## How licensing works

- **Every deployment needs an active license.** Without one, the widget and detection endpoints (`/v2/challenge`, `/v2/verify`, `/v2/classifier`, and the rest) answer `403 LICENSE_NOT_ACTIVE`. You can still sign in to the admin UI and diagnose the instance.
- **A license is a signed document.** It names the plan, the licensee, the term, the license features, and the limits. Sentinel checks the signature offline.
- **You get it from [cloud.altcha.org](https://cloud.altcha.org).** Each license has a production key and a non-production key. Either key works as an online key (`SENT-…`) or downloads a license file bound to one deployment. Both carry the same plan.
- **The license lives in `sentinel.toml`.** You set it with `[license] key` or `[license] file`. The admin UI shows the license status but can't install a license.
- **Detection doesn't depend on the plan.** Every plan includes every protection feature and API. Plans differ in capacity, database support, and enterprise integrations.

## Plan comparison

| | Trial | Professional | Enterprise | Enterprise Lifetime |
| --- | --- | --- | --- | --- |
| **Price** | Free | €99 / month<br />(€990 / year) | €799 / month<br />(€7,990 / year) | On request, one-time |
| **Term** | 60 days | Subscription | Subscription | Perpetual |
| **Production use** | No | Yes | Yes | Yes |
| **All protection features and APIs** | Yes | Yes | Yes | Yes |
| **Deployments** | 1 | 1 production<br />2 non-production | Unlimited | Unlimited |
| **Instances** (`instances`) per deployment | 3 | 3 | Unlimited | Unlimited |
| **Standby instances** per deployment | 3 | 3 | Unlimited | Unlimited |
| **Accounts** (`accounts`) | 10 | 10 | Unlimited | Unlimited |
| **Users** (`users`) | 10 | 10 | Unlimited | Unlimited |
| **API keys** (`api_keys`) | 10 | 50 | Unlimited | Unlimited |
| **Security groups** (`security_groups`) | 10 | 50 | Unlimited | Unlimited |
| **Domains and verifications** | Unlimited | Unlimited | Unlimited | Unlimited |
| **SQLite, PostgreSQL, MySQL, MariaDB** | Yes | Yes | Yes | Yes |
| **Microsoft SQL Server, Oracle** | Yes | — | Yes | Yes |
| **ClickHouse request logs** (`clickhouse`) | Yes | — | Yes | Yes |
| **Audit logs** (`audit_logs`) | Yes | — | Yes | Yes |
| **OAuth sign-in** (`oauth`) | Yes | — | Yes | Yes |
| **LDAP sign-in** (`ldap`) | Yes | — | Yes | Yes |
| **Software updates** | During the trial | Yes | Yes | Lifetime |

The names in parentheses are the license features and limits that Sentinel checks; [License features](#license-features) and [License limits](#license-limits) explain each one. The database rows correspond to the features `exotdb.backend.sqlite`, `exotdb.backend.postgres`, `exotdb.backend.mysql`, `exotdb.backend.mariadb`, `exotdb.backend.mssql`, and `exotdb.backend.oracle`. The license server counts deployments; see [Deployments](#deployments). [Standby instances](#standby-instances) don't need instance slots.

**Enterprise Multi-Tenant** is a separate arrangement for running one deployment for several organizations, including offering Sentinel-backed protection to third parties as a service. [Contact us](/contact/) for terms.

## Trial

The trial lets you evaluate every feature before you buy. To start it, register at [cloud.altcha.org](https://cloud.altcha.org) and create a Sentinel V2 trial license in the **Licenses** section.

- **60 days**, starting when you create the trial license.
- **Every license feature**, including SQL Server, Oracle, ClickHouse, audit logs, OAuth, and LDAP, so you can test an Enterprise setup.
- **3 instances**, and 10 each of accounts, users, API keys, and security groups.
- **One deployment.** The trial key activates one Sentinel deployment, either online or through a license file.
- **One trial per cloud account.**
- **Not for production traffic.** The [EULA](/legal/sentinel/eula/) limits the trial to testing and evaluation.

Install the trial like any other license: see [Configure the license](/docs/sentinel/v2/configure/licensing/). When the trial ends, the license status becomes `expired` and the functional API stops; see [When a license ends](#when-a-license-ends).

## Without a license

Sentinel starts without a license, but it doesn't serve traffic. The challenge, verification, and detection endpoints answer `403 LICENSE_NOT_ACTIVE`. Sign-in, the management API, `/v2/license*`, and `/v2/doctor*` keep working, so you can sign in as root, copy the deployment ID, and run diagnostics.

Without a usable license (no license, a license that isn't valid yet, or a revoked one), Sentinel runs on the **baseline**:

| | Baseline |
| --- | --- |
| Database | Embedded SQLite only (`exotdb.backend.sqlite`) |
| Instances | 3 |
| Accounts, users, API keys, security groups | 1 each |
| ClickHouse, audit logs, OAuth, LDAP | Not available |

The first start always creates the default account and the root user, so they use up the account and user allowance of the baseline. If `[database] url` points at another backend, Sentinel still connects and starts, but most `/v2` routes answer `403 BACKEND_NOT_LICENSED` until a license with that backend is installed.

## License features

A license feature switches on one capability. A feature that a license doesn't list isn't available, whatever the configuration says.

| Feature | Unlocks | Without it |
| --- | --- | --- |
| `exotdb.backend.sqlite` | The embedded SQLite database. Part of every plan and the baseline. | — |
| `exotdb.backend.postgres`<br />`exotdb.backend.mysql`<br />`exotdb.backend.mariadb` | PostgreSQL, MySQL, or MariaDB as the main database, and the built-in KV store on it. | Most `/v2` routes answer `403 BACKEND_NOT_LICENSED`. |
| `exotdb.backend.mssql`<br />`exotdb.backend.oracle` | Microsoft SQL Server or Oracle as the main database, and the built-in KV store on it. | Most `/v2` routes answer `403 BACKEND_NOT_LICENSED`. |
| `clickhouse` | Request logs in ClickHouse (`[clickhouse]`). Checked at startup. | Request logs stay in the main database; startup logs a warning. |
| `audit_logs` | Recording audit log entries. | Nothing is recorded. Existing entries stay searchable. |
| `oauth` | Admin sign-in with OAuth providers (`[auth.oauth.*]`). | The OAuth sign-in options are hidden, and the OAuth routes redirect with `FEATURE_NOT_LICENSED`. |
| `ldap` | Admin sign-in with LDAP (`[auth.ldap]`). | The LDAP sign-in option is hidden, and `POST /v2/auth/ldap` answers `403 FEATURE_NOT_LICENSED`. |

Supported database versions and connection settings are in [Databases & KV store](/docs/sentinel/v2/configure/databases/). OAuth and LDAP setup is in [Admin sign-in & SSO](/docs/sentinel/v2/security/sign-in/#single-sign-on). While no licensed OAuth or LDAP sign-in is configured, password sign-in stays available, even with `[auth] password_login = false`, so root can always sign in.

### Not gated by any plan

These work the same with every license, because Sentinel doesn't check a license feature for them:

- every detection and protection feature: proof-of-work, code challenge, Human Interaction Signature, rate limiting, the classifier, text analysis, similarity, the AI decider, threat intelligence, phishing detection, email analysis, and Web Bot Auth;
- Redis or Valkey as the KV store (`[redis]`), required for more than one replica;
- a remote ExotDB server as the database (`[database] url = "https://…"`); the ExotDB server enforces its own license;
- Prometheus metrics, OpenTelemetry tracing (`[telemetry]`), alerts, snapshots, and request logs in the main database;
- passkeys, TOTP, and step-up verification for admin users.

## License limits

A limit caps how many of something can exist at once. Enterprise licenses set every limit to unlimited.

| Limit | Counts | When the limit is reached |
| --- | --- | --- |
| `instances` | Sentinel processes sharing one database at the same time | A new replica waits for a free slot; see [Instances](#instances). |
| `accounts` | Accounts that aren't deleted | `POST /v2/accounts` answers `403 LICENSE_LIMIT_REACHED`. |
| `users` | Users that aren't deleted, root users included | `POST /v2/users` and the first OAuth or LDAP sign-in of a new user are refused with `LICENSE_LIMIT_REACHED`. |
| `api_keys` | API keys that aren't deleted, across all accounts | Creating an API key answers `403 LICENSE_LIMIT_REACHED`. |
| `security_groups` | Security groups that aren't deleted, across all accounts | Creating a security group answers `403 LICENSE_LIMIT_REACHED`. |

Only creation is refused. Records that already exist keep working when you reach a limit or when a license lapses, and deleting a record frees its place. Sentinel counts and inserts under a database lock, so concurrent requests on several replicas can't exceed a limit. The error carries the limit and its maximum, for example `"data": {"limit": "users", "max": 10}`; see [Error codes](/docs/sentinel/v2/reference/errors/).

### Instances

An instance is one running Sentinel process: one container, pod, or replica. Each replica holds a leased slot in the shared database, so the `instances` limit applies to all replicas that share one database.

- **Rolling deploys** don't need spare capacity. Besides the regular slots, a license grants a few short-lived burst slots, so a new replica can start before the old one stops.
- **At startup**, a replica that finds no free slot within 60 seconds exits with an error that names the nodes holding the slots.
- **At runtime**, a replica that loses its slot keeps serving for 5 minutes while it retries, then answers `503 LICENSE_INSTANCE_LIMIT` until a slot frees up. Nothing is shut down by the license server.

Leases, burst rules, and node IDs are covered in [Clustering & high availability](/docs/sentinel/v2/operations/clustering/#instance-slots).

### Standby instances

A standby instance is a warm failover replica, for example in a second availability zone, that shares the production database. You mark it with `[license] standby = true`. It starts without an instance slot and serves nothing but `GET /` until a regular slot frees up, for example when a production replica or its zone goes down. Then it takes that slot and starts serving like any other replica.

A deployment can run as many standby instances as it has licensed instances: 3 standbys next to 3 active replicas on Trial and Professional, any number on Enterprise. Standbys take no slot while they wait, and they share the production database, so they don't count as another deployment. How standbys wait, take over, and fail back is covered in [Clustering & high availability](/docs/sentinel/v2/operations/clustering/#standby-instances).

### Deployments

A deployment is one Sentinel database, together with every replica and standby instance that shares it. Its deployment ID is stored in that database. A staging environment with its own database is a separate deployment with its own instance slots, so it needs its own activation or license file.

cloud.altcha.org counts deployments per license key. Activating a key online and downloading a license file each use up one deployment of that key.

| | Trial | Professional | Enterprise |
| --- | --- | --- | --- |
| Production key | — | 1 deployment | Unlimited |
| Non-production key | — | 2 deployments | Unlimited |
| Trial key | 1 deployment, evaluation only | — | — |

Use the non-production key for staging, test, and development environments. Licenses issued for it mark every `/v2` response with `X-Sentinel-License: non-production`; see [Non-production licenses](/docs/sentinel/v2/configure/licensing/#non-production-licenses). Each deployment has its own instance limit, so a Professional staging deployment can also run 3 instances.

## When a license ends

When a subscription or trial ends, the license status becomes `expired`. An online license that Sentinel can't refresh in time becomes `refresh_overdue`. In both cases:

- the functional API answers `403 LICENSE_NOT_ACTIVE`;
- the license features and limits stay in effect, so the database stays licensed, OAuth and LDAP users can still sign in, audit logs are still recorded, and no replica loses its slot;
- no data is deleted or disabled.

Any grace period, such as the payment settlement window of a renewing subscription, is already included in the license's end date. A revoked license drops to the [baseline](#without-a-license).

When you renew, upgrade, or change a plan in cloud.altcha.org, an online key picks up the new license at its next refresh, about once a day. A license file has a fixed term, so download a new file and restart Sentinel. Status values and alerts that warn before expiry are listed in [Configure the license](/docs/sentinel/v2/configure/licensing/#status-values).

<Callout type="tip" title="Renew before expiry">

Alert on `altcha_sentinel_license_expiry_timestamp_seconds - time()` in Prometheus, or watch the `license_expired` and `license_refresh_failing` alerts, so the functional API doesn't stop unexpectedly.

## Support plans

**Basic support** (email, best-effort response) is included with every license. Paid support is a separate add-on: it changes the response-time SLA and the channels, and it never unlocks product features. Which support plan you can buy depends on your license.

| Support plan | Requires license | Channels | Response SLA | Typical resolution | Price |
| --- | --- | --- | --- | --- | --- |
| Basic | Any | Email | Best-effort | — | Free |
| Standard | Professional | Email | &lt;&#8202;12h | Within a day | €39 / month |
| Standard Enterprise | Enterprise | Email | &lt;&#8202;6h | Within hours | €300 / month |
| Priority Enterprise | Enterprise | Email, live chat | &lt;&#8202;4h | Within hours | €600 / month |

Enterprise support engagements also include an integration review and periodic health checks. See the [Support Policy](/legal/sentinel/support/) for scope and definitions.

## Choosing a plan

- **Evaluating Sentinel**: the **Trial** includes every feature for 60 days.
- **Production with one deployment of up to 3 instances (plus up to 3 standbys), up to two non-production deployments, and up to 10 accounts, users**, on SQLite, PostgreSQL, MySQL, or MariaDB: **Professional**.
- **SQL Server, Oracle, ClickHouse, OAuth or LDAP sign-in, audit logs, unlimited API keys, more than 3 instances, more than one production deployment, or larger tenant counts**: **Enterprise**.
- **A long-term deployment where a one-time cost beats a subscription**: **Enterprise Lifetime**.
- **One deployment serving several organizations, or reselling protection**: **Enterprise Multi-Tenant** ([contact us](/contact/)).

## Related

- [Configure the license](/docs/sentinel/v2/configure/licensing/): online keys, license files, status values, alerts, and metrics
- [Clustering & high availability](/docs/sentinel/v2/operations/clustering/): instance slots and standby instances across replicas
- [Databases & KV store](/docs/sentinel/v2/configure/databases/): supported backends and versions
- [Accounts, users & roles](/docs/sentinel/v2/concepts/accounts-users/)
- [Pricing](/pricing/#sentinel)
- [EULA](/legal/sentinel/eula/) and [Support Policy](/legal/sentinel/support/)
