Goodbye Postman collections, hello Markdown specs

TL;DR

Postman’s collections are bloated, paywalled, and siloed from your codebase. Voiden is an offline, lightweight Postman alternative. It uses Markdown-style files to enable you to spec, test, and document your APIs in a single place, leveraging a code-like workflow that you already know and understand.

The Problem: Postman Collections Create Friction

Postman's collection-based approach using JSON or YAML files, cloud dashboards, and a complex UI promises seamless API workflows, but it often slows developers down with unnecessary hurdles:

• Paywall barriers: The free plan caps you at 25 collection runs, 3 collaborators, and one private API. Need more? Pay $14–$49 per user per month. Scaling the team is a budget burden.
• Siloed specs: Collections live in Postman’s cloud, detached from your repo. Syncing them to Git requires manual exports, breaking your workflow’s rhythm.
• Cluttered and rigid: The UI buries simple tasks in menus, and collections don’t support reusable components. Docs are separate, leaving you without a single source of truth.

Think of this scenario: You’re debugging an API mid-sprint, but Postman’s free tier stops you at 25 runs. Your teammate’s changes are stuck in the cloud, and syncing them to your repo means tedious copy-pasting. And needing an internet connection to test the localhost endpoint… that’s a bottleneck, not a workflow.

Postman’s enterprise focus and heavy UI frustrate indie hackers and small teams. Voiden’s markdown-based, Git-native workspace keeps APIs simple, code-adjacent, and free of SaaS constraints.

Workflow: How do I switch from Postman to Voiden?

Voiden lets you trade Postman’s collections for markdown-style .void files in your repo, using a workflow that feels like coding. Here’s how to make the switch:

Step 1: Import a Postman Collection

Export your Postman collection and add it to a Voiden project.

Step 2: Generate Voiden files

In the top right corner of the imported Postman collection, there should be a Generate Voiden files button. Click it.

The result is a newly generated Directory holding all of the collection’s API specs.

Note that I also created a .env file, which holds a token needed for running this endpoint successfully.

Step 3: Edit, Test, Document, and Commit

Now you can edit generated .void files, adding docs, tests, changing the payload, etc.

Hit the Ctrl/Cmd + Enter to run it.

The right-hand side opens a panel with response (and request) details.

When happy with the state of the API, head over to the in-app terminal, commit the changes, and collaborate as developers do. Via Git.

That’s it.
This approach skips Postman’s cloud dependency and UI clutter, keeping your APIs in your repo, where they belong.

Why This Wins

Voiden’s markdown-based workflow fixes Postman’s pain points for those among you who value code over dashboards:

No paywalls: Free, no limits, no per-user fees. Postman’s $14–$49/month plans are a burden.
Fast migration: One click converts Postman collections to .void files, no hassle.
Code-like simplicity: Markdown is clean, reusable, and editor-friendly. Git tracks every change, unlike Postman’s siloed setup.
Offline control: Specs stay in your repo, not a random cloud. And you can work anywhere, with no sync issues.
Postman’s costs and complexity slow you down. Voiden’s lean, Git-integrated approach keeps you moving.

Getting Started

Ready to drop Postman? Try Voiden:

• Install Voiden: Download the offline app from voiden.md and set up an API repo.
• Migrate your first Postman collection: Start with a single API spec.
• Collaborate via Git: Commit your spec, open a PR, and let your team review it using your existing Git tools.

Join our GitHub Discussions to share feedback and shape Voiden's future. Download Voiden and start building APIs the right way.