This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/kiselitza on 2025-05-20 12:31:37+00:00.
Hi folks!
Let me introduce Voiden: https://voiden.md/
A free, offline (self-hosted), git-native API workplace.
Everything is in markdown and sits together: your API definition, its docs, and tests.
I’ve spent years as a dev wrestling with API design, and it’s a pain. I got frustrated a lot, and often.
Pretty sure it sounds familiar.
Not once did I burn hours fixing API specs that didn’t match our code.
Docs were in a random tool, tests were separate, and governance was a mess.
Team API design sucks.
Cloud-sync feels sketchy.
Bloated tools slowing me down on quick tests. Specs and docs in different places break your flow.
And WTH is real-time collaboration? Make a branch.
Well, the team behind Voiden got tired of all this.
It’s not another Postman clone. It’s like code: markdown specs, reusable blocks, Git-versioned, offline.
And yes, it looks different than your usual API tool - on purpose.
Docs tie to your specs with live requests - a single source of truth.
Git tracks changes; branch, diff, review - no login or cloud nonsense.
Here’s a minimalistic GET request in Voiden:
Minimalistic GET request in Voiden
To reproduce this:
- Hit Cmd+N (Mac) or Ctrl+N (Win/Linux) to create a new file.
- Type /endpoint to create a new (GET by default) request block.
- Type or paste the URL you want to trigger a GET request to.
- Hit Cmd+Enter (Mac) or Ctrl+Enter (Win/Linux) to run it.
And now you check the response.
That’s it.
Commit it (yes, the terminal is in the app), run git diff, and your team sees what changed.
No login.
No lock-in.
No telemetry.
No more clones of that same tool we all used, and then moved to the next new kid in the block that looked similar.
So you tell me, what’s your biggest API design pain?
