Compare
MockBase vs Mockoon
A genuinely good free desktop app — as long as local, or paying for Cloud, works for you.
Mockoon is a free, open-source desktop application (Electron-based) for defining and running mock APIs locally. It's one of the most established tools in this space, with a mature UI, OpenAPI import/export, and a scripting layer (data buckets, templating helpers) for more advanced setups.
| Feature | MockBase | Mockoon |
|---|---|---|
| Hosted endpoint, nothing to install | Live HTTPS endpoint in one click | Desktop app; hosting requires paid Cloud add-on |
| Usable without creating an account | 3 mocks, 10 routes, 2,000 requests/month, no account needed | No account needed to run it locally |
| Conditional matching (header, query, body) | 5 operators, priority ordering, path params | Rules by header, query, and body |
| Dynamic response templating | Sandboxed Jinja2 — request data, UUIDs, timestamps | Handlebars-based helpers, not Jinja2 |
| Automatic stateful CRUD | One toggle — full GET/POST/PUT/PATCH/DELETE lifecycle | Data buckets exist, but CRUD logic is hand-wired |
| Random failure injection | Weighted scenarios: status, latency, truncated or empty bodies, or a real connection reset | No built-in probabilistic failure rate |
| OpenAPI import & export | Import by paste, file or URL; export with inferred $ref schemas | Strong, well-supported import/export |
| Record & replay a real API | Proxies unmatched requests, captures them as routes | No built-in record-and-replay proxy |
| Live, remote request inspector | WebSocket stream: method, path, headers, body, latency, IP | Local request logs in the app, not a remote stream |
| GraphQL operation-name matching | Matches operationName, or the name parsed out of the query text | No documented operation-name-aware matching |
| SOAP/XML matching and responses | Reads envelope elements by name; raw XML responses, templating included | Documented XML/SOAP body rules; any response body |
| Binary file responses | Upload a file, served with its real Content-Type (300 KB cap) | Serves a file from local disk |
| Version history with rollback | Snapshot before every save, 30 versions, restore is itself undoable | Config is a file you version in git yourself |
| Deterministic rate limit simulation | N requests per window, per route, with Retry-After | No documented rate limit simulation |
| Outbound callouts (webhooks) | Fires a templated webhook after responding, with a delay | No documented outbound callout |
| API, CLI, or MCP server for managing mocks | Personal API key drives a dependency-free CLI (push/pull a JSON config) and a local MCP server (8 tools). Newer and smaller than most of the field below — see the honest comparison in the notes for each competitor. | Official CLI for years; an MCP command (list/start/stop local mocks) shipped in 2026 |
What Mockoon is good at
- Completely free and open-source for local use — no account, no quota, ever
- A polished desktop UI for hand-building detailed mock configurations
- OpenAPI import and export are first-class, well-supported features
- Runs fully offline, useful for air-gapped or privacy-sensitive environments
Where it differs from MockBase
- Mockoon's core product is a desktop app you install and run yourself — there's no shared URL a teammate, CI job, or mobile device can hit unless you also pay for Mockoon Cloud (plans start around $15/month with tiered request quotas).
- State across requests (data buckets) and CRUD-style behavior are built with templating helpers you wire up yourself, rather than a single toggle that gives a route full create/read/update/delete semantics automatically.
- There's no built-in probabilistic failure injection — you can script specific responses, but not "fail this route 15% of the time" as a one-field setting.
- Because it's a local app, there's no live remote request inspector to share with someone watching from a different machine — you see requests in the app you're already running.
- Its official CLI (@mockoon/cli) has run mocks from a data or OpenAPI file in CI for years, and a 2026 release added an MCP command an AI assistant can use to list, start, and stop local mocks — a mature, if narrower (local-mocks-only, no remote account) story than MockBase's API-key-driven CLI and MCP server.
Pricing
The desktop app is free and open-source, permanently. Mockoon Cloud (hosting, cross-device sync, AI-generated endpoints) is a separate paid add-on starting at roughly $15/month for a Solo plan with a capped number of instances and monthly requests.
Choose MockBase if
- You need a URL a teammate, mobile app, or CI pipeline can hit today, without installing anything
- You want stateful CRUD, chaos injection, and templating without hand-wiring helper scripts
- You want to watch requests arrive live, from a browser, without the app running on your machine
Choose Mockoon if
- Everything happens on one machine and a shared URL was never the point
- You want a fully offline tool with zero dependency on anyone else's server
- You're comfortable scripting your own dynamic/stateful behavior with Mockoon's helpers
Pricing, limits, and features for Mockoon were checked against its own pricing and documentation pages at the time of writing and may have changed since — see its current pricing page for the latest numbers. A feature marked as missing means it isn't documented, not that we tested it and it failed. MockBase is an independent tool and is not affiliated with, endorsed by, or sponsored by Mockoon. Spot something out of date? Tell us and we'll correct it.