# Plans & add-ons

What each subscription tier includes, the CIAM and DIAM add-ons, and the sizing limits that apply.

Your access to features is governed by two independent things: your **subscription tier** (Free, Essential, Advanced, or Pro) and any **add-ons** you have licensed (CIAM and DIAM). This page explains both, and the limits that come with each.

Where a documentation page describes a gated feature, it opens with a callout naming the add-on or the lowest tier that includes it.

## Subscription tiers

| Tier | Best for | Highlights |
|---|---|---|
| **Free** | Getting started at no cost | Core authentication (passkeys, MFA, SSO), social login, one enterprise directory integration, small limits |
| **Essential** | Simple projects needing solid security | Enterprise directory integration, passkeys & MFA, enhanced password protection, threat protection |
| **Advanced** | Advanced use cases | Everything in Essential plus conditional access, network zones, enterprise brokering, RBAC, device compliance |
| **Pro** | Large or unique requirements | Everything in Advanced plus advanced deployment options, geo-redundancy, and full support |

## Add-ons

Add-ons unlock whole capability areas and are licensed separately from the tier:

- **CIAM: Customer Identity.** Manage external (non-employee) users measured as monthly active users, and B2B **organizations**. Unlocks the *Customers* and *Consumers* user types. Social login connections themselves are part of every plan; external users signing in through them count toward the monthly active users.
- **DIAM: Device Identity.** Manage enrolled endpoints, evaluate device compliance, and use device-based authentication. Unlocks the [Device inventory](https://dts-identity.com/docs/endpoints/device-inventory.md) and [device compliance policies](https://dts-identity.com/docs/security/conditional-access/device-compliance-policies.md).

> **Note:** Some features need *both* a tier and an add-on. For example, B2B organizations require the CIAM add-on **and** the `organizations` feature (Advanced+); device compliance requires the DIAM add-on **and** the `deviceTrust` feature (Advanced+).

## Feature availability by tier

| Feature | Free | Essential | Advanced | Pro |
|---|:---:|:---:|:---:|:---:|
| Multi-factor authentication | ✓ | ✓ | ✓ | ✓ |
| SMS authentication (MFA and mobile verification) | – | ✓ | ✓ | ✓ |
| Passwordless email login, needs CIAM | – | ✓ | ✓ | ✓ |
| Enhanced password protection | ✓ | ✓ | ✓ | ✓ |
| Threat protection | ✓ | ✓ | ✓ | ✓ |
| Cross-app single sign-on | ✓ | ✓ | ✓ | ✓ |
| Passkeys (passwordless) | ✓ | ✓ | ✓ | ✓ |
| Social login connections | ✓ (3) | ✓ | ✓ | ✓ |
| Privileged admin accounts & emergency access (break-glass) | – | ✓ | ✓ | ✓ |
| Temporary access code (help-desk MFA fallback) | – | ✓ | ✓ | ✓ |
| Third-party MFA (Cisco Duo, privacyIDEA) | – | – | ✓ | ✓ |
| OATH hardware tokens (TOTP / HOTP) | – | – | ✓ | ✓ |
| Application provisioning (outbound SCIM) | – | ✓ | ✓ | ✓ |
| Custom domain | – | ✓ | ✓ | ✓ |
| Custom mail provider | – | ✓ | ✓ | ✓ |
| Custom SMS gateway | – | ✓ | ✓ | ✓ |
| Authentication policies (conditional access) | – | – | ✓ | ✓ |
| Approval workflows & access certification | – | – | ✓ | ✓ |
| Alarms on the audit log | – | – | ✓ | ✓ |
| Network zones | – | – | ✓ | ✓ |
| Enterprise identity brokering | – | – | ✓ | ✓ |
| Role-based access control (RBAC) | – | – | ✓ | ✓ |
| Custom profile attributes | – | – | ✓ | ✓ |
| Windows SSO (Kerberos) | – | – | ✓ | ✓ |
| FAPI 2.0 security profile | – | – | ✓ | ✓ |
| FAPI 1.0 Advanced security profile | – | – | – | ✓ |
| OAuth dynamic client registration | – | – | ✓ | ✓ |
| Public client registration for AI agents | – | – | – | ✓ |
| Organizations (B2B), needs CIAM | – | – | ✓ | ✓ |
| Invitation workflows for organizations, needs CIAM | – | – | ✓ | ✓ |
| Device compliance, needs DIAM | – | – | ✓ | ✓ |
| MFA for Windows logon, needs DIAM | – | ✓ | ✓ | ✓ |
| Device-based authentication, needs DIAM | – | – | ✓ | ✓ |
| Device endpoint vulnerabilities, needs DIAM | – | – | ✓ | ✓ |

A "–" means the feature is not included at that tier. Entitlements are evaluated against your current license at all times.

## Sizing limits

| Resource | Free | Essential | Advanced | Pro |
|---|---|---|---|---|
| Tenants | 1 | 2 | 5 | unlimited |
| Employee users | 25 | up to 2,000 | up to 10,000 | from 500 up |
| External MAU (CIAM) | up to 1,000 | up to 100,000 | up to 500,000 | custom |
| Devices (DIAM) | – | up to 500 | up to 5,000 | custom |
| Applications | 5 | unlimited | unlimited | unlimited |
| Enterprise integrations | 1 | unlimited | unlimited | unlimited |
| Connections | 3 | unlimited | unlimited | unlimited |
| Organizations | – | – | unlimited | unlimited |
| Authentication policies | – | – | unlimited | unlimited |
| Network zones | – | – | unlimited | unlimited |
| Admin team members | 3 | 10 | 100 | unlimited |
| Log retention | 7 days | 30 days | 90 days | up to 365 days |
| Machine-to-machine tokens per month | 1,000 | unlimited | unlimited | unlimited |
| Machine-to-machine token requests per minute, per client | 60 | 1,200 | 6,000 | 30,000 |

The two machine-to-machine limits work differently: the monthly figure is a volume budget that exists on the entry tiers only, while the per-minute figure is a throughput limit that applies on every tier and answers a client that exceeds it with `HTTP 429` and a `Retry-After` header. A service that caches its access token stays far below both. See [APIs](https://dts-identity.com/docs/integrations/apis.md#machine-to-machine-token-limits).

## Platform separation

Some properties are not tiered at all. They follow from how the platform is deployed, and they apply on every plan including Free:

| Property | Included in every plan |
|---|---|
| Your own database, with its own credentials | ✓ |
| Your own application instances, serving no other tenant | ✓ |
| Multiple instances per deployment | ✓ |
| Your own signing keys, encryption keys, and audit log | ✓ |
| Data center in Germany, EU data protection compliant | ✓ |

The higher tiers add dedication on top of that separation rather than creating it: a **private database cluster** (optional on Advanced, included on Pro) removes the shared database environment, and a **private deployment** (Pro) removes the shared cluster. The Free plan runs the same architecture as Pro, so an upgrade changes limits and features but never moves your tenant to a different stack. See [Platform architecture](https://dts-identity.com/docs/getting-started/platform-architecture.md) for the full picture.

## Admin access levels by tier

The set of [admin access levels](https://dts-identity.com/docs/security/admin-console-users.md) you can assign also depends on the tier:

- **Free:** Owner
- **Essential:** Auditor, Operator, Owner
- **Advanced / Pro:** all levels

## How gating behaves

Feature gating is evaluated live against your license, so there is no restart or re-provisioning when your subscription changes. If an add-on lapses, areas that depend on it stop accepting *new* configuration, but data created earlier remains viewable so you are never locked out of your own records.

You can review your current entitlements at any time under [Settings → License & subscription](https://dts-identity.com/docs/settings/license-and-subscription.md).
