Self-hosted

A self-hosted tab manager that syncs every browser you use

Most tab managers keep your saved pages in their cloud. TabCabin keeps them in your browser, and when you want them everywhere, it syncs through a small server you run yourself — on a VPS, a home server or a Raspberry Pi.

Coming soon to Chrome

Server

One container with Hono and SQLite. Accounts with scrypt-hashed passwords, sessions, rate-limited login.

HTTPS

Caddy in the same Compose file fetches and renews certificates for your domain automatically.

Sync

Browsers push changes and pull everything newer; the newest edit of each item wins. Live updates arrive over server-sent events.

Backups

A script writes a consistent copy of the database every night and keeps the last seven.

~/tabcabin
# on your server
$ cd tabcabin && cp .env.example .env
# set DOMAIN and the first account, then
$ docker compose --profile caddy up -d
✔ Container tabcabin-tabcabin-1 Started
✔ Container tabcabin-caddy-1 Started
$ curl https://tabs.example.com/health
{"ok":true,"name":"tabcabin","version":"1.2.0"}

How it works

  1. 1Point a domain at your server and copy .env.example to .env with the domain and your first account.
  2. 2Run docker compose --profile caddy up -d. Caddy gets a certificate, the server creates the database and your account.
  3. 3Build the extension with your address (WXT_SYNC_SERVER, or the Build workflow on GitHub), click Sign in in a new tab and choose whether to keep this browser’s boards or use the server’s.
  4. 4Sign in on your other browsers. Changes appear everywhere within seconds; offline edits are sent when you reconnect.

Self-hosting questions

What hardware do I need?

Anything that runs Docker: a 1 vCPU / 512 MB VPS, a home server or a Raspberry Pi 4. The server uses a few dozen MB of memory.

Is it safe to expose to the internet?

Sign-up is off by default, passwords are hashed with scrypt, session tokens are stored only as hashes, logins are rate-limited and the API only accepts requests from the extension. Keep the host updated like any other server.

What happens when I am offline?

TabCabin keeps working from the browser’s local database. Changes wait in a queue and are sent when the server is reachable again.

Can several people use one server?

Yes. Create an account for each person with the built-in command; everyone only sees their own boards.

Comparing tools? See TabCabin vs OneTab, Toby and Workona.