Local mock APIs from an OpenAPI contract: Prism, Microcks, Counterfact and Mockoon

Choose Prism when your contract’s examples should drive the mock, with per-request control of examples and errors. Its upkeep has slowed. Microcks is the better-governed alternative if your team already runs containers.

PRACTICAL PICKSPreferredPickOur Preferred PickContract-first frontend mocks$0

Prism CLI

Reads your OpenAPI file directly, serves its examples, and lets a request choose a named example or error with a Prefer header. Listens only on your own computer by default.

Narrow lead over Microcks. Mainly maintenance releases since April 2025; the current package needs Node.js 24.18 or later.

Why Prism is our Pick
Newcomer assessment

No Rising Star selected

Our search found no newer tool with confirmed release, platform, contract-response and safe local-use evidence together.

We could not establish every requirement for a newcomer recommendation.

Who is this article for? Small frontend teams with an OpenAPI contract that need repeatable local HTTP responses, including error states, before the backend exists.

About 25 min read

What Preferred Pick, Rising Star and Ready to Rock mean

The quick list

Start with Prism when your contract should be the mock. Choose Microcks for container-based rules, or consider Counterfact and Mockoon for behaviour you maintain separately.

All four are free, open-source tools that need no account for local use. Pricing and licences checked November 6, 2026: Apache 2.0 for Prism and Microcks, MIT for Counterfact and Mockoon. Mockoon also sells a self-hosted Pro product, and Prism’s maker sells hosted mocking, both outside this comparison. Setup and maintenance still take team time.

The comparison at a glance

Compare how each tool turns your contract into responses, what it takes to run safely on your own computer, and its 2026 maintenance and security record.

Prism is our choice for contract-first frontend mocks, followed by Microcks, Counterfact and Mockoon. Prism’s lead over Microcks is narrow. This order covers the products with complete scores.

Local OpenAPI mock servers for a small frontend team
FeaturePrism CLIMicrocksCounterfactMockoon CLI
Best fitPreferred Pick: a frontend team that wants its OpenAPI file to be the mock, with nothing else to maintainA team that already runs containers and wants richer mock rules under long-term open governanceProgrammable frontend mocks; Prism remains our choice when the contract should be the only artifactA team willing to hand-build rule-based mocks in a separate Mockoon file
Cost and licence$0; Apache 2.0$0; Apache 2.0; CNCF incubating project$0; MIT$0; MIT
Which response you get by defaultThe first example in the contract; without one, static values built from the schemaThe example whose name matches your request values (path or query parameters)Generated sample responses; customize the generated route code for specific behaviourStarted from the file: a body generated from the schema, not your examples. After import: a generated default, with each example added as a response that is not served until you change the default or add rules
Choosing another example or an errorSend a Prefer header (example=name or code=503) or the matching __example or __code query parameterSend request values that match a named example; header-based selection, scripts or a fallback response need configuringThe October 19 documentation selects named examples with .example(name) in route code; custom errors need codeEdit the native file: change the default response or add rules on headers, query parameters or body
Network exposure by defaultListens on 127.0.0.1 onlyDocker publishes the port on every network interface unless you add 127.0.0.1 to the port mappingQuick start uses localhost:3100 but does not establish the listening address; confirm loopback-only configurationListens on every interface unless you set --hostname 127.0.0.1; admin API on by default, token-protected since 9.7.0
Security recordNo advisory published for Prism itself; a dependency flaw published in February 2025 (CVE-2025-1302) was addressed in 5.14.3 in October 2025One advisory: before 1.10.0, import and export endpoints allowed non-administrator access (2024)No published repository advisory listed November 6; this does not establish dependency safetyFive advisories since March 2025, all fixed: critical prototype pollution (9.9.0), unauthenticated admin API with open cross-origin access (9.7.0), denial of service (9.8.0), two path traversals (9.2.0, 9.7.0)
Reader reviewsNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a reviewNo reviews yet. Write a review

Counterfact sources, checked November 6, 2026: repository and MIT licence, releases, issues and advisories. The current quick start confirms generated sample data and code-based customization; named-example details retain their October 19 evidence date.

