CheckOps home

Tools directory

V

CheckOps

Voiden

Voiden is an Apache-2.0, offline, Git-native API workspace where requests, tests and docs live in plain-text .void Markdown files built from reusable blocks, with no accounts, telemetry or cloud lock-in.

Visit website

Latest public signals

Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.

Visit Website

Introduction

Voiden is an offline API client that helps developers, QA engineers and technical writers build, test, document and collaborate on APIs in one place. Everything is stored in plain-text .void files, so there are no accounts and no required cloud sync: just local files, reusable blocks and Git.

The problem it targets is scattered API knowledge spread across five tools with zero coherence. In Voiden, requests, docs and explanations live side by side in Markdown and execute in place. Requests are composed from small reusable blocks, such as endpoint, headers, auth and parameters, which you can reuse, replace and version like code.

It supports REST, GraphQL, gRPC and WebSockets, each implemented as a plugin. A programmable interface with slash commands and an agent-friendly CLI fit existing engineering workflows. Voiden is built with Electron and TypeScript, states it has no telemetry and no VC funding, and offers an enterprise option and a test runner.

Because collections are text files in Git, API tests get the same review, branching and history as code, a natural fit for docs-as-code teams.

The source code is at VoidenHQ/voiden on GitHub under the Apache-2.0 licence, with about 1,800 stars; the most recent commit was on 11 November 2026.

Features

  1. Plain-text .void files: Markdown-based.
  2. Reusable blocks: Compose requests.
  3. Docs alongside requests: Executable documentation.
  4. Protocol plugins: REST, GraphQL, gRPC and WebSockets.
  5. Slash commands: Programmable interface.
  6. Agent-friendly CLI: Automation and AI agents.
  7. No account or telemetry: Fully local.

Pros

  1. Git-native: Review API changes in PRs.
  2. Free to use: Open source under the Apache-2.0 licence, so the core tool costs nothing to use.
  3. Actively maintained: The repository had commits as recent as 11 November 2026.

Cons

  1. Young project: Ecosystem still growing.
  2. Electron app: Heavier than a TUI.
  1. Download Voiden for your OS.
  2. Create a .void file and compose a request from blocks.
  3. Commit the file to your repository and run it from the CLI in CI.

Resources:

Pricing

Voiden is free and open source under the Apache-2.0 licence.

  1. Teams that version everything in Git and dislike cloud-locked API tools.

Conclusion

Voiden is a thoughtful, local-first take on API workspaces.

Try it for one service’s API docs and tests.

On CheckOps, Voiden is filed under the API & contract testing and Integration testing stages. Related tools listed here include Postman, Bruno, Insomnia, Hoppscotch, Yaak and HTTPie. A short trial on a real project, with your own code, data and pipeline, is usually the fastest way to choose between them, because fit matters more than feature lists. Facts here come from the official site, documentation and repository, checked on 11 November 2026.

Alternatives

Other tools on CheckOps that cover similar ground. Open a page, or compare one with Voiden side by side.