Voiden is an offline-first, git-native API tool built on Markdown - and it very intentionally didn’t start as “let’s build a better Postman”.

Over time, API tooling became heavyweight: cloud dependencies for local work, forced accounts, proprietary formats, and workflows that break the moment you’re offline. Testing a localhost API shouldn’t need an internet connection.

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

  • Specs, tests, and docs living together in Markdown

We opensourced Voiden because extensibility without openness just shifts the bottleneck.

If workflows should be transparent, the tool should be too.

Github : https://github.com/VoidenHQ/voiden

Download here : https://voiden.md/download

    • dafalcon@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      18 hours ago

      quite cool - i think voiden is similar in premise to verb - but it is more easier to manage for non emacs folks. But i’ll check it out - emcas will bring back the ptsd from my phd days of writing my thesis on it :D

      • banshee@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        I really think tools like voiden, hurl, and verb make sense. They make it easier to troubleshoot a system later or to share requests with other developers without leaving the repo. The only real challenge becomes handling authentication scenarios without putting secrets in plain text.

        Speaking of writing a thesis, I imagine that leaves plenty of room for PTSD! I personally like the direnv support for emacs much more than other environments, and I’ve become a big fan of ripgrep and fuzzy finding.