yep i got one as well.

Welcome to join us here : https://discord.com/invite/XSYCf7JF4F

Everyone seems to hate this template.

You are welcome ! Join us here : https://discord.com/invite/XSYCf7JF4F

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.

They do !

Here’s how to get started : https://docs.voiden.md/docs/getting-started-section/getting-started/openapi-imports

Unfortunately I agree but there are a few that are different, for example have you tried Voiden ( https://voiden.md/) maybe? We opensourced a few weeks back.

Postman was great when it made APIs simple, but over time all the accounts, cloud sync, and extra features kind of slowed down the core workflow. And then a lot of clients just ended up copying that model instead of rethinking it.

On the optimistic side we are seeing some stuff that want to rethink this: tools like Voiden and Yaak with a few new approaches like  Git-native workflows, reusable request pieces, more composable setups basically making API work feel more like actual dev work again.