Self-Host ApiTab

Own Your API Tooling

A self-hosted, open-source alternative to Postman — for any team that wants full control over their own API tooling.

Free & open source Self-hosted Already built
Why This, Why Now

Cloud API tools come with a recurring cost — in money, speed, and control

Per-seat pricing that scales with headcount

Postman charges per user, every month, indefinitely — the price of standing still goes up as the team grows.

Heavy and slow to run

Postman is widely reported as slow to launch and resource-hungry, especially with larger collections. ApiTab is built lightweight from day one.

Sensitive data leaves our network

API keys, tokens, and request payloads pass through a third party's cloud by default.

We don't control the roadmap

Feature paywalls, pricing changes, and end-of-life decisions happen to us, not with us.

The Proposal

ApiTab — the same daily workflow, hosted entirely on your own infrastructure

ApiTab is a full-featured API client — a desktop app and a browser extension — backed by a small self-hosted server you run yourself. Same collections, environments, and scripting your team already knows. Existing Postman collections import in one click, so switching costs nothing but a few minutes.

100% open source · MIT licensed Free — no per-seat cost Self-hosted on your infra One-click Postman import
Why It's Worth Doing

What you get

Zero licensing cost

No per-seat fees, no annual renewal negotiation. Free, indefinitely.

Full data control

API keys, tokens, and requests never leave infrastructure you own.

No vendor lock-in

Open source (MIT) — you can audit, modify, or fork it at any time.

You own the roadmap

Uptime, retention, backups, and priorities are yours to decide.

Feature Parity Where It Counts

Everything the team already uses, day to day

Full request builder

All HTTP methods, auth, JSON/form/raw bodies

Collections & environments

{{variable}} interpolation with autocomplete

Pre/post-request scripts

Postman-script-compatible test scripting

Code generation

cURL, Fetch, Axios, PHP, Python snippets

Request history

Automatic, searchable, restorable

Team collections

Share, sync, and collaborate live

One-click import

cURL commands and Postman collections

Desktop + browser

Windows, macOS, Linux, Chrome, Firefox

Fake data generators

{{$randomEmail}}, {{$guid}} and more — same $-syntax Postman uses

How It Stacks Up

ApiTab vs. Postman

Capability ApiTab (self-hosted) Postman
Pricing Free, open source $19–$49 / user / month
(Team–Enterprise, billed annually)
Where your data lives Your own server Postman's cloud
Source code Fully open (MIT) Closed source
Collections, environments, history
Pre/post-request test scripts
Team sync & sharing
Fake data generators
Mock servers & API monitors Not yet

You don't need feature-for-feature parity — just the part of Postman your team actually uses, without the rest of the bill.

How It Works

Already built. Already running.

Desktop App Windows · macOS · Linux
Browser Extension Chrome · Firefox
Server Laravel · MySQL

Framework

Laravel 12 on PHP 8.2 — mature, widely supported

Database

MySQL — standard, easy to back up and migrate

Auth & API

Token-based (Sanctum), open REST API under /api

Light footprint

Runs comfortably today on ordinary shared hosting

Proven today Runs on ordinary shared hosting No dedicated server required
Recommended for teams Your own server Full control over your data & uptime
A Look Inside

What using it actually looks like

ApiTab request builder
Request builder
ApiTab environments and variables panel
Environments & variables
ApiTab pre and post-request test scripts with passing tests
Pre/post-request scripts
ApiTab generated cURL snippet
Generated cURL & code
ApiTab collections and folders
Collections & folders
ApiTab in dark mode
Dark mode
Get Started

Ready to own it for your team?

The software is already built, open source, and free. If it looks useful for your team, here's what it takes to self-host it.

What it takes to self-host it for your team

  1. 1

    Spin up a small server (or reuse existing infra) and point a subdomain at it

  2. 2

    Pilot it with your team for a few weeks alongside your current tooling

  3. 3

    Decide on full rollout based on real usage

Thank You

Try it, break it, and tell us about it

ApiTab
01 / 09