# Plans and limits

> Free and Pro entitlements, soft-limit behavior, and what never counts against you — generated from the source.

Allowances are pooled per organization. Project and member limits are hard; request and bandwidth limits are soft — published content is never taken offline because of an overage.

| Capability | Free | Pro |
|---|---:|---:|
| Price | €0 | €9/month or €90/year |
| Projects | 2 | 10 |
| Members | 2 | 5 |
| Asset storage | 1 GB | 25 GB |
| Monthly asset bandwidth | 25 GB | 500 GB |
| Monthly public API requests | 100,000 | 2,000,000 |
| Webhook endpoints | 1 | 25 |
| Max upload size | 50 MB | 500 MB |
| Revision retention | 30 days | Indefinite |

Entries, collections, drafts, and previews are unlimited on both plans. Management, preview, CLI, dashboard, SDK-management, and MCP calls never count toward the public request allowance — agent actions are not billing units.

## The `internal` plan

`planKey` has a third value, `internal`, and a client that parses it should accept it. It waives every allowance in this table and belongs to the organizations Myna runs on Myna — the one behind [the changelog](https://myna.sh/changelog). It is not sold, does not appear at checkout, and cannot be granted through the API; it is written directly to the database by an operator. Billing ignores organizations on it, so no provider event can move one on or off.

On an `internal` organization the usage report still returns real quantities, but every `limit` is `null` — the same value the API already uses for a metric it does not cap.

## Soft-limit behavior

At 80% of a soft allowance you get a dashboard and email warning; at 100% operation continues with a prominent warning; past 120% requests may be throttled — published content and assets stay online.