All four are free to run locally. None of these sources measures speed, failure rates or behaviour on large contracts. Whichever you choose, keep the mock on 127.0.0.1 and keep it updated. Original capability findings checked October 19, 2026; local pricing and Counterfact checked November 6, 2026.

All features and sources 14 criteria

Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.

How your contract becomes a mock

Show 4 criteria
How your contract becomes a mock
FeaturePrism CLIMicrocksCounterfactMockoon CLI
Starting from your OpenAPI fileprism mock reads the file directly and reloads it when it changesUpload the file in its web interface; mocks appear at /rest/<API name>/<version>/…Generates editable TypeScript routes from the contract and starts a local HTTP serverStart the CLI from the file directly, or import it into a native Mockoon file
Which response you get by defaultThe first example in the contract; without one, static values built from the schemaThe example whose name matches your request values (path or query parameters)Generated sample responses; customize the generated route code for specific behaviourStarted from the file: a body generated from the schema, not your examples. After import: a generated default, with each example added as a response that is not served until you change the default or add rules
Choosing another example or an errorSend a Prefer header (example=name or code=503) or the matching __example or __code query parameterSend request values that match a named example; header-based selection, scripts or a fallback response need configuringThe October 19 documentation selects named examples with .example(name) in route code; custom errors need codeEdit the native file: change the default response or add rules on headers, query parameters or body
OpenAPI versions documented2.0, 3.0 and 3.1, plus Postman collections; an open May 2026 report says some 3.1 schemas are validated by older rulesNo explicit statement found; its conventions page uses a 3.1.0 exampleCurrent quick start lists Swagger 2.0 and OpenAPI 3.0, 3.1 and 3.22.0 and 3.0, per the CLI guide
Sources for how your contract becomes a mock

Documentation and issues read October 19, 2026: Prism CLI guide, mocking guide, README and issue 2797; Microcks first REST mock, OpenAPI conventions and dispatching; Mockoon CLI guide, issue 962 and issue 992. Documented behaviour, not measured reliability.

Running it on your computer

Show 3 criteria
Running it on your computer
FeaturePrism CLIMicrocksCounterfactMockoon CLI
What you need to run itNode.js 24.18 or later for the current npm package; standalone binaries up to 5.15.11; Docker imageDocker or Podman, using its all-in-one “uber” imageNode.js 22.22 or newer, per the November 6 READMENode.js 18 or later; Docker image; optional desktop app
Network exposure by defaultListens on 127.0.0.1 onlyDocker publishes the port on every network interface unless you add 127.0.0.1 to the port mappingQuick start uses localhost:3100 but does not establish the listening address; confirm loopback-only configurationListens on every interface unless you set --hostname 127.0.0.1; admin API on by default, token-protected since 9.7.0
Cost and licence$0; Apache 2.0$0; Apache 2.0; CNCF incubating project$0; MIT$0; MIT
Sources for running it on your computer

Read October 19, 2026: Prism installation and npm package metadata; Microcks getting started and Docker’s port publishing guide; Mockoon CLI guide and admin API advisory.

Maintenance, security and stewardship

Show 4 criteria
Maintenance, security and stewardship
FeaturePrism CLIMicrocksCounterfactMockoon CLI
Release evidence: October 19 for original tools; November 6 for Counterfact5.16.0, July 17, 20261.15.0, August 5, 20263.2.2, November 5, 2026; checked November 69.9.0, September 16, 2026
Recent maintenanceReleases since April 2025 are mainly dependency and build fixes; 5.16.0 added install-time analytics you can switch off; 115 open issuesFeature releases roughly every three to six months; CNCF incubating since May 2026; 34 open issuesActive feature and bug-fix releases; 3.2.2 fixes shared-schema memory use and malformed numeric queriesFive feature releases in 2026, from 9.5.0 in January to 9.9.0 in September; 28 open issues; funded by sponsors and Pro licences
Security recordNo advisory published for Prism itself; a dependency flaw published in February 2025 (CVE-2025-1302) was addressed in 5.14.3 in October 2025One advisory: before 1.10.0, import and export endpoints allowed non-administrator access (2024)No published repository advisory listed November 6; this does not establish dependency safetyFive advisories since March 2025, all fixed: critical prototype pollution (9.9.0), unauthenticated admin API with open cross-origin access (9.7.0), denial of service (9.8.0), two path traversals (9.2.0, 9.7.0)
Who maintains itSmartBear, which agreed to buy Stoplight in 2023 and lists Prism among its open-source productsMicrocks community under the Cloud Native Computing FoundationPatrick McElhaney and contributors; MIT source repositoryThe Mockoon project, without external funding
Sources for maintenance, security and stewardship

