Voiden is an open-source desktop API workspace that stores requests, tests, notes, and documentation together in plain-text .void files. It is offline-first and Git-native: there are no accounts, no required cloud sync, and no telemetry, so teams collaborate through branches and pull requests instead of proprietary workspaces.[1][2]
Quick verdict
Voiden is an open-source, offline-first API client that replaces cloud-synced collections with plain-text .void files versioned in Git. It suits developers and QA engineers who want multi-protocol requests, scripting, CI execution, and agent access without accounts or telemetry; teams needing hosted collaboration or a support contract should look elsewhere.[1][2]
What Voiden does
Requests, tests, notes, and documentation live together in human-readable .void files that can be opened in any editor and versioned in Git.[1]
Reusable API building blocks for endpoints, authentication, parameters, and bodies behave like code: they are inheritable, versionable, and composable across files.[1]
One workspace covers REST, GraphQL, gRPC, and WebSocket workflows, including subscriptions and response examples.[1]
Pre-request and post-response scripting runs in JavaScript, Python, or shell, with assertions, environment switching, and hotkeys for a keyboard-driven flow.[1]
The Stitch runner executes .void files in batch, and the headless Voiden Runner CLI runs the same files in terminals and CI pipelines on Node 18 or later.[1]
MCP support lets coding agents run project requests directly from the terminal or serve them as tools to assistants such as Claude Code and Codex.[1]
Installers cover macOS (Apple Silicon and Intel), Windows, and Linux (.deb, .rpm, .AppImage), plus Homebrew, winget, Chocolatey, Flatpak, apt, snap, and Nix.[1]
Teams coming from Postman can export a collection as JSON v2.1, drag it into Voiden, and generate native .void files with headers, auth, params, bodies, and response examples preserved.[1]
Who it fits
Developers, QA engineers, and technical writers who design, test, and document APIs and want their API workspace to behave like source code.[1]
Teams working with internal or sensitive endpoints that should never sync to a vendor cloud by default.[1]
Agent-assisted engineering teams that want coding assistants to execute versioned API requests or call them as tools.[1]
Limitations to weigh
Teams that rely on hosted shared workspaces with built-in cloud sync, comments, and access controls will not find that model here; collaboration is deliberately file- and Git-based.[1]
No enterprise support offering, pricing page, or paid tier is documented in the inspected official sources, so organizations that require a support contract should verify before adopting.[1]
Questions worth asking
Is Voiden really offline?
Yes. Voiden works with local files, requires no account, performs no required cloud sync, and collects no telemetry, so requests can be built and run fully offline.[1]
Can I migrate an existing Postman collection to Voiden?
Yes. Export the Postman collection as JSON v2.1, drag it into Voiden, and generate native .void files; headers, auth, params, bodies, and response examples are preserved.[1]
Sources and editorial review
Source research. Reviewed on October 13, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Voiden official homepage
official · Observed October 13, 2026
Official homepage presenting the offline Git-native API workspace, plain Markdown .void files, MCP support, runner CLI, and one-click import from Postman, OpenAPI, and Insomnia.
- VoidenHQ/voiden GitHub repository and README
official · Observed October 13, 2026
Public repository metadata and README: Apache-2.0, 1807 stars, offline Git-native workspace, Electron/TypeScript stack, multi-protocol support, scripting, Stitch runner, headless CLI, MCP support, desktop installers, no accounts or telemetry, and the Coming-from-Postman migration guide.