YES

Replaceable in one session with an AI coding agent.

An API client and workspace: send requests, save them into collections, script tests against the responses, and share the lot with a team.

Promptfree, for everyone, and the only version there is
Keep requests in the repository instead of in a workspace.

STACK
- .http files and the REST Client extension, or Hurl for the command line
- No service at all

REQUESTS AS FILES
- One file per resource, checked in beside the code it calls
- Variables per environment in a .env-style file that is git-ignored
- A request diff now shows up in code review, which a hosted workspace never does

TESTS
- Hurl asserts on status, headers and JSON paths in the same file as the request
- Run the whole directory in CI; a broken contract fails the build

SECRETS
- Never in the request file. Read from the environment, and keep an example file with the names and no values

WHAT YOU GIVE UP
- The shared workspace. Replace it with the repository, which is where the rest of your contracts already live

Include the file layout, one example with assertions and the CI step.

What you lose

  • Shared workspaces where a collection is the team's living documentation of an API
  • Mock servers, monitors and generated documentation from the same collection
  • A desktop app that handles cookies, proxies and certificates without configuration

If you would rather not build

  • Hurl or curl, for the command line

The escape hatch

open source · no votes, no paid placement

Bruno

$0

An API client whose collections are plain files you commit.

usebruno/brunofree · open source

Hoppscotch

$0

A browser-based API client, self-hostable.

hoppscotch/hoppscotchfree · open source

Why this verdict

our own opinion · changed only by a person

72/100

Verdict yes at 72. Moving requests into the repository is usually an improvement rather than a compromise: they get reviewed, versioned and run in CI.

History

tracked since 10 Aug 2026 · nothing is ever overwritten

Interest · last 30 days

Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.

Questions about Postman

answered from the record above

Is Postman free?

No — the plan we track is $14 a month. Basic at $14 per user per month billed monthly, $12 annually; a free tier covers individuals.

Can you replace Postman by building your own?

YES. Replaceable in one session with an AI coding agent. Replacement score 72 out of 100, build time one session. Read what you lose before you decide.

How much does Postman cost?

$14 a month on Basic — $168 a year. Recorded 10 Aug 2026.

What do you lose by replacing Postman?

Shared workspaces where a collection is the team's living documentation of an API; Mock servers, monitors and generated documentation from the same collection; A desktop app that handles cookies, proxies and certificates without configuration. If any of those carry weight for you, keep paying.

Is there an open-source alternative to Postman?

Yes: Bruno, Hoppscotch. The prompt on this page is for when you want it your way instead.

Related entries

same category first, most replaced first

All 36 in Dev tools

Coming soon

Every week, something stops being worth paying for.

New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click.

free forever · no tracking pixel · every prompt stays free on the site

Esc