Plans and capabilities
Restorm gates capabilities, never quotas. There is no numeric limit whatsoever: not on the number of requests, nor of projects, nor of collaborators on one file.
The Community edition is the complete foundation: every execution protocol, every import, scenarios in the interface, the firewall, the console, the mini browser, and the API designer — building models and routes, and generating code from the official and local templates.
The table
Section titled “The table”| Feature | Community | Pro | Enterprise | What it unlocks |
|---|---|---|---|---|
| Headless / CI scenarios | — | ✔ | ✔ | CLI / CI execution of scenarios |
| Step-by-step scenario debugging | — | ✔ | ✔ | Stepping and breakpoints in the scenario inspector |
| Built-in Git client | — | ✔ | ✔ | Built-in git and the git tools over MCP |
| Advanced MCP tools | — | ✔ | ✔ | Advanced MCP tools: scenarios, screenshots, interface automation, multiple instances, themes, layout, mini browser |
| Serve an API design as a mock | — | ✔ | ✔ | Serving a design as a live REST / GraphQL / SOAP / OData / gRPC mock |
| Export a design descriptor | — | ✔ | ✔ | Exporting a design as an OpenAPI 3.0 / 3.1 descriptor |
| Deduce the routes of a recording session | — | ✔ | ✔ | Recording sessions: captured calls become replayable requests (recording itself is open to everyone) |
| Secret vaults | — | ✔ | ✔ | Encrypted storage for secrets, injected at run time |
| Centralised firewall policies | — | ✔ | ✔ | Firewall rules managed and distributed by the team |
| Reassignable named seats | — | ✔ | ✔ | Reassignable named seats |
| Priority support | — | ✔ | ✔ | Priority handling of your requests |
| Single sign-on (SAML) | — | — | ✔ | SAML single sign-on |
| Directory provisioning (SCIM) | — | — | ✔ | SCIM directory sync |
| Audit logs | — | — | ✔ | A timestamped trail of actions and access, for compliance |
| Organization template library | — | — | ✔ | Your organization’s shared code-generation templates |
What you see when a capability is missing
Section titled “What you see when a capability is missing”Restorm does not hide restricted features, it shows them locked — so you know what exists:
- a restricted setting appears greyed out, with an invitation to move up an edition;
- the git surfaces are locked with the same invitation; in the Pro edition outside a git repository, the message becomes “Initialise your folder with git to use this feature”, with no purchase link — the plan is not the problem;
- a restricted MCP tool stays listed, with the
(Restorm Pro)suffix, and returns an explicit error; - headless execution exits with code 3 and a message that distinguishes “missing token”, “insufficient plan”, “invalid or revoked token” and “endpoint unreachable”.
The reasoning
Section titled “The reasoning”The purchase trigger is running in continuous integration. That is where Restorm goes from individual convenience to team tooling, and that is what a company pays for.
Everything else — exploring, calling, importing, mocking, building scenarios — stays free and unlimited, because a development tool you cannot try out seriously never gets adopted.
Up-to-date prices: restorm.app/pricing.