Postman started as a Chrome extension.
One developer, scratching his own itch. No accounts. No pricing tiers. No "upgrade to unlock collections." Just a clean tool that let you hit endpoints and see what came back.
That was 2012.
Fast forward to now — you open Postman and the first thing it asks for is an account. Then it wants you to sync to the cloud. Then it nudges you toward a team plan. The tool that used to just work now needs to know who you are before it lets you do anything.
I get it. Companies need to make money. But somewhere between the Chrome extension and the enterprise sales deck, Postman stopped being for developers and started being for procurement teams.
So I built Reqit.
What Reqit is:
A desktop API client. Local-first. Offline-first. No account required. Zero telemetry. Your collections are plain JSON files sitting on your machine — you can read them, version them, move them, delete them. No vendor lock-in.
Built with Go, Wails v2, React, and TypeScript. Works on Windows, macOS, and Linux.
Why open source?
Because that's the only way to actually prove the promise.
"We don't collect your data" means nothing coming from a closed binary. With open source, you can read the code. You can verify that there's no phone-home logic, no hidden analytics, no silent cloud sync. The code is the contract.
Also honestly because Postman itself started as an open project. The irony of building a closed replacement for it wasn't lost on me.
Who it's for:
Developers who want a tool that respects their workflow. If you're working offline, behind a VPN, on a local environment, or just tired of logging into your API client — Reqit is for you.
I'm Kamsy, aka halxdocs. I build developer tooling in Go and TypeScript.
Reqit is free, open source, and available now. Drop a star if it's useful — and if you have feedback, open an issue. That's the point.
→ github.com/halxdocs/reqit
reqit.vercel.app
Top comments (0)