---
title: Plans and limits
description: What each plan includes, covering seats, concurrent events, domains, features, and event sizes.
---

Your workspace subscription plan sets how many people can work with you, how many events you can run at once, and which features and event sizes are available. Wallet credits, which pay for event hosting and usage, are separate from the plan; see [Manage billing and credits](/organizers/how-to/manage-billing).

## Plans

| | Hobby | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Price | Free | $10/month | $25/month | Custom |
| Seats | 1 | 10 | 50 | 200 |
| Concurrent events | 1 | 3 | 10 | 25 |
| Custom domains | 1 | 5 | 20 | 50 |
| API access | ✗ | ✓ | ✓ | ✓ |
| Forms | ✗ | ✓ | ✓ | ✓ |
| Event audit log | ✗ | ✗ | ✓ | ✓ |
| Integrity findings | ✗ | ✓ | ✓ | ✓ |
| Export retention | 7 days | 30 days | 30 days | 30 days |
| On-demand exports per event, per day | 2 | 5 | 10 | 25 |
| Event sizes | Extra Small, Small | Extra Small to Large | All, up to Extra Large | All |

What each limit covers, and what you see when you hit it:

- **Seats**: accepted members in your workspace; pending invitations don't count toward the total. At the limit, the invite controls are disabled with *"Your plan's seat limit (N) is reached. Upgrade your plan to invite more members."*
- **Concurrent events**: live events and events still being set up both count toward this limit. Creating one more fails with *"You have reached your plan limit for concurrent events."*
- **Custom domains**: domains configured at the workspace level. At the limit, the **Add domain** button is replaced by a *"Domain limit reached"* notice showing your used/maximum count; see [Connect a custom domain](/organizers/how-to/connect-a-custom-domain).
- **API access** (Starter and above): per-event API keys for your own integrations. On Hobby the API keys page is unavailable, and moving to a plan without API access revokes an event's existing keys; see [Create API keys](/organizers/how-to/create-api-keys).
- **Forms** (Starter and above): workspace forms and their embeds. On Hobby, forms turn read-only: the share link and every embed show the closed state, and creating or editing a form is refused with *"Forms are available on Starter and above. Your existing forms and responses stay readable and exportable."* Reading, exporting, and deleting what you already collected all stay available; see [Collect responses with forms](/organizers/how-to/collect-form-responses).
- **Event audit log** (Pro and Enterprise): the per-event Audit log page. On other plans it shows *"Audit logs unavailable on current plan"* with a prompt to upgrade. The workspace Audit log, which records events, sign-in changes, domains, membership and billing changes, is available on every plan.
- **Integrity findings** (Starter and above): the per-event Integrity pages, where the platform surfaces suspected collusion for you to review. On Hobby the group does not appear.
- **Export retention**: how long each event data export stays downloadable, counted from the moment the archive is ready. Every plan gets the automatic export produced when an event ends; the plan sets how long you have to collect it. Changing plans doesn't move the deadline on archives you already have, since each one keeps the retention it was created with. See [Export event data](/organizers/how-to/export-event-data).
- **On-demand exports per event, per day**: exports you start yourself while an event is running. Past the limit the request is refused and tells you the number your plan allows. This number is also how many on-demand archives are kept per event: starting one beyond it expires the oldest. The automatic export at the end of an event is never limited and never expired early. Listing and downloading exports is limited to organization owners and admins.
- **Event sizes**: the Create Event form only offers the sizes your plan allows. A size outside your plan shows *"This event size isn't available on your current plan."* Submitting one anyway is rejected with *"Your plan does not allow this event size."*

The workspace **Usage** page tracks seats, events, and domains used against your plan's limits for the current period.

### Enterprise

**Enterprise** isn't a self-serve plan. On the upgrade page its price shows as **Custom** and, in place of a checkout button, its card has a **Contact sales** button. Clicking it sends your request (the button reads *"Sending…"*, then *"Request sent"*) and the team follows up about Enterprise pricing; there's no form to fill in.

## Event sizes

Every event has a size, chosen on the Create Event form and fixed for the event's lifetime; it's one of the choices [locked at creation](/organizers/reference/event-settings). The size sets the event's storage cap and Docker build-minute quota:

| Size | Available on | Storage | Build minutes |
|---|---|---|---|
| Extra Small | All plans | 20 GB | None |
| Small | All plans | 50 GB | 200 min |
| Medium | Starter, Pro, Enterprise | 150 GB | 400 min |
| Large | Starter, Pro, Enterprise | 400 GB | 800 min |
| Extra Large | Pro, Enterprise | 1024 GB | 1600 min |

Where the quotas surface: each event's **Usage** page shows storage used against the cap, and its **Image builds** page shows a **Build quota** card with Docker storage and build minutes used; see [Build challenge images](/organizers/how-to/build-challenge-images).

:::note[Storage is split between files and images]
The storage figure above is the event's total. On every size except Extra Small it's divided between two separate quotas (roughly four-fifths for challenge attachments and one-fifth for built Docker images), and each is enforced on its own. So a Small event's 50 GB isn't a single pool you can spend on either; running out of image storage won't be helped by having attachment space to spare. Extra Small events build no images, so their whole allowance goes to attachments.

The two meters are shown separately: attachments on the **Files** and **Usage** pages, images on the **Build quota** card.
:::

The included instance-hours and overage rates that come with each size are covered in [Usage, credits, and event sizes](/organizers/explanation/usage-and-credits).

:::note[Extra Small events are static-only]
The size selector says it directly: *"Extra Small CTF is for static challenges only."* On an Extra Small event the challenge editor rejects dynamic flags and container runtimes, there are no image builds or build minutes, and the container-related dashboard pages don't apply. Pick Small or larger if you want [container challenges](/organizers/tutorials/run-a-container-challenge).
:::

To move up a plan, use the **Upgrade** flow, covered in [Manage billing and credits](/organizers/how-to/manage-billing).
