Mockzilla
mockzilla.org
- Free plan
- Open source
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Mockzilla is
Mockzilla creates mock APIs from OpenAPI specifications or plain JSON files for frontend development, integration tests, and demos. OpenAPI schemas can generate realistic responses, and requests can be checked against the specification. Developers can add latency or errors at the service or endpoint level to exercise retry and fallback behavior. A proxy can pass requests to a real backend while serving mocks for routes it does not handle. Its GitHub Action provides a mock URL for each pull request, updates it on pushes, and removes it when the branch is gone. Request records include status and timing, with options to replay a request or a set. The MIT-licensed CLI runs offline on a laptop or in CI; hosted cloud features are optional. Mockzilla also lists an MCP server and payment-provider simulations. The Free plan is free, with no API access and two-hour request-history retention. Hobby is $10 a month. Uploaded content must not include sensitive data such as credentials, health records, or real financial data.
Who it suits
It suits developers who need API mocks for frontend work, testing, demos, or pull-request environments. The plan descriptions also identify solo developers, small teams, side projects, and teams with CI pipelines as audiences for paid tiers.
Good to know, and what to watch
- Generates responses from OpenAPI schemas.
- Can validate requests against an API specification.
- Simulates latency and errors by service or endpoint.
- GitHub Action creates and updates pull-request mock URLs.
- Offline-capable, MIT-licensed CLI runs on laptops or in CI.
- Free plan has no API access.
- Free plan retains request history for only 2 hours.
- Uploaded content must not contain sensitive data.
Plans
Every plan and priceEnterprise
Free
Hobby
Starter
Free plan
Getting started
- Open the Mockzilla website
- Choose the Free, Hobby, Starter, or Pro plan
- Import an OpenAPI specification or plain JSON file
- Configure responses, latency, or endpoint errors
- Connect the GitHub Action, MCP server, or CLI workflow
Limits to check
The Free plan costs nothing and includes 1K requests per month, 5 requests per second, one simulation, and 10 MB of data transfer. API access is unavailable and request history is retained for 2 hours.
The Club's review
Mockzilla creates hosted mock APIs from OpenAPI specifications or plain JSON for frontend development, integration tests and demonstrations. It is aimed at developers and teams that need controllable behavior both locally and in CI. The combination of contract-aware responses, deliberate failures and pull-request environments is compelling, but Free is constrained by disabled API access, a short history window and strict data restrictions.
Overview
OpenAPI imports produce realistic schema-based responses and validate requests against the specification, helping frontend work stay aligned with an API contract. Plain JSON provides a simpler starting point when no formal schema exists. Dynamic responses and generated mock data make the service more useful than a collection of fixed fixtures.
Mockzilla can run offline through its MIT-licensed CLI, on a laptop or in CI, while hosted cloud features remain optional. HTTP is the supported protocol. TLS protects data in transit, encryption protects it at rest, and simulations run in isolated environments with scoped access. Those safeguards do not change the terms requirement: uploaded content must exclude personally identifiable information, real financial data, health records, credentials and other sensitive data.
Key features
Latency and error injection can be configured per service or endpoint, allowing teams to exercise retry and fallback behavior deliberately. The proxy forwards routes to a real backend and supplies mocks for routes that backend does not serve, making it practical while an API is only partly implemented.
The GitHub Action creates a mock URL for each pull request, refreshes it on pushes and removes it when the branch disappears. That is a useful fit for isolated review and CI environments. Request history records status and timing, and users can replay one request or a set of requests. Free-plan history lasts only two hours, which limits its value for longer investigations.
Integrations include the GitHub Action and an MCP server for coding agents; the CLI documentation includes setup for Claude and Gemini. Payment simulations cover decline cases, 3D Secure flows, lifecycle operations and idempotency behavior, relevant to teams testing checkout logic rather than merely displaying sample data.
Pricing
Mockzilla uses a freemium model. Free costs nothing and includes 1K requests per month, 5 requests per second, one simulation and 10 MB of data transfer. API access is unavailable and request history is retained for only two hours, so this tier suits evaluation and very small experiments rather than a shared service.
Hobby costs $10 a month, with 100K requests per month, 10 requests per second, two simulations and 1 GB of transfer. It fits side projects that need hosted API access without substantial volume. Starter is $20 a month for 200K requests, 20 requests per second, five simulations and 4 GB of transfer; it is the more sensible baseline for a solo developer or small team.
Pro costs $50 a month and raises capacity to 400K requests, 40 requests per second, 10 simulations and 16 GB of transfer, matching teams with CI pipelines. Enterprise has custom pricing, dedicated infrastructure, an own domain and traffic-sized capacity. Verified students can apply for a free tier without a card; manual review usually takes one to two business days.
Platforms
Mockzilla supports API, Linux, macOS, self-hosted, web and Windows workflows. The offline CLI and local deployment serve teams that want control over execution, while hosted environments support browser-based and CI use.
Who it's for
Choose Mockzilla for frontend teams working from OpenAPI contracts, integration testers who need repeatable failures, and GitHub-based teams that want temporary environments per pull request. Payment teams also get targeted lifecycle and decline simulations. It is a weaker fit for workloads requiring sensitive production-like uploads or for users who need only a few static fixtures with no proxy, history or fault testing.
Pros and cons
Pros
- Contract-aware mocks: OpenAPI response generation and request validation help expose mismatches before a backend is complete.
- Useful failure control: Per-endpoint latency and error injection makes retry and fallback testing repeatable.
- Hybrid routing: Proxy fallback combines a real backend with mocks for missing routes.
- Pull-request environments: The GitHub Action creates, updates and removes isolated mock URLs automatically.
- Local option: The MIT-licensed CLI runs offline and in CI.
Cons
- Restrictive Free tier: No API access and only two hours of history make it unsuitable for ongoing shared use.
- Usage ceilings: Paid tiers impose monthly request, rate, simulation and transfer limits that teams must size carefully.
- Data prohibition: Sensitive personal, financial, health and credential data cannot be uploaded.
Alternatives
For a broad comparison, see API Mocking Tools. Pick Beeceptor instead if its Individual plan’s 15,000 requests per endpoint, private endpoints and CRUD objects better match a smaller endpoint-focused setup. WireMock suits users wanting a free tier with 1,000 calls per month, three mock APIs and a 10-request-per-second limit. Choose WireMock for its self-hosted and web-oriented free offering. Microcks is the choice for a 100% open-source, CNCF Incubating distribution. Mockttp fits traffic viewing, rewriting and manual breakpoints. Parasoft SOAtest is a paid, quote-based option with a free trial. Knockout API is worth considering for image-oriented free and metered plans. Mockfly offers a free starter allowance of 500 requests per day across one project.
Verdict
Mockzilla is a strong choice for developers and CI-driven teams that need schema-valid mocks, controlled faults, hybrid backend proxying and disposable pull-request environments. Its local CLI and focused payment simulations broaden the use cases. Look elsewhere if the Free tier must provide API access, if request history must persist beyond two hours, or if your test data includes information the terms prohibit uploading.
The verdict
Mockzilla combines schema-based API mocks with fault simulation, proxy fallback, and pull-request environments. Check the Free plan's API and history limits, and keep sensitive data out of uploads.
Questions people ask
Is there a free plan?
Yes. The Free plan is free. Paid plans start with Hobby at $10 a month.
Which platforms does Mockzilla support?
It lists API, Linux, macOS, self-hosted, web, and Windows platforms, with HTTP support.
Can Mockzilla run locally?
Yes. The MIT-licensed CLI runs offline on a laptop or in CI, and hosted cloud features are optional.
Does it integrate with developer workflows?
The site lists a GitHub Action and an MCP server. CLI setup instructions are provided for Claude and Gemini.
What does the Free plan include?
It includes 1K requests per month, 5 requests per second, one simulation, and 10 MB of data transfer, but no API access.
What the maker publishes
- Access controls
- Simulations support API-key protection, explorer credentials and IP allowlists. source
- API key roles
- API keys have administrator or editor roles and are managed by organization owners and administrators. source
- Audit logging
- The settings area includes an audit log showing organizational changes and their actors. source
- CLI installation
- The CLI is distributed through Homebrew and prebuilt binaries for macOS, Linux and Windows, and runs without an account. source
- Codegen
- Codegen mode produces typed Go handlers from an OpenAPI specification while keeping the specification in the repository. source
- Company identity
- GitHub marks the Mockzilla organization as domain-verified for mockzilla.org and lists [email protected] as its contact email. source
- Documentation depth
- The documentation is organized into getting started, simulations, resilient backends, developer tools, settings, billing and help sections. source
- Error simulation
- Users can set service-wide or endpoint-specific error rates to exercise failure handling. source
- External platform coverage
- The GitHub organization README lists 24 AWS regions with latency-based routing for hosted simulations. source
- External praise: Go implementation
- A Reddit commenter specifically recommended mockzilla.org for running multiple specifications on one port and identified it as Go-based. source
- External praise: multi-service use
- A Reddit commenter said Mockzilla can run multiple API specifications on one port with URL prefixes and CI support without extra setup. source
- External repository size
- The public GitHub repository showed 110 stars and 6 forks when opened. source
- External validation claim
- The GitHub README reports validation against more than 2,200 OpenAPI specifications and 98,000 endpoints. source
- Fault simulation
- Users can inject latency and errors per service or endpoint to test retry and fallback behavior. source
- History and replay
- Mockzilla records requests with status and timing and allows users to replay individual requests or sets of requests. source
- Hosted retention limit
- Request history is a rolling debugging window whose default retention is one hour, with plan-specific retention limits. source
- Integrations
- The site lists a GitHub Action and an MCP server for coding agents; its CLI page gives setup instructions for Claude and Gemini. source
- Latency simulation
- Latency can be configured for an entire service or individual endpoint. source
- License
- The Mockzilla engine is released under the MIT license. source
- Local execution
- Simulations can run locally with the CLI, Docker or Docker Compose. source
- MCP integration
- Mockzilla provides an MCP server that lets Claude Code, Cursor and Gemini CLI launch mock APIs from OpenAPI definitions. source
- Notable news: payment coverage
- A LinkedIn post dated about four weeks before the research date said payment simulations covered 12 providers, including Stripe, PayPal, Adyen and Klarna. source
- Open source and local use
- The CLI is MIT-licensed, runs offline, and the site says it can run on a laptop or in CI; hosted cloud features are opt-in. source
- Payment backends
- Mockzilla describes payment-provider simulations with decline cases, 3D Secure flows, payment lifecycle operations, and idempotency behavior. source
Checked against the maker's pages on 15 Oct 2026.