Voiden is an offline-first, git-native API tool built on Markdown - and it very intentionally didn’t start as “let’s build a better Postman”.
Over time, API tooling became heavyweight: cloud dependencies for local work, forced accounts, proprietary formats, and workflows that break the moment you’re offline. Testing a localhost API shouldn’t need an internet connection.
So we asked a simple question: What if an API tool respected how developers already work?
That led to a few core ideas:
-
Offline-first, no accounts, no telemetry
-
Git as the source of truth
-
Specs, tests, and docs living together in Markdown
We opensourced Voiden because extensibility without openness just shifts the bottleneck.
If workflows should be transparent, the tool should be too.
Github : https://github.com/VoidenHQ/voiden
Download here : https://voiden.md/download
Gave it a quick shot right now, and gonna be honest - while the premise seems nice, the sample project is very transparently AI slop generated with a prompt that, I can only assume, included an instruction like “for every sentence that doesn’t include a whimsical quip, I’m gonna kill a kitten”. It is absolutely grating to read. I don’t care if you do that in your marketing copy, but keep that shit out of technical documentation, it’s annoying, it’s distracting, and it’s turning me off the entire project. Like wtf is this:
Why use curl when you can use netcat? I love curl but curl is not postman alternative.
Why use netcat when you can just tap the bits into an ethernet cable with a bench power supply like a telegram operator?
