# Plans

> The four Lumin tiers, what each one caps, and what is enforced today.

Canonical: https://docs.getlumin.dev/plans/

Lumin has four flat tiers. A tier caps the number of **projects** and **services** you run, and sets how long Lumin keeps your data. There is no per-gigabyte charge and no seat charge.

| | Hobby | Solo | Team | Studio |
|---|---|---|---|---|
| **Price** | €0 | €19 | €49 | €99 |
| **Projects** | 1 | 1 | 3 | Unlimited |
| **Services** | 1 | 5 | 15 | 50 |
| **Retention** | 7 days | 30 days | 30 days | 30 days |
| **Alerts** | — | Yes | Yes | Yes |
| **Support** | — | — | Email, priority | Email, priority |

Prices are per month and exclude VAT. Logs, metrics, sessions from web and mobile, and uptime checks are on every tier, Hobby included.

An alert rule watches a metric or a log pattern. Slack is the delivery channel today. An uptime check shows its status on the dashboard, but it does not fire an alert yet.

## Why services and not gigabytes

You can count your services today. Nobody can predict their log volume, and a cap you cannot predict turns a flat price back into a meter. So the tier caps the number you already know.

A **service** is one value of the `service` field on a log row, or one scrape target. The agent derives it from the container name, or from the `lumin.service` label if you set one — see [Container labels](https://docs.getlumin.dev/agent/labels/).

## Studio and client work

Studio is for an agency or a freelance operator who runs machines that belong to someone else. The shape is one project per client:

- A project is already the tenancy boundary, so one client's data never reaches another's. See [Projects & API keys](https://docs.getlumin.dev/concepts/projects-and-api-keys/).
- Each client's hosts run the agent with that project's key.
- Each project gets its own Slack alert route.
- One bill covers every client.

## What is enforced today

Billing is live: you subscribe to a paid tier and manage it under **Account → Billing**. On Lumin Cloud, the API enforces the tier:

- **Projects.** Project creation stops at the cap of your tier. If a downgrade or a cancellation leaves the workspace over the cap, the existing projects keep working — you only cannot create new ones.
- **Retention.** The retention window is the window of your tier. The sweeper removes older data automatically. See [Retention](https://docs.getlumin.dev/concepts/retention/).
- **Alerts.** On Hobby you cannot create or enable an alert rule, and existing rules stop evaluating.
- **Services.** Lumin counts the distinct services that sent data in the last 30 days, and shows the count under **Account → Billing**. The count warns when you are over your tier; it never blocks ingest.

A switch to a smaller tier runs a check first: the workspace must fit the project cap of the target tier, or the switch is refused with the reason. A move to Hobby is a cancellation at the period end, through the billing portal.