Plans and quotasSoon
Plans are by audience: Free for trying Mulno, Indie for a small team, Team per seat. Only reviewers take a seat. Testers never do, whether you send a build to five friends or five hundred players. During the beta every studio starts on Free, and we agree a paid plan's price with the studio, at or below the most the first row of the table shows. It is the exact table the platform enforces, and the limits that aren't on the Pricing page.
You can't buy a plan yetPayment has only been tested
Workspaces and billing open with app.mulno.com, so while the beta runs we set a studio up by email and agree a paid plan's price with it. Checkout is built on Paddle's sandbox and was completed there once, end to end; it hasn't taken a real payment. Without the platform, everything local is unmetered: recording, Studio on your own folders, and mulno mcp.
Workspaces and plans live at app.mulno.com. A new account starts on Free once we let you in from the waitlist, and Indie and Team can be bought only after Paddle has approved the site for payments; their price is the one we agree with the studio during the beta. Checkout is built on Paddle's sandbox and was completed there once, end to end; it hasn't taken a real payment. Without the platform, everything local is unmetered: recording, Studio on your own folders, and mulno mcp.
1. What each plan includes
| Free | Indie | Team | |
|---|---|---|---|
| Most a plan costs | Free | Up to $29 a month, or $279 a year | Up to $49 per seat a month, or $39 per seat a month billed yearly ($468 per seat a year) |
| Reviewer seats | 1 | 3 | As many as you buy |
| Active campaigns | 1 | 5 | Unmetered, fair use |
| Remote sessions a month | 20 | 200 | Unmetered, fair use |
| Mulno Cloud storage, for builds and sessions | 15 GB | 250 GB | 250 GB per seat, pooled |
| Sessions kept in Mulno Cloud | 14 days | 1 year | No fixed number, fair use |
| Projects in a workspace | 3 | 10 | Unmetered |
| Builds in a project | 20 | 200 | Unmetered |
| Per-tester mark and your own overlay on the picture | The generic mark only | Included | Included |
- A Private bucket works on every plan, Free included. It costs you storage, not us, and Mulno Cloud's quota doesn't apply to it. Free's one active campaign and 20 remote sessions a month still do.
- Extra Mulno Cloud storage on a paid plan is agreed with the studio during the beta Soon. Builds count toward the quota.
- Education (free for verified teachers) and Enterprise (SSO, SCIM, an offline license, a security review) are planned, not sold.
2. Limits you'll meet
Each of these refuses in words that name your plan and what lifts it. What each one counts, and whether the code enforces it today:
- Seats (enforced). An invite, or an acceptance, past the plan's seats is refused, such as "Indie includes 3 reviewers — upgrade for more."
- Free's campaign and session caps (enforced). One active campaign, and 20 codes redeemed in a rolling 30 days, not a calendar month. The broker checks both when a tester redeems a code. Indie's five active campaigns and 200 sessions a month are not enforced yet: they are what the plan promises, and nothing stops a sixth. Team's are unmetered.
- Storage (enforced, builds and sessions both count). A push that would take a workspace over its Mulno Cloud storage is refused before any row is written, and so is an upload link that would push a pending upload over it. A build's size is charged when its upload link is signed, at the size signed. An admin can delete a build that no branch has live (through the api, not a Studio screen yet), which gives its room back. The other fixes are a higher plan or your own bucket.
- Builds and projects (enforced). At most 20 builds in a project on Free and 200 on Indie, and 3 projects in a workspace on Free and 10 on Indie. A deleted build no longer counts, so the cap is on the builds you keep; an admin deletes one that no branch has live. A build's manifest is capped per plan as well (256 KB on Free, 2 MB on Indie, 8 MB on Team).
- Distinct chunks (enforced). A workspace can reference at most 20,000 different chunks on Free and 150,000 on Indie, summed over all its projects. Team has no cap under fair use.
- Retention (enforced). Mulno Cloud keeps a session for the plan's number of days (14 on Free, a year on Indie, no fixed number on Team), counted from when it finished uploading. Then the session is hidden from everyone and its files are deleted for good 30 days later; until then an admin can restore or export it (not a session a tester's request is hiding: restore it first). Builds are never deleted because of a plan. An owner or admin can also delete one session sooner from its review: hidden now and gone 30 days later, or deleted right away with no undo. A session a tester asked to have deleted on Mulno's deletion page is hidden at once and deleted for good 30 days later, unless you restore it; a plan change's 30-day hold doesn't delay that. A Private bucket's retention is up to you. The workspace's audit log is kept a year, or the plan's number if longer.
3. Seats, sign-in and working offline
A seat is a named person who signs in to review. Testers redeem an invite code and never become a member, so nothing can turn a tester into a seat. The web app checks your seat when you sign in. A desktop Studio that carries the platform's screens (the shipped Studio 0.4.1 doesn't yet) keeps working offline for up to 30 days on a signed token it can verify without a network. Removing a member revokes their access within about a minute for anyone online.
4. Paying
Paddle is the merchant of record: it sells the plan, takes payment and handles tax; the seller is Somnolent Team Limited, a Thai company. During the beta we agree a paid plan's price with each studio, at or below the most the first table shows; when we have agreed it we set up your plan with you, and Paddle shows your tax before you pay. You start a paid plan and cancel it from your workspace's Billing screen. Changing seats or switching plans on a running subscription isn't built (it will go through Paddle's customer portal), and invoices and payment methods aren't shown in Mulno yet. Read the DPA and subprocessors before you put a real tester's data on Mulno Cloud.