Read October 19, 2026: Prism changelog, analytics change and repository; Microcks 1.15.0 release, CNCF announcement and advisory; Mockoon 9.9.0 release and advisories. Open-issue counts are from each repository page.

Flexibility and exit

Show 2 criteria
Flexibility and exit
FeaturePrism CLIMicrocksCounterfactMockoon CLI
Beyond static examplesRequest validation, generated data (repeatable with --seed), validation proxyHeader, body and script dispatchers, stateful mocks, proxy fallback, contract tests; also AsyncAPI, gRPC and GraphQLEditable TypeScript behaviour, shared context, selective proxying and request validationRules on headers, query and body; sequential or random responses; templating; CRUD routes; proxy
What you keep and maintainOnly the OpenAPI contractThe contract, plus optional x-microcks extensions or a separate metadata fileKeep the contract and generated TypeScript routes, lockfile and custom behaviourA native Mockoon JSON file; its OpenAPI export drops rules
Sources for flexibility and exit

Read October 19, 2026: Prism mocking guide; Microcks dispatching and stateful mocks; Mockoon response rules, CRUD routes and OpenAPI compatibility.

Earlier hands-on check, October 1, 2026

Show 1 criteria
Earlier hands-on check, October 1, 2026
FeaturePrism CLIMicrocksCounterfactMockoon CLI
Earlier hands-on check, October 1, 2026 (historical)5.16.0 on Node 24.18.0: default returned the ready example; Prefer headers returned the pending example and the 503 body; unknown path 404Not part of that checkNot part of that check9.9.0 on Node 22.23.3: generated body with empty id for all three requests; Prefer headers ignored; unknown path 404; import kept the named examples as extra responses
Sources for earlier hands-on check, october 1, 2026

Historical observation from a small local check run on October 1, 2026, before Practical Picks adopted its research-only method on October 3. It sent four requests to each tool using one fictional OpenAPI 3.0.3 contract, and it did not decide any recommendation. Microcks was added to this comparison on October 19, 2026 and was not part of it. Earlier check record, October 1, 2026.

What matters when choosing

Prism CLI is our Preferred Pick for a small frontend team that wants local mock responses straight from its OpenAPI contract, but its lead is narrow. Prism reads the contract file you already keep and serves its examples with no second mock file to maintain: by default the first example for each response, and any named example or documented status code when a request asks for it with a Prefer header, such as Prefer: example=pending or Prefer: code=503. It listens only on your own computer (127.0.0.1) unless you tell it otherwise, and it is free under the Apache 2.0 licence. The compromises are in its upkeep. SmartBear, which agreed to buy Prism’s maker Stoplight in 2023 and now lists Prism among its open-source products, has shipped mainly dependency and build fixes since the last release with new mocking features in April 2025, and the project had 115 open issues on October 19, 2026. Version 5.16.0, from July 17, 2026, added analytics, which the project describes as anonymized, that run when the package is installed and can be switched off. The current npm package needs Node.js 24.18 or later. On our five-point scale Prism led Microcks by 0.2, less than half a scoring step, and that lead depends on our judgement that Prism’s slow maintenance is an ordinary trade-off for a local development tool rather than a serious one. Prism CLI guide, mocking guide, changelog, repository

Consider Microcks if your team already runs containers and puts long-term stewardship or richer mock behaviour ahead of a quick start. It is an Apache 2.0 project of the Cloud Native Computing Foundation, which accepted it as an incubating project in May 2026, and its releases are steady: 1.15.0 arrived on August 5, 2026. It runs locally as a Docker or Podman container, serves your contract’s examples by matching each request to the example with the same name, and can add header-based selection, scripted rules and stateful mocks. For this reader it costs more effort: you need a container runtime, your examples must follow its request-and-response naming convention, mock addresses carry a /rest/<API name>/<version> prefix, and the docker run command in its quick start publishes the port on every network interface unless you add 127.0.0.1 to the mapping. Getting started, OpenAPI conventions, CNCF announcement

