HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
VoidenHQ
voiden
TypeScript2025–2026
VoidenHQ / voiden

voiden

Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.

4Distinct people
25Mentions
1Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love how you have used markdown here ! We kind of have used the exact philosophy in https://voiden.md/ - offline-first, file based and support for git. This is exactly the…

dhruv3006 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:16:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month25 dated mentions

Observed mentions: 2025-05-12 10:42:44 UTC to 2026-10-02 12:52:30 UTC.

024682025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 20252025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC110
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC101
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC817
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC303
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC413
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC404
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC101
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC000
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC000
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

8 sources
I agree that AI has dramatically lowered the cost of production and it becomes super easy for small teams to spin up “good enough” systems for API testing, documentation, compliance, or cost monitoring. But where things are still hard is maintaining that tool, security, reliability, UX, integrations, and long-term tool evolution - especially when its not core to their business. Those don’t disappear just because the first version was generated quickly. Operating a tool well over years is still expensive and requires discipline. Again that is not to disagree with your statement, but trying to highlight the difference between building a plane vs operating an airline. there are significant challenges that should not be discounted. But I see the issue around existing tools - why they end up becoming unfriendly to developers or development tea
Read the rest
ms when they all start with great intentions is because their entire business identity is tied to being “the API tool.” Be it postman, insomnia (perplexes me even more why kong has to push it so hard), even bruno to some extent is forced to find a viable monetization strategy. In any case, all this creates strong pressure to monetize aggressively. When survival depends on one product, paywalls, feature gating, and pricing complexity become almost inevitable, even with good intentions. Part of why we built Voiden differently (https://github.com/VoidenHQ/voiden) is that it started as an internal tool. We used it ourselves for nearly two years, shared it with few teams to get feedback and incorporated it, before open-sourcing it. We also run an established API marketplace, which is our actual business. So Voiden isn’t something we’re trying to turn into a product line. The intent from the start has been to treat it as long-term community infrastructure — closer in spirit to tools like VS Code or Backstage — open, free, and evolving in the open. Interestingly, much of what the article describes as the “ideal API tool” maps closely to how Voiden ended up being designed. That’s largely because we never tried to build “a better Postman” or “an open Insomnia.” We wanted to rethink API tooling from the ground up: markdown-based workflows, reusable blocks, versioned artifacts, and workflows that work well for both humans and AI agents. No need for Postman's Postbot or whatever AI solution the tools are locking the users into - use the integrated terminal in Voiden to use claude or any other agent of user's choice. Maybe I’m going out on a limb, but I think this style of tooling will become the norm over the next few years, or at least push the category to evolve. AI is changing how fast we can build. It’s not changing what ultimately matters: trust, usability, sustainability, and developer experience. Teams will keep using tools that respect those fundamentals, and walk away from ones that don’t. And to be clear, I’m not sharing this to promote Voiden. The broader point is that we need more genuinely novel approaches to modern API challenges. Voiden is just our take on that problem. Other teams will arrive at different answers, and that’s healthy and I want people to be bold enough to shed the legacy tooling's "hangover".
In The API Tooling Crisis
dhruv3006·Feb 1, 2026Submission

Show HN: Voiden – an offline, Git-native API tool built around Markdown

Hi HN, We have open-sourced Voiden. Most API tools are built like platforms. They are heavy because they optimize for accounts, sync, and abstraction - not for simple, local API work. Voiden treats API tooling as files. It’s an offline-first, Git-native API tool built on Markdown, where specs, tests, and docs live together as executable Markdown in your repo. Git is the source of truth. No cloud. No syncing. No accounts. No telemetry.Just Markdown, Git, hotkeys, and your damn specs. Voiden is extensible via plugins (including gRPC and WSS). Repo: https://github.com/VoidenHQ/voiden Download Voiden here : https://voiden.md/download We'd love feedback from folks tired of overcomplicated and bloated API tooling !
48 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.