On the one side you have legacy tools: API tools like Postman, Insomnia etc that are built as platforms first: Accounts, workspaces, cloud sync, dashboards, paywalls. Actual API work often comes second.
On the other side, we now have a bunch of API tools that are vibe coded. Built, shipped and posted on Twitter the same day. Yes, they look sharp, but under the surface they are often thin abstractions over fetch calls. With no clear model or long-term thinking about workflows, versioning, or how teams evolve their API usage over time.
Somewhere in between, there is Voiden. Voiden is a result of years of synthesizing thoughts and feedback from real developers : backend engineers, platform teams, API designers. We watched how they actually work. Where workflows break. Where collections rot and collaboration becomes painful.
So we designed it, we showed it, we improved it and then improved it a bit more. And now we open sourced it.
Voiden is an offline-first, Git-native API tool where requests, specs, tests, and docs live together as executable Markdown inside your repository.
Voiden introduces a live Markdown + API runner workflow. API requests, reusable blocks, and human explanations live in the same Markdown file - and can be executed in place. No request builder UI. No context switching.
The best thing is, while other tools treat a request as a single opaque object, Voiden does something completely different (and unique) - no other API client does this.
Voiden breaks a request into composable blocks: endpoint, headers, query, JSON, auth etc.In most tools, headers and auth live inside individual requests, so if you need them elsewhere, you duplicate them. When something changes, you update every copy manually.
In Voiden, blocks behave like functions: define them once, reference them across requests, and when the block changes, every request using it stays in sync.
Voiden is intentionally lightweight and extensible. We wanted the core to stay lean, and everything else to live in a plugin system: gRPC, GraphQL, WebSockets (WSS), assertion blocks, etc and more coming.
That means the tool can grow in capability without growing in bloat. Everyone can select which plugins to have and the community can extend it just as easily as we can.
Voiden works around your workflow, your way, rather than make you adapt your processes around the tool.
If you don't want to deal with bloated API tooling and saas looking clients, Voiden is the tool you want to try.
Github : https://github.com/VoidenHQ/voiden
How to switch from Postman to Voiden : https://voiden.md/blog/migrate-postman-collections-to-voiden
Top comments (0)