GitHub - VoidenHQ/voiden: Define, test, and document APIs like a developer, not a SaaS user. No accounts. No lock-in. No telemetry. Just Markdown, Git, hotkeys, and your damn specs.
github.com
Define, test, and document APIs like a developer, not a SaaS user. No accounts. No lock-in. No telemetry. Just Markdown, Git, hotkeys, and your damn specs. - VoidenHQ/voiden

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

    • ReginaPhalange@lemmy.worldEnglish
      51·
      4 hours ago

      Hate this elitist shit. Just for once try to work with other humans on a tech project that requires collaboration.
      Postman strike a balance between technical and user friendly.
      RTFM for curl for everyone is alienating for a a lot of people.

      • dudesss@lemmy.caEnglish
        1·
        4 hours ago

        I’m liking seeing both these opinions side by side. Both sound great.

        Someone wants to spoon feed me curl commands, like thanks :-)

        Someone wants to spoon me a UI which I can’t curl, thanks eh :-)

  • melfie@lemy.lolEnglish
    3·
    7 hours ago

    Postman never appealed me for these exact reasons, and I usually just use curl, but this looks like a great option.

  • chrash0@lemmy.worldEnglish
    12·
    11 hours ago

    i’ve been looking for a silver bullet in this space. hurl[1] seems promising as well. i feel like Bruno has always been jank, and going 1.0 didn’t help. at work i’ve stuck to vibe coding my API test code with a stack of TOML configs, that way i get to reuse/test my client code as well.

    what i want is something version controllable with lightweight dependencies that i can automate easily. i’m afraid that discounts this project. not going to ask my team to download Yet Another Electron API client UI. i’m hesitant to introduce hurl, which can at least be scripted.

    1: https://hurl.dev/

    • nikolasdimi@lemmy.worldEnglish
      2·
      7 hours ago

      hey, nikolas here (part of the team of Voiden)- I am keen to understand more if you dont mind. Which of the preferences you mentioned discounts this project? the version control and lightweight?

      I guess you are you referring to the tool being on Electron (Since the version control is handled through the native git integration)?

      We used electron cause allows to deliver the same experience across Windows, macOS, and Linux, and makes it easier to iterate quickly in these early stages.

      a few points:

      • Some apps do feel heavy because of how they are structured : monolithic cores, always-on cloud layers, or unnecessary background services. Voiden is (intentionally) built with a lightweight core: offline-first, Git-native, and without extra baggage.

      • Voiden uses a plugin architecture. This means that we have a small core and all the extra functionality is optional (users can enable or disable plugins) so the base app stays small while the ecosystem can grow. Community contributions or advanced features don’t inflate the core, they live in plugins that users opt into.

      At the same time, there is no special tie to Electron :) We evaluated other options as well but we felt they didn’t offer the same support for all the features we wanted to deliver.

      But we intentionally designed the plugin SDK to be framework-agnostic, leaving the door open to switch the core to a different framework in the future if it makes sense.The goal is a tool that stays lean, extensible, and adaptable as it evolves.

      apologies for the long answer - hope it makes sense?