Voiden

At a Glance:

Voiden is an offline, Git-native API client that stores requests, tests, and documentation in executable plain-text .void files, supports REST, GraphQL, WebSocket, and gRPC via plugins, and uses Git for collaboration without requiring accounts or cloud sync.

Overview:

Voiden is a desktop API workspace designed as an offline-first, local development tool. It keeps API requests, tests, markdown documentation, and pre/post-response scripts together in a single, human-readable .void file that is managed through Git. Built on Electron and written in TypeScript, the application requires no user accounts and sends no telemetry. Developers can compose and reuse API building blocks across files, execute scripts in JavaScript, Python, or Shell, and batch-run multiple files using the stitch runner. Voiden also imports existing collections from Postman and OpenAPI specifications, converting them into native .void files for a unified, text-based workflow.

Key Decision Points:

• Git-native collaboration: Team workflows rely on Git branches and pull requests, not on proprietary cloud workspaces or user accounts.

• Local-first operation: The workspace runs entirely offline with no required signup or cloud synchronization, using local file directories.

• Plain-text file format: All API definitions and related documentation are stored in .void files that are diffable, greppable, and editable by AI or standard text tools.

• Plugin-based protocol support: Core protocols like GraphQL, gRPC, and WebSockets are provided as installable or removable plugins, allowing you to configure only the needed capabilities.

• Desktop application: Voiden is an Electron-based desktop IDE-like environment available on macOS, Windows, and Linux, with integrated terminal and Git access.

Core Features:

• .void file format: Stores API requests, block definitions, markdown documentation, and metadata in a single executable text file.

• API building blocks: Decomposes requests into reusable components such as endpoint, auth, params, and body, which can be shared across multiple .void files.

• Pre-request and post-response scripting: Runs scripts written in JavaScript, Python, or Shell both before sending a request and after receiving a response.

• Stitch runner: Batch-executes multiple .void files sequentially with support for glob patterns, stop-on-failure, configurable delays, and environment selection.

• Protocol plugins: Supports REST, GraphQL, gRPC, and WebSockets through a plugin system that allows you to install or uninstall specific protocols.

• Importers: Converts existing Postman collections and OpenAPI specifications into native .void file collections.

Use Cases:

• Developers building and testing multi-protocol APIs locally in a single desktop workspace.

• Engineering teams that want to version API specifications, requests, and documentation together using Git.

• Developers transitioning from Postman who want to preserve existing collections in a plain-text, editor-friendly format.

• Users who require a fully offline API testing environment with no telemetry or backend service dependencies.

Open-Source Alternative Value:

Voiden offers a transparent and Git-friendly alternative by operating directly on plain-text files rather than opaque binary collections. It stores all API definitions, tests, and documentation in diffable .void files that can be reviewed, forked, and merged like source code. The application runs entirely locally with no required account, no telemetry, and no cloud synchronization. By avoiding proprietary team workspaces, Voiden lets users maintain a single source of truth for API work inside their own repositories. It also provides a migration path from Postman through its built-in collection importer, preserving existing work in a portable, file-based structure.