from dhruv3006@lemmy.world to programming@programming.dev on 13 Mar 07:11
https://lemmy.world/post/44194196
Voiden is an offline-first, git-native API tool built on Markdown Voiden is an API client we have been building that takes a different approach from most existing tools.
It didn’t start with the idea of “building a better Postman”.
A bit of background. Over time, API tooling has become heavyweight: cloud dependencies for local work, forced accounts, proprietary formats, and workflows that break the moment you are offline. On top of that, time wasted on fixing API specs that don’t match the code, docs in separate random tools, tests also separate and an overall governance mess. Not to mention collaboration.
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.
- Plain text files: specs, tests, and documentation live together in Markdown
- A programmable interface instead of static forms: requests are composed from reusable blocks (endpoints, headers, auth, params, bodies, etc.) that you can structure the way you want
- Plugin system for extending functionality rather than bloating the core with new features Some of our core plugins include gRPC,GraphQL,WebSockets,etc…
We have just also updated our docs to welcome community plugins, so teams can extend the tool for their own workflows or integrations. docs.voiden.md/docs/plugins/build-a-plugin
We opensourced Voiden because extensibility without openness just shifts the bottleneck. If (API) workflows should be transparent, the tools should be too.
Welcome to try out and share feedback- happy to chat with everyone.
Strong opinions are encouraged. :)
Github : github.com/VoidenHQ/voiden
Download here : voiden.md/download
#programming
threaded - newest
So you basically made org-mode + restclient for people who don’t use Emacs?
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.
Thanks for sharing, I’ll give it a try
Would love some feedback here: github.com/VoidenHQ/voiden
How does this compare to Bruno?
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 : voiden.md/comparison
Interesting.
Bruno also has inheritance for things like auth, which kinda solves the same problem as composable blocks. So it’s not like you have to copy it everywhere
yes in Voiden everything is a block though.
voiden.md/comparison
depends on what you want to focus on - for example I like the reusable blocks and the programmable interface + the idea of community plugins that extend the tool!
Just as I was getting fed up with Postman. I’ll be looking into this.
You are welcome ! Join us here : discord.com/invite/XSYCf7JF4F
Just use
curl.justuse.org/curl/
Ok? Guess i’m too out of the loop. But thanks regardless.
Edit: mixed the explicit “proprietary” from the german Wikipedia in the quote.