Mockoon is popular, but it is a weaker fit when the contract should drive the mock. Started directly from an OpenAPI file, its CLI serves bodies generated from the schema rather than your examples; a request to change that has been open since March 2023. Importing the file adds each example as an extra response, but you then choose between them by editing a separate Mockoon file or writing rules. Those rules, with templating and stateful routes, are its real strength. Mockoon also published five security advisories between March 2025 and September 2026, including a critical flaw fixed in 9.9.0 and an admin interface that, before 9.7.0, was switched on by default and answered requests from any website without authentication. All are fixed. If you use it, run 9.9.0 or later and set --hostname 127.0.0.1. CLI guide, issue 992, security advisories

No Rising Star selected. We have not established a newer option that meets the same requirements for contract-driven responses and safe local use. The candidates we found lacked confirmed first-release, platform, contract-import or safety evidence needed for a recommendation. This does not change our recommendation to start with Prism for this job.

Prism CLI

Preferred Pick · contract-first frontend mocks

$0Apache 2.0 · SmartBear open-source project

Choose Prism when your OpenAPI file should be the mock, with nothing else to keep in step. Send a Prefer header for alternate examples and errors, keep it updated, and switch off its install-time analytics if you prefer.

Reasons to choose it

  • Serves the contract’s own examples with no second mock file
  • Named examples and error statuses chosen per request with a header
  • Listens only on 127.0.0.1 by default

What to watch

  • Mainly dependency and build fixes since April 2025; 115 open issues
  • The current npm package needs Node.js 24.18 or later
  • Your app must send a header or query parameter for each non-default state

Run prism mock with your contract and Prism serves every operation it describes. By default it uses a static strategy: the response’s example if there is one, otherwise values built from the schema, such as a property’s own example or default. A request can ask for something else. Prefer: example=pending returns the example named pending, Prefer: code=503 returns the documented 503 response, and Prefer: dynamic=true returns generated data; the same choices work as __example, __code and __dynamic query parameters when your app cannot set headers. Generated data can be made repeatable with --seed, Prism validates incoming requests against the contract, and it reloads when the file changes. Its guide warns that if a request fails validation, Prism may answer with an error instead of the example you asked for. Your frontend has to send the header or query parameter for each non-default state; if it cannot, a rule-based tool fits better. CLI guide, mocking guide

Prism’s README lists OpenAPI 2.0, 3.0 and 3.1 and Postman collections. Two open reports touch on that: one from May 2026, with no maintainer reply by October 19, says some OpenAPI 3.1 schemas are validated with older JSON Schema rules, and one from January 2026 says examples inside an anyOf property are ignored. The npm packages for 5.16.0 require Node.js 24.18.0 or later, although the README still says 18.20.1; follow the package. Standalone binaries for Linux, macOS and Windows are attached to releases up to 5.15.11 (June 3, 2026) but not to 5.16.0, and a Docker image is documented. A bug that stopped Prism from loading a contract by URL on Node.js 24 was fixed in 5.15.1 in March 2026. README, 3.1 validation report, anyOf report, installation, URL-contract issue

Read the full Prism CLI analysis and sources

SmartBear announced an agreement to buy Stoplight in August 2023 and now lists Prism on its open-source page. Prism’s recent history reads like maintenance mode. Its 2026 releases moved it to Node.js 24, fixed builds and updated dependencies; the last release that added mocking features was 5.14.0 in April 2025. A flaw in the jsonpath-plus library it depends on, published in February 2025 (CVE-2025-1302), was addressed in 5.14.3 in October 2025; we found no assessment of whether Prism’s own use of the library was exploitable, and no security advisory has been published for Prism itself. On October 19, 2026 the repository showed 115 open issues and 32 open pull requests. Version 5.16.0 added Scarf, a service that the README says collects “anonymized installation analytics” and runs only during installation. To opt out, set SCARF_ANALYTICS=false when you install or add "scarfSettings": {"enabled": false} to your project’s package.json. SmartBear’s announcement, SmartBear open source, changelog, analytics change, CLI package README

In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Prism CLI 5.16.0 on Node.js 24.18.0 served one fictional OpenAPI 3.0.3 contract on 127.0.0.1. A plain request returned the contract’s ready example, Prefer: example=pending returned the pending example, Prefer: code=503 returned the documented 503 body, and a path outside the contract returned 404. That matches the documentation. It was four requests to one small file and says nothing about large contracts, validation, speed or security. Earlier check record, October 1, 2026

Used Prism CLI? Share your experience to help other readers choose.

Microcks

Also consider · teams that already run containers

$0Apache 2.0 · CNCF incubating project

Choose Microcks when your team already uses Docker or Podman and wants long-term open governance, scripted or stateful mocks, or contract tests. Map its port to 127.0.0.1 and pair your request and response examples by name.

Reasons to choose it

  • Strongest stewardship: CNCF incubating since May 2026
  • Header, body and script dispatchers, plus stateful mocks
  • Also mocks AsyncAPI, gRPC and GraphQL

What to watch

  • Needs a container runtime and a contract upload
  • Examples must be paired by name with request values
  • Mock addresses carry a /rest/<API name>/<version> prefix

Microcks turns OpenAPI contracts, and also AsyncAPI, gRPC, GraphQL, Postman and SoapUI definitions, into live mocks. On your own computer it runs as one container: its quick start uses docker run -p 8585:8080 -it --rm quay.io/microcks/microcks-uber:latest-native with Docker or Podman, after which you upload the contract in its web interface. Docker’s documentation explains that a port mapped without a host address is published to all of the computer’s network interfaces, so use -p 127.0.0.1:8585:8080 to keep the mock to yourself. Mock addresses include the API’s name and version, for example http://localhost:8585/rest/Petstore+API/1.0.0/my/pets, so your app’s base URL changes accordingly. Getting started, first REST mock, Docker port publishing, README

Microcks builds its mock from pairs of examples. A request example and a response example with the same name belong together (“related parts must have the same key”), and Microcks uses only complete pairs. It then works out which request values decide the response, such as a path or query parameter, so GET /tasks/task-8 can return a different example from GET /tasks/task-7. If your contract has response examples but no matching parameter examples, you will need to add them. Header-based selection (since 1.11), JSON-body matching, Groovy or JavaScript scripts, a fallback response and stateful mocks that remember data between requests (since 1.10.0) are all available, set in its interface or with x-microcks-operation extensions in the contract. We found no explicit statement of OpenAPI 3.1 support, though its conventions page uses a 3.1.0 example, and we did not establish what it returns for an operation without examples. OpenAPI conventions, dispatching, stateful mocks

Read the full Microcks analysis and sources

Its stewardship is the strongest in this comparison. The Cloud Native Computing Foundation accepted Microcks as a sandbox project in June 2023 and as an incubating project in May 2026; its announcement reports 167 active contributors from 35 organisations in 2025 and more than 2.5 million container image downloads that year. Releases arrive every three to six months: 1.13.0 in October 2025, 1.14.0 in April 2026 and 1.15.0 on August 5, 2026. The repository showed 34 open issues on October 19, 2026. One advisory has been published: before 1.10.0, its import and export endpoints were open to non-administrators (CVE-2024-44076, rated high, August 2024). Microcks was added to this comparison on October 19, 2026 and was not part of our earlier hands-on check of October 1, 2026. CNCF announcement, CNCF project page, 1.15.0 release, advisory

Used Microcks? Share your experience to help other readers choose.

Counterfact

Evaluated alternative · programmable frontend mocks

$0MIT · generated TypeScript routes

Consider Counterfact when you want to program errors and custom behaviour alongside your contract. Prism remains the simpler choice when the contract should be the only mock artifact.

Reasons to choose it

  • Generates editable routes from an OpenAPI contract
  • Selective proxying to real services
  • Recent fixes for request-schema memory use and numeric validation

What to watch

  • Custom responses mean maintaining generated route code
  • Needs Node.js 22.22 or newer
  • The quick start does not establish a loopback-only listening address

Counterfact takes an OpenAPI contract, generates editable TypeScript routes and starts a local HTTP server. Choose it when your frontend needs custom errors, shared state or a mixture of simulated and real responses, and your team is comfortable maintaining code alongside the contract. Its documentation starts with generated sample responses; the October 19 documentation described selecting a named example with .example(name) in route code rather than a request header. That extra artifact is why Prism remains our choice when the contract itself should be the mock. Repository and MIT licence, checked November 6, 2026; example-selection documentation checked October 19, 2026.

The current README requires Node.js 22.22 or newer. Version 3.2.2, released November 5, addresses excessive memory use with shared request schemas and malformed numeric query values. These are the maker’s reported fixes, not measured reliability. Its issue list also contains a November 5 report about module-loader identity, filed by a project account, and its security page lists no published advisories; neither establishes that the current package is free of defects. The quick start gives a localhost URL without documenting the listening address, so confirm a loopback-only setup before using sensitive contracts. Release notes, issues, security advisories, checked November 6, 2026.

Used Counterfact? Share your experience to help other readers choose.

Mockoon CLI

Evaluated alternative · hand-built rule-based mocks

$0MIT · independent project

Mockoon suits teams that would rather build mock behaviour by hand in its own format than serve the contract as written. Run 9.9.0 or later, bind it to 127.0.0.1 and check its default responses.

Reasons to choose it

  • Rules on headers, query and body; sequences and templating
  • CRUD routes keep data between requests
  • Desktop app for editing mocks

What to watch

  • Started from a contract, serves schema-generated bodies, not your examples
  • Choosing an example or error means editing a separate Mockoon file
  • Five security advisories since March 2025, all fixed

Mockoon’s CLI can start from its own data file or from an OpenAPI 2.0 or 3.0 file, and its guide warns that OpenAPI cannot express every Mockoon feature. Started from the contract, it serves a body generated from the schema rather than your examples: a user asked in March 2023 for the CLI to return the contract’s examples, and that request was still open on October 19, 2026, labelled as needing more interest. Mockoon’s import adds one response per example, but the maintainer explained in 2023 that the schema-generated response stays the default and the others are not rules, so only the default is served until you change it or add rules. That means a second, Mockoon-specific file to keep in step with the contract. Its compatibility page adds that rules are lost when you export back to OpenAPI and that import and export are “not a way to share your mock APIs”. In December 2025 a user’s import of a contract of about 105,000 lines ran out of memory, and the maintainer suggested splitting the file. CLI guide, issue 992, issue 962, OpenAPI compatibility, large-import discussion

Once you work in its own format, Mockoon is particularly flexible. Responses can be chosen by rules on headers, query parameters or the request body, served in sequence or at random, and filled with templates; CRUD routes keep data between requests; and there is a desktop app for editing it all. It is free under the MIT licence, runs on Node.js 18 or later or as a Docker image, and has had five feature releases in 2026, from 9.5.0 in January to 9.9.0 on September 16. The project says it is maintained without external funding, relying on sponsors and its paid Pro product. Response rules, multiple responses, templating, CRUD routes, repository

Read the full Mockoon CLI analysis and sources

Its security record needs attention. Mockoon has published five advisories since March 2025, all fixed: a path traversal through templated file paths (high, fixed in 9.2.0); an admin interface that was on by default, allowed requests from any website and had no authentication, so a page open in your browser could rewrite the mock or read its secrets (high, published June 22, 2026, fixed in 9.7.0); a second path traversal (moderate, 9.7.0); unbounded request bodies that could exhaust memory (high, 9.8.0); and prototype pollution through multipart form fields (critical, published September 16, 2026, fixed in 9.9.0). The admin interface is still on by default but now requires a token, and --disable-admin-api turns it off. The advisory describes the default listening address as 0.0.0.0, every network interface, so set --hostname 127.0.0.1. The quick fixes are a good sign; the number and severity are what to weigh. Advisories, admin interface advisory, multipart advisory, admin API

In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, Mockoon CLI 9.9.0 on Node.js 22.23.3, started directly from the same fictional contract on 127.0.0.1 with its admin interface disabled, returned a generated body with an empty id and state: pending for a plain request and for both Prefer requests, and 404 for a path outside the contract. Its import command saved the ready and pending examples as extra responses behind a generated default. That matches what its maintainer describes above; rules and export were not tried. Earlier check record, October 1, 2026

Used Mockoon CLI? Share your experience to help other readers choose.

Which product are we missing?

Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.

Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.

Suggest a product

Opens an email draft with this article attached as a link. Nothing is sent until you send it.

No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.

What people are saying

We have no Practical Picks reader reviews for these tools yet.

The clearest user complaint is Mockoon’s handling of examples. The March 2023 request put it plainly: “The response is never one of the examples defined in the openapi yml, but always a generated one.” For Prism, the open reports concern OpenAPI 3.1 validation and examples inside anyOf, and both have gone without a maintainer reply. Mockoon issue 992, Prism issue 2797, Prism issue 2726

Download counts give only a rough sense of use, and automated builds inflate them. In the 30 days to October 18, 2026, npm recorded about 938,000 downloads of Prism’s CLI and 233,000 of Mockoon’s. Microcks is mainly distributed as a container image and reports its own figure, more than 2.5 million downloads in 2025. These numbers are not comparable market shares. CNCF announcement

How we researched

This is public-source research. For this review we did not install, run or test any of these tools, create accounts or contact the projects. Our sources were each project’s documentation, changelogs and release records, security advisories (GitHub and OSV), issue trackers, package metadata from npm and Maven Central, the Cloud Native Computing Foundation’s announcement, and user discussions, all read on October 19, 2026. No project supplied access or payment, and our links carry no affiliate tracking.

This article first appeared on October 1, 2026, and then rested mainly on a small hands-on check run that day, before we adopted our research-only method on October 3. We keep that check as a dated observation. It sent the same four requests to Prism CLI 5.16.0 and Mockoon CLI 9.9.0, using one fictional OpenAPI 3.0.3 contract. It shows what those versions did with that file once, not how they behave on large contracts, in continuous integration or under attack, and it did not decide any recommendation here: the behaviour it showed is documented by Prism and described by Mockoon’s maintainer. Earlier check record, October 1, 2026

We wrote this for a small frontend team that has an OpenAPI contract and needs repeatable local responses, including error states, before the backend exists. Before scoring, we fixed five criteria and their weights: how faithfully the tool turns the contract into responses (30%); maintenance, security and continuity (30%); local setup and safe defaults (20%); flexibility beyond static examples (10%); and what you keep and maintain if you leave (10%). The local editions are free, so cost carried no weight. Prism scored 3.80, Microcks 3.60, Counterfact 3.30 and Mockoon 3.05 on our five-point scale. Prism’s lead over Microcks is less than half a scoring step and depends on a judgement about Prism’s maintenance in which we have only medium confidence. Microcks came first when maintenance carried about 40% of the weight, and drew level when we scored setup for a team that already runs containers, which is why we name it as the alternative. Mockoon did not come first under any of the weightings we examined.

On November 6, 2026 we examined GitHub’s mock-server directory, the OpenAPI tools directory and launch-community records for relevant alternatives and newcomers. Counterfact joins the comparison because its generated routes serve the same frontend job. Among other options with enough documentation to score, Swagger Inflector scored 2.90, Imposter 2.85 and muonsoft’s openapi-mock 2.55. Inflector needs a Java application scaffold; Imposter needs extra configuration or scripts for custom behaviour; openapi-mock has unresolved user requests about choosing examples and error codes. Imposter’s recent repository changes mean its old release date alone is no reason to call it abandoned. GitHub directory, OpenAPI mocking directory, Swagger Inflector, Imposter, openapi-mock issues, checked November 6, 2026.

WireMock’s own comparison still describes OpenAPI import in its open-source edition as manual stub authoring; Postman’s documented mock deployment is cloud-hosted. MSW generates handlers for interception inside an app or tests rather than a standalone HTTP server. Insomnia’s documentation explicitly requires an account for mocks, including its self-hosted offering. Bruno’s free mock entitlement and Apidog’s account-free local access could not be confirmed. WireMock, Postman, MSW Source, Insomnia mocks, checked November 6, 2026.

Specmatic Core offers free stateless OpenAPI mocking and fault simulation; its paid stateful features are not needed for the basic job here. Mokapi also serves local contract mocks with scriptable responses. We could not establish enough startup and control-interface detail to give either a complete score. MockServer’s GraalJS advisory concerns an optional engine and access to its management API; it does not establish that every current installation is vulnerable. Other advisory applicability details remain unclear. Crudio and apisprout also fit the contract-server job, but we lack enough evidence about Crudio’s local confinement and apisprout’s current security and maintenance to give them complete scores. They are not assigned lower totals. Specmatic licence comparison, Mokapi, MockServer advisory, Crudio, apisprout, checked November 6, 2026.

No Rising Star selected. The November 6 search found no newer tool with confirmed first-release, Windows and macOS availability, contract-server functionality and safe local-use evidence together. An unknown first-release date prevents a newcomer award, while the tool remains part of our research. GitHub directory, OpenAPI mocking directory. We give no points for popularity or for being new.

ToolPublic sourcesWhat remains uncertain
Prism CLIREADME, CLI, mocking and installation guides, changelog to 5.16.0, analytics pull request, npm package metadata, release assets, GitHub and OSV advisory records, issues 2723, 2726 and 2797, SmartBear acquisition announcement.SmartBear’s plans for Prism, whether open 3.1 and example reports will be fixed, whether binaries will return for 5.16.0, whether CVE-2025-1302 was reachable through Prism.
MicrocksREADME, getting started, first REST mock, OpenAPI conventions, dispatching and stateful-mock guides, releases to 1.15.0, CNCF announcement and project page, GitHub advisory, Docker port-publishing guide.Explicit OpenAPI 3.1 support, behaviour for operations without examples, resource use of the container on a developer laptop.
CounterfactMIT repository, quick start, releases to 3.2.2, issue list and advisory list, checked November 6, 2026.Native listening address, module-loader report applicability and large-contract behaviour. Current docs confirm code-based customization; named-example details retain their October 19 date.
Other local alternativesNovember 6, 2026 documentation, pricing, release and advisory pages; October 19 research for earlier capabilities.Specmatic and Mokapi startup/control-interface details; MockServer advisory applicability; Crudio confinement; apisprout current maintenance/security; newcomer release and platform evidence.
Mockoon CLICLI guide, OpenAPI compatibility, rules, multiple-response, templating, CRUD and admin API documentation, issues 962 and 992, large-import discussion, five security advisories, npm package metadata, release 9.9.0.OpenAPI 3.1 handling, behaviour on large contracts after the December 2025 fixes, whether further security reports follow the 2026 cluster.

None of these sources measures speed, failure rates or behaviour on large contracts. Next substantive review is due December 18, 2026, or sooner if a security advisory, a new Prism release or a change in its stewardship affects this job. Found a change? Contact the editors.

Sources and evidence

Checked October 19, 2026: Prism repository and licence, README, CLI guide, mocking guide, installation, changelog, 5.16.0 release, 5.15.11 release with binaries, analytics change, CLI package README, issues 2723, 2726 and 2797, SmartBear’s Stoplight announcement and SmartBear open source; Microcks repository and licence, getting started, first REST mock, OpenAPI conventions, dispatching, stateful mocks, 1.15.0 release, CNCF announcement, CNCF project page and advisory GHSA-r6ph-5fp2-3w2v; Docker port publishing; Mockoon repository, MIT licence, CLI guide, OpenAPI compatibility, response rules, multiple responses, templating, CRUD routes, admin API, 9.9.0 release, issues 962 and 992, large-import discussion, and advisories GHSA-w7f9-wqc4-3wxr, GHSA-rqx4-3f6q-3x2v, GHSA-8wqc-v2q8-vff2, GHSA-845j-g722-g66h and GHSA-cmwm-hp2w-h3cx; alternatives set aside: WireMock open source and Cloud, Postman mock servers, MSW Source and its OpenAPI function, MockServer and OpenAPI, Specmatic, Counterfact, Mokapi, Imposter and openapi-mock; and the earlier check record, October 1, 2026 with its fictional contract. No project supplied access or influenced the conclusion. No affiliate links were used. Recheck versions, advisories and Prism’s maintenance before any public release.

Additional sources checked November 6, 2026: Counterfact repository, releases, issues and advisories; local pricing and licence evidence for Prism, Microcks, Mockoon, Specmatic, Mokapi, Imposter, openapi-mock and Swagger Inflector. Other incumbent capability and security findings retain their October 19, 2026 evidence date.

No screenshots are shown: these are command-line and container tools, and this review is based on public sources. The earlier check record, October 1, 2026 and its fictional contract describe a small check run before our research-only method.