Welcome to join us here : https://discord.com/invite/XSYCf7JF4F
dhruv3006
joined 4 weeks ago
Everyone seems to hate this template.
Voiden's core request model is based on composable blocks (for elements like headers and auth) that are reusable across requests for a DRY (Don't Repeat Yourself) approach, unlike Bruno which treats the request as a single, monolithic object that leads to copy-pasting and maintenance burden.
For documentation, Voiden provides living documentation by integrating runnable requests and human explanations side-by-side in the same Markdown file, ensuring it stays in sync with the API, while other tools' documentation is often separate.
From the monetisation side Voiden: Is an open-source community infrastructure project backed by a different main business, reducing the pressure to monetize aggressively. Bruno is as an open-source project that is under pressure to find a viable monetization strategy, which can lead to license shifts or paywalls.
You can read about the comparison here : https://voiden.md/comparison
Its an alternative to Monolithic Requests - Voiden has composable blocks which are an alternative to copy pasting entire request objects. We do not lock in collections in cloud like other api clients like postman and have a file centric and git native approach. Also we offer a unified toolchain - for design, testing, and documentation as an alternative to juggling multiple disconnected apps.
That's a pretty good comparison.
The core idea of executable documentation next to your code is exactly what we were aiming for.
The difference is that Voiden is a dedicated, cross-platform app for the modern ecosystem, bringing the power of that file-centric workflow to everyone. We specifically go further by offering resuable composable blocks for requests (closer to functions than monolithic objects), a unified toolchain for design, testing, and documentation, and a clean, Git-native experience for all developers.
Well having decent documentation is kind of rare.
Thanks for this.
Hey, that’s a fair comparison. .http files are actually one of the closest things conceptually.
The difference is mostly in how far the idea is pushed.
.http files are basically request definitions written in HTTP syntax. They are great for sending requests and keeping them next to your code.
Voiden treats the Markdown file more like an executable API workspace. Requests are composed from reusable blocks (endpoints, auth, headers, params, bodies, etc.), so instead of copying similar requests around you can structure them like small building blocks and reuse them across the file. That becomes useful once an API grows and you start repeating the same pieces everywhere.
Another difference is that the file can mix documentation, explanation, requests, tests, and scripts in the same place and actually run them. The goal is that the file itself becomes the living artifact of the API workflow rather than just a request list. And since everything is still plain text and Git-friendly, you can keep it alongside the codebase the same way you would with .http.
If someone is happy with .http files they probably don’t need Voiden. The idea is more for teams that want the requests, tests, and docs to live together in one executable spec rather than spread across tools.
Do you use .http mostly for quick testing, or do you keep full API workflows in them?
This is actually a great comparison ! Thanks for these words !
Postman teams plan no longer free.
view more: next ›
yep i got one as well.