> For the complete documentation index, see [llms.txt](https://docs.flowcp.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowcp.ai/reference/plans-and-features.md).

# Plans & features

FlowCP ships the same four plans in both deployment modes — **Starter**, **Team**, **Business**, and **Enterprise** (keys: `starter`, `team`, `business`, `enterprise`). What changes between modes is how requests are metered and where the plan comes from; what stays the same is that **features are gated by plan**.

## Cloud vs Self-Hosted

| Aspect           | Cloud                                                         | Self-Hosted                                                          |
| ---------------- | ------------------------------------------------------------- | -------------------------------------------------------------------- |
| Deployment       | Managed multi-tenant service ([flowcp.ai](https://flowcp.ai)) | You run it ([self-host the platform](/guides/self-host-platform.md)) |
| MCP requests     | **Metered** per plan (included volume + overage)              | **Unlimited** — no metered quota                                     |
| Plan source      | **Stripe subscription**                                       | Signed **license key** (`FLOWCP_LICENSE_KEY`)                        |
| No plan / no key | New workspaces start on **Starter**                           | No key → free **Starter** plan                                       |
| Plan management  | **Billing** tab (Stripe Checkout / Portal)                    | **License** panel (no Stripe config shipped)                         |

For Cloud request metering, included volumes, overage rates, and quota behavior, see [Billing & plans](/reference/billing-and-plans.md). Self-Hosted forgoes metering entirely — there is no included-call allowance or overage.

## Plan → feature matrix

Features unlock **cumulatively**: each plan includes everything below it plus its own additions.

| Plan           | Requests (Cloud / Self-Hosted)  | Premium features unlocked (cumulative)                    |
| -------------- | ------------------------------- | --------------------------------------------------------- |
| **Starter**    | Metered (free tier) / Unlimited | Core only                                                 |
| **Team**       | Metered / Unlimited             | + Environments (separate dev/prod URLs) + Version history |
| **Business**   | Metered / Unlimited             | + RBAC / advanced roles + Alerts & monitoring             |
| **Enterprise** | Metered / Unlimited             | + Golden-scenario replay + Audit-log streaming            |

### Core (every plan, both modes)

Available on every plan in both Cloud and Self-Hosted:

* Connect / import APIs (Generic OpenAPI, Bubble, Git-backed sources)
* Tools, resources, prompts, widgets, and skills
* MCP serving and publishing
* User-context OAuth and all auth providers
* Playground
* Embeddable chat widget
* Connector library
* CLI and GitHub Actions
* Per-server export folder
* Feedback
* Server tests
* Logs, health, and stats views

### Team adds

* **Environments** — separate dev/prod URLs per server.
* **Version history** — server-config version snapshots and rollback.

### Business adds

* **RBAC / advanced roles** — finer-grained workspace roles.
* **Alerts & monitoring** — health alerts and monitoring.

### Enterprise adds

* **Golden-scenario replay** — recorded-scenario regression replay.
* **Audit-log streaming** — stream the audit log to your own sink.

## Where the matrix is defined

The authoritative plan definitions — keys, ordering, and which feature each plan unlocks — live in code in **`PLAN_CONFIGS`** (`packages/shared/src/plans.ts`). Both modes read from the same config; the only difference is the plan **source** (Stripe subscription on Cloud vs. license key on Self-Hosted) and request metering (on for Cloud, off for Self-Hosted).

> **Custom domains** are not plan-gated. They depend on Cloudflare for SaaS being configured for the deployment (see [Custom domain](/guides/custom-domain.md)) and are available regardless of plan once that configuration is present.