WireMock OSS runs simple mocks in your tests or on standalone servers you host.
WireMock Cloud is enterprise-grade environment simulation infrastructure: high-fidelity, shared simulations that every team and AI agent in your organization can rely on.
Compare OSS to Cloud
Both editions run the same WireMock engine, so there’s nothing to prove on OSS first. WireMock Cloud offers more capabilities (such as stateful mocking and contract validation), cloud-based collaboration, and enterprise-readiness.
| WireMock OSSBest for a developer or team running its own mocks, in tests or on a standalone server. | WireMock CloudBest for organizations where many teams depend on the same systems. | |
|---|---|---|
| The engine | Request matching, response templating, faults, basic recording | Open source core + state management, chaos testing, contract validation, security, cloud UI, and much more |
| Who builds simulations | Developers | Platform teams, developers, QA, and AI agents (via MCP) |
| How they build them | Code | UI, CLI or AI |
| Where simulations are managed | In each repo that needs them | One shared catalog, with version history |
| Staying true to the real environment | Edit or re-record by hand; no automated drift alert | Simulations sync with real APIs via automated validation, AI-powered recording, and continuous contract testing |
| Test data and failures | Scenarios, templates and faults, set per stub | Adds CSV/Database data sources, chaos settings across a whole API, and rate limits |
| Protocols | HTTP, including SOAP. gRPC and GraphQL through extensions (requires manual configuration) | REST, SOAP, GraphQL and gRPC, built in |
| Access and audit | Yours to build and maintain | SSO, roles and an audit trail. SOC 2 certified |
| Where it runs | A standalone JAR or Docker process per mock API, which you host, patch and scale | Our cloud, or inside your network with WireMock Runner, where one container serves many mock APIs |
| AI agent integrations | Agents can write stub code, but requires manual tuning to achieve high fidelity simulations | MCP server and Agent Skills built by the WireMock team |
| Ready-made API mocks | Write your own, manually configuring each stub and endpoint | Templates library for third-party APIs such as Stripe, Okta and GitHub, each with a live sandbox |
| Support | Community | Technical support from the team that maintains WireMock |
Why teams switch
As more teams adopt mocking locally, the same dependency gets mocked again and again – creating downstream issues, drift, and inconsistencies.
Every repo that calls an API mocks it again, each copy a little different from the rest.
Hand-written stubs don’t change when the real API does, so tests pass against behavior that no longer exists.
Data-driven simulations, state management, and ongoing validation need to be implemented manually.
Self-hosted mock servers need to be secured, patched and scaled. Using mocks for performance testing is costly and difficult.
Stubs live in JSON files or test code, so only the people who know the format can change one.
A simulation is one versioned service that every team and pipeline calls, so a fix lands everywhere at once.
Start from ready-made templates, record real traffic or generate from OpenAPI, then validate every response against the spec.
State, CSV test data and response templates let a simulation run complete business flows.
Add latency, faults and rate limits, and hammer a simulation in performance tests on infrastructure we scale for you.
Use our cloud, or run simulations inside your network and in CI with WireMock Runner.
Agents build simulations through the MCP server and Agent Skills, and test their code against them before review.
Teams that made the switch
Bilt Rewards, Cuscal, OVO Energy and FreeWill all ran WireMock OSS before they moved to Cloud.
“…we can save a number of developer hours, not having to figure out how to host WireMock, how to protect it, how to define access controls, scale it, maintain it…”
“WireMock Cloud has become the backbone of our daily regression and sanity testing.”
How to get started
Drag the mappings and __files folders from a standalone project into WireMock Cloud’s OSS import. Matchers, templates and responses come across without a rewrite. Stubs built on custom extensions need rework.
Switch your test config to the Cloud URL, or run WireMock Runner next to your tests. Your test code stays the same.
Turn the APIs every team mocks into one shared, versioned simulation, then open it to your pipelines and AI agents.
Book a demo, and we’ll walk through moving the dependencies your teams mock most into WireMock Cloud.