Mockoon vs MockServer

Mockoon is a free, open-source tool for designing and running mock APIs locally. It supports OpenAPI and can fit into existing applications and API design workflows. Mock behavior can use dynamic templating, rule matching, JSON databases, proxy mode, webhooks, and TLS. The tool can record requests and responses from a real API to create mocks, and it supports proxying and integration testing. The open-source version permits unlimited mock APIs and routes, including parallel runs. Its CLI can run mocks in headless automated environments such as CI, GitHub Actions, and Docker; mocks can also run in serverless environments including AWS Lambda and GCP/Firebase Functions. The desktop app stores mocks locally, works offline without an account, and reports that mock content and request data are not sent to Mockoon. Pro adds real-time team collaboration, synchronized mocks, and deployment management on private infrastructure; it can be self-hosted on-premises, in a private cloud, or on isolated or air-gapped networks. Team is listed at €10 a month, billed annually at €120/license/year, tax excluded. Eligible companies can request one 14-day self-hosted Pro trial with five license slots using a verified work email, without a payment method.

MockServer is a free, self-hosted tool for mocking and proxying HTTP, HTTPS, and gRPC services during isolated testing. It can verify requests as well as stand in for services. Teams can generate mocks and validate traffic against OpenAPI or Swagger contracts, or import recorded sessions from browser HAR files and Postman collections. Beyond HTTP services, it can mock gRPC, AsyncAPI brokers such as Kafka, MQTT, and AMQP, and OAuth2/OIDC providers. Its protocol coverage includes HTTP/1.1, HTTP/2, HTTPS, SOCKS, and experimental HTTP/3, which uses a separate UDP port. For fault-oriented testing, it can add latency, errors, dropped connections, and malformed responses to mocked or proxied traffic. Deployment options include Docker, an executable JAR, Helm/Kubernetes, Testcontainers, Homebrew, and a JVM-less bundle. A web dashboard displays logs, expectations, and recorded traffic; Prometheus metrics and OpenTelemetry tracing are available for shared environments. Each instance includes an MCP server at /mockserver/mcp. The /mockserver/status and /mockserver/ready probes remain reachable without authentication or authorization.