Plans and limits

A plan belongs to a workspace, and sets what its projects can do: how many there are, how often they deploy, who can open them, and how much of what viewers did you can see. This page lists every plan and limit, explains each one, and says exactly what happens when you reach it.

Limits are checked in one place, the platform's data layer, so the app, pitch and Claude's connector are refused the same things with the same words.

Every plan

Prices are before VAT, per seat where a plan has seats; a year costs ten months, so two months are free. Projects and viewer-hours are per seat on Pro and Team. A live app's time counts twice against viewer-hours. Paid plans cannot be bought yet. Whatever the plan, a project listed on the community admits 5 people at once at its public address.

Prices

Prices are in pounds, before VAT. Yearly is ten months' price: two months free.

• Free: £0.
• Pro: £4 a month, or £40 a year, for one person.
• Team: £5 a seat a month, or £50 a seat a year, for 2 to 5 seats. A sixth seat is Organisation.
• Organisation: by arrangement, for teams of more than 5. Contact sales: it is a team's plan, agreed with each team and never bought in the app, so it has no listed price.

Paid plans are coming soon

Every workspace starts on Free. The paid plans are defined, and every limit on this page already applies to them, but they cannot be bought yet: there is no checkout. Until there is, Roomi assigns a plan by hand, and a plan assigned that way counts exactly as a bought one will.

Everywhere a limit bites, the app and the refusal name the plan that would allow more and say that paid plans are coming soon, rather than offering an upgrade button that goes nowhere.

The limits

Projects

How many projects the workspace has at once: every project not deleted, paused ones included. Free and Pro have 5, and Team 7 a seat, so 21 for a team of three. Organisation has 200 unless its arrangement says otherwise; so do its other limits below.

It is checked when a project is created, which pitch deploy --commit does the first time it publishes under a new address. Past it, the project is not created, and the refusal gives Team's figure for one seat:

Free allows 5 projects. Team allows 7 — paid plans are coming soon.

Deleting a project frees its place at once. Its address stays held for 30 days, so links already sent can never open someone else's project.

Deploys a day

How many builds the workspace creates in any rolling 24 hours, across all its projects. Free has 2; the paid plans have no limit.

A build is counted when it is registered, which is what pitch deploy --commit does; the rehearsal, pitch deploy without --commit, never counts. Making an earlier build live again (a rollback, in the app's Builds tab) is not a deploy. The limit is checked before any bytes are uploaded and again when the build is registered:

Free allows 2 deploys in any 24 hours. Pro deploys without a limit — paid plans are coming soon.

Private links

Whether projects can have private viewer links: one link per viewer, naming them, with its own copy of the demo, an expiry and a revoke. Free has none; every paid plan has them.

On Free a project is an unlisted draft that only your workspace opens, with Preview as viewer, or a listed project at one public address (see The community). Making a link on Free is refused:

Free has no private viewer links: list the project on the community for one public address, or use Preview as viewer to see it yourself. Pro gives each viewer their own link — paid plans are coming soon.

Links per project

How many private links one project can have that still admit someone. No plan limits it today: Free's is zero because it has no private links, and the paid plans have no limit. Only links that still work count: a revoked or expired link frees its place, so a link that leaked can always be replaced.

Viewer-hours

The time viewers spend in your rooms in a calendar month (UTC), across every project in the workspace. Pro includes 50 viewer-hours a month, Team 100 a seat (so 300 for a team of three), Organisation 10,000. Free has none, because it has no private links: see Viewing on Free.

It is measured from visits, not from open tabs. The room counts the seconds a viewer spends on each app and page while its tab is visible, and a month's viewer-hours are those seconds summed over every visit that began in that month. Two rules apply on every paid plan:

• A live app counts twice. Time in a container demo uses two viewer-hours for every hour, because a live app costs far more to run than a static demo.
• At a public address, only live-app time counts. Time in a static demo at a listed project's public address is measured, but never taken from your allowance, so a stranger there can never close your private rooms. Time in a live app there is taken from it.

A tab left open in the background adds nothing. Analytics and the pipeline says how the room measures.

What happens as you use them:

• From 80%, the app shows a notice above every screen: "You have used 40 of this month’s 50 viewer-hours. At 50, your rooms stop taking new visits until 1 November."
• At the allowance, your rooms take no new visits until the month turns (UTC) or the plan changes. A viewer opening a link, or reloading the room, sees "This room is not taking visits right now" and, with your name in it, "Northwind's room has reached its viewing allowance for this month. Your link still works; please get in touch with Northwind directly." The page names no plan and no figure. No live demo starts or is kept awake. Anyone already in a room is not cut off: what they have open keeps working, a live demo until it next sleeps, and its time is still counted.
• New private links are refused while the month's hours are used:

Pro includes 50 viewer-hours a month, and this month's are used. Team includes 100 — paid plans are coming soon.

The refusal gives Team's figure for one seat. Deploys, pages and everything in the app keep working.

Viewing on Free

Free has no viewer-hours. Instead, a Free workspace's public addresses share 100 hours of viewing a month (UTC), measured as the time a seat in the room is held rather than the time a tab is visible. Past it, new visitors are turned away until the month turns. Nobody already in a room is cut off.

Viewers at once

How many people can be in one room at the same time. Free's is 5; the paid plans set no cap on a private link, where every viewer has their own copy.

The cap that applies in practice is the public address's: everyone at a listed project's public address shares one copy of the demo, so it admits five people at once on every plan. The sixth sees "This demo is full right now", and "Northwind's demo has as many people in it as it can take at once. Try again in a few minutes." A seat is given back as soon as a viewer closes the tab, or 45 seconds after their room stops checking in.

Each viewer turned away is a capacity bounce, counted once per visitor per hour however often they retry. You see this month's count on the project's Overview and in the plan panel in Settings, and from the third in a month the notice adds: "On a paid plan each viewer gets their own private link, and there is no cap on how many are in at once. Paid plans are coming soon."

Running containers

For a container demo: how many copies of one project's demo can run at once. Every open private link has its own copy, so this is how many viewers can be in a project's container demo together. Pro runs 5, Team 10, Organisation 50. It does not apply to static demos, which run in the viewer's browser.

Free runs static demos only, and no container starts on it. A container project's room on Free still opens, with its pages and materials; only the demo frame says the live demo is not available on this plan.

A viewer who arrives when the project is at its cap sees the same "full right now" page, and counts as a capacity bounce.

The platform also holds a ceiling of 50 containers at once across every project. A viewer who arrives while it is reached sees "The demo is starting — high demand, one moment." The room asks again every five seconds for a minute, then says "The demo is still in high demand. Try again in a moment.", with Try again.

A copy runs only while someone is using it. The room keeps it awake while its tab is visible and in use; hidden or untouched for ten minutes, it stops doing so, and three minutes later the copy stops. The viewer then sees "The demo paused while you were away." with Resume the demo, which starts a fresh copy. No copy runs for more than two hours at a stretch.

Custom domain

Team seats

Whether the workspace can invite other people into it. Team has 2 to 5 seats, each adding 7 projects and 100 viewer-hours a month, and more than 5 people is Organisation, for as many as its arrangement says. Free and Pro are for one person, and the app shows the invite form only on a plan that has seats. See Teams and invites.

Next steps

Whether the room offers the next steps you choose at the end of a visit (see Brand and next steps). On the paid plans it offers the steps you chose, in your order and your words. On Free a room offers only "Ask a question"; the choices you make are kept, and apply as soon as the workspace is on a paid plan.

At a listed project's public address, "Ask a question" is the only step offered, on every plan.

Branding

Whether rooms wear your brand: your name, accent colour and logo. On the paid plans they do. On Free a room carries a small "Made with Roomi" mark instead; the brand you set is kept, and shows as soon as the workspace is on a paid plan.

Analytics

Whether analytics are shown in full. On the paid plans you see every measure, chart and ranked list, and each viewer's journey. On Free the platform computes and sends total views and nothing else, and refuses a journey:

Free shows total views only. Pro shows each viewer’s visits in order — paid plans are coming soon.

The app draws the rest as a locked placeholder made of invented values, never your own numbers blurred. See Analytics and the pipeline.

The pipeline

Whether you work the pipeline: each viewer as a card with their signals, placed in a stage, marked won, lost or later, followed up and noted. On the paid plans you do. On Free the platform refuses all of it, including for links made while the workspace was on a paid plan:

Free has no pipeline. Pro shows each viewer’s stage, signals and follow-ups — paid plans are coming soon.

The app draws the board locked, from invented viewers. See Analytics and the pipeline.

History

How far back you can see what viewers did: their visits, events, comments, responses and the pipeline's evidence. Free shows the last 30 days, Pro the last 90, and Team and Organisation all of it. A comment thread shows if any message in it is inside the window. Build history and your own notes are never windowed.

Nothing is deleted: older history is only hidden, and moving to a plan with a longer window shows it again.

How a refusal looks

A request the plan does not allow is answered 402, with what the plan allows and which plan would allow more:

{
  "error": "Free allows 2 deploys in any 24 hours. Pro deploys without a limit — paid plans are coming soon.",
  "reason": "limit",
  "limit": "deploys",
  "plan": "free",
  "upgrade": "pro"
}

limit is one of projects, deploys, links, viewerHours or analytics. upgrade is the lowest plan that allows more, or null when none does.

The app shows error as it is. pitch prints it after the request and its status, for example POST /api/projects/:projectId/uploads answered 402: Free allows 2 deploys in any 24 hours. …. Claude's connector returns it to Claude as the tool's error. Errors lists every refusal.

Changing plan

When a workspace's plan changes, its projects are fitted to the new allowance: the most recently used run, up to the number the plan allows, and the rest are paused. A project's last use is the latest of when it was created, last deployed and last visited. A paused project is kept whole, but:

• its room admits nobody, on every request, by any link;
• it takes no deploys and no new links, refused 423 with "this project is paused: the workspace has more projects than its plan allows. It opens again when the plan allows it: ask Roomi to change the plan while paid plans are coming soon".

Moving to a plan that allows more resumes paused projects, most recently used first. Nothing is ever deleted because of a plan.

Private links made on a paid plan stop admitting anyone on Free; the app marks them Closed on Free. They are kept, and open again if the workspace moves back to a paid plan.

Suspension

Roomi can suspend a workspace, giving a reason that is recorded. While it is suspended, every project is paused, nothing deploys, no room admits anyone, and anything that creates or publishes is refused 423 with "this workspace is suspended by Roomi; contact support". The plan panel says: "This workspace is suspended by Roomi: nothing deploys and no room admits."

Restoring it resumes its projects, apart from any the plan does not allow.

Separately, Roomi can take down a single project (see The community): it is paused and hidden, and refuses deploys and links with "this project was taken down by Roomi; contact support".

Where you see usage

Settings, Usage, shows the plan and this month against it:

• Projects: how many of the plan's, and how many are paused.
• Viewer-hours this month: used against the allowance, until the first of next month, or "Not metered on this plan".
• Deploys, last 24 hours: against the plan's limit, or "no limit".
• Viewers at once: the cap, and whether it is per private link or at the public address only.
• Turned away, on a capped plan: this month's capacity bounces.

The side bar's meter shows projects against the plan. GET /api/billing returns the same reading (see HTTP API).

Other bounds

These apply on every plan, and are not plan limits:

A free project nobody has visited in 30 days may be cleaned up by Pitch Product: deleted as its owner would delete it, by a person, never automatically.