Overview:
Voiden is an offline, Git-native API workspace for building, testing, documenting, and collaborating on APIs. It stores requests, notes, and reusable API components in plain-text .void files, eliminating the need for accounts or required cloud sync. Designed for developers, testers, and technical writers, Voiden treats API work like code, integrating request blocks, Markdown documentation, and Git-based collaboration into a single local-first desktop application.
Core Features:
Git-native collaboration: Use branches and pull requests for team workflows instead of proprietary workspaces, with all files stored as plain text.
Reusable API blocks: Share headers, authentication, body parameters, and entire sections across files using linked blocks and linked files.
Multi-protocol support: Build REST, HTTP, GraphQL, WebSocket, and gRPC requests within the same workspace, including GraphQL schema import and visual query builder.
Scripting and automation: Run pre-request and post-response scripts in JavaScript, Python, or shell, and stitch multiple files into batch runs with aggregated results.
Import from existing tools: Import OpenAPI specs and Postman collections (JSON v2.1) to generate native
.voidfiles, preserving headers, auth, query parameters, variables, bodies, and response examples.
Use Cases:
Developers building and testing REST or GraphQL APIs while keeping request files alongside code in a Git repository.
Technical writers documenting API endpoints with live request blocks and Markdown notes in the same file.
Teams collaborating on API design through Git pull requests, avoiding proprietary team workspaces.
Testers running batch assertions across multiple requests and viewing aggregated results from the desktop app.
Why It Matters:
Voiden provides a local-first, file-based alternative to API tools that rely on cloud sync, accounts, and proprietary storage. By using plain-text .void files that work with Git, it fits into existing developer workflows without requiring new collaboration infrastructure. It supports importing from Postman and OpenAPI, allowing teams to migrate existing collections into a Git-native format. The project is transparent about its Electron foundation, prioritizing cross-platform stability and deep system access (Git, terminal) over a lighter stack.
