Postman is a commercial cloud API platform and client for building, testing and documenting APIs; these pages cover replacing it with the offline Bruno client or a self-hosted Hoppscotch instance.
Compares Postman's cloud workspaces with Bruno, the MIT-licensed offline-only client that keeps collections as files in Git: no account or cloud sync, Postman script translation, the bru CLI against Newman, and which Git and import features need a paid Bruno edition.
Compares Postman with a self-hosted Hoppscotch Community Edition, which keeps shared team workspaces but on your own server and PostgreSQL database: web and desktop clients, OAuth sign-in, the alpha CLI, and when the paid Enterprise Edition is needed for SSO and SCIM.
Moving collections from Postman to Bruno: exporting Collection v2.1 JSON or a full data dump, Bruno's importer and script translation, packages that Bruno flags as unsupported, and committing the resulting collection folders to Git.
Moving Postman collections and environments into a self-hosted Hoppscotch instance: the documented Postman importer, the 50 MB self-hosted import limit, setting up team workspaces and OAuth sign-in, and rewriting Postman scripts for Hoppscotch.
Cost by component after Postman's March 2026 plan change made Free single-user: Team seats, the Simple Security add-on for SSO and AI credit overages, against a server and PostgreSQL for Hoppscotch Community Edition or optional Bruno Pro and Ultimate seats, plus support and staff time.
What leaves Postman and how: per-collection JSON exports, environment exports, the account-wide bulk export that only team admins can request, the two-day download window, and the Postman API call limits that apply to scripted exports.
Why Postman does not fit isolated networks, since collections and environments require a signed-in cloud account and the offline Scratch Pad was retired in 2023, and how offline-only Bruno or a self-hosted Hoppscotch instance with local sign-in compare.
Replacing Postman mock servers, which live in Postman's cloud, with mocks you host: WireMock for stubbing HTTP APIs, Microcks for mocks generated from OpenAPI, AsyncAPI or existing Postman collections, and Mockoon for desktop and CI use, plus where each one runs.
For teams that run Postman collections in CI with Newman or the Postman CLI: moving test runs to the Bruno CLI (bru run with JUnit-style reports) or the Hoppscotch CLI (hopp test), what changes in scripts and reporters, and how to keep collections in Git next to the pipeline.
Where API keys and tokens live once Postman is gone: Postman's local and shared vaults against Bruno's secret manager integrations for HashiCorp Vault, AWS, Azure and Google Cloud, Hoppscotch environments on a self-hosted instance, and rules for keeping secrets out of Git.
Since March 2026 the Postman Free plan supports one user and cannot create a team. This page sets out the choice for small teams: pay for Postman Team seats, move to Bruno with collections shared through Git, or run the free Hoppscotch Community Edition for the team.
Postman's EU instance in Frankfurt is sold only to Enterprise customers and lacks some features. This page covers keeping API collections, environments and test data in the EU with Bruno's local files or a Hoppscotch instance in your own EU infrastructure.
Postman puts SAML SSO in a Team add-on and advanced security administration in Enterprise. This page compares Hoppscotch Enterprise Edition, self-hosted with SAML, OIDC, SCIM and audit logs, with Bruno's paid editions, whose license portal covers SAML SSO and SCIM.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.