Keep your collections. Drop the account.
Import collections, environments and globals, and run mocks and tests on your own machine. Nothing goes to a cloud.
Be aware: No team workspaces: Git is how you share.
Zyvra as a Postman alternativeMock the APIs you do not have, test the ones you do. One small program on your machine, with no account and no cloud.
curl -fsSL https://www.zyvra.dev/install.sh | sh irm https://www.zyvra.dev/install.ps1 | iex Installs for your user only, no sudo. How the download is verified
- method: GET
path: /products/{id}
rules:
- name: unknown product
when:
- { source: path, name: id, op: equals, value: "999" }
respond: missing
scenarios:
found: { status: 200, body: { name: Keyboard, price: 49 } }
missing: { status: 404, body: { error: product not found } } $ curl -i localhost:18081/products/999
HTTP/1.1 404 Not Found
X-Zyvra-Rule: unknown product
X-Zyvra-Scenario: missing
{"error": "product not found"} A mock shop API, the API client, the Console, Traffic and a collection run.
Use the mock side, the client side, or both in one project.
Stand in for a service that is not ready, is slow, or that you would rather not call. Rules, scenarios and state decide the answer from the request itself.
Find out what your client does when the other side is slow, down, rate limited or wrong, without waiting for it to happen.
A full API client that knows your mocks: every response says which service, rule and scenario produced it, and whether it matches your spec.
The Console logs every request the dashboard sends, from the API Client, the Test Runner and workflows alike, with real values in place of your {{variables}}.
Add checks to a request, then run the whole collection here, or in CI with one command and a JUnit report.
Every request a mock receives is recorded with the rule and scenario that handled it, so a surprising answer is easy to explain.
Every tool here is good at something. These are the honest trade-offs.
Import collections, environments and globals, and run mocks and tests on your own machine. Nothing goes to a cloud.
Be aware: No team workspaces: Git is how you share.
Zyvra as a Postman alternativeRules, scenarios and failures from a UI or plain YAML, plus an API client and a test runner in the same program.
Be aware: Younger, and not a JVM library.
Mock API tools comparedStored state, webhooks, failure modes and tests in CI, when a fixed response is no longer enough.
Be aware: More to learn than a one-file fake.
When each tool fitsYour mocks and your data stay on your computer, work offline and cost nothing.
Be aware: No public URL to hand to outsiders.
How Zyvra mocks an APILatest release: v0.8.0, November 18, 2026. 24 releases so far, each one signed.
Most of this can be checked.
Everything listens on 127.0.0.1. Nothing is reachable from other computers, and there is no cloud service behind it.
YAML in your own folder. Read them, review them, keep them in Git. Nothing is locked in a database you cannot open.
Mark a variable secret and its value is stored encrypted outside the project, then masked in responses, history and traffic.
JavaScript is code, so it stays off until you trust the project. It runs in a sandbox with no file, network or process access.
Every release is signed with Zyvra's own key. Zyvra refuses an update the key did not sign, and never installs one without asking.
Zyvra reports nothing about you or your projects. The optional daily update check sends only a version, a system and an architecture, which this website only counts: no address, no identifier.
Short guides on mocking an API, testing failures, running API tests in CI and more.
Install it, create a project, and send your first request to a mock. There is nothing to sign up for.