Sbarbase صباربيز

What it is

Sbarbase is an open source, self-hosted layer that runs the original Supabase services (PostgreSQL, Auth, PostgREST, Storage) for many projects on one server.

• One ordinary server. No second machine and no cloud service needed. Clients hold projects, projects hold environments (production, staging).
• No data mixing. Each environment has its own database, its own logins and its own keys. A key from one project never opens another.
• Shared resources. The existing topology shares PostgreSQL and Storage across environments. Capacity depends on measured workloads; no fixed project count is validated.
• A busy project uses the free room, never its neighbours' share. Each environment has a guaranteed share of the gateway, and a busy one may borrow what the others are not using. Every project that was active in the last minute keeps its whole share. If one keeps choking, you get a message by email, webhook or Telegram.
• Original Supabase APIs. Tested workflows use supabase-js and SQL. Full cloud feature compatibility remains a development goal.

Install

On a compatible Linux host with rootful Docker Engine and Compose, three commands (Install with Docker):

git clone https://github.com/M7MMAD-OMAR/sbarbase /opt/sbarbase && cd /opt/sbarbase
docker compose up -d --build
docker compose exec sbarbase python3 lab/bootstrap.py

The earlier native supervisor installation path, on an empty Fedora server (plan on 4 cores and 8 GB). Each step is explained in the quickstart.

sudo dnf install -y moby-engine git python3-cryptography && sudo systemctl enable --now docker
sudo useradd -m sbarbase && sudo usermod -aG docker sbarbase && sudo install -d -o sbarbase -g sbarbase /opt/sbarbase && sudo -u sbarbase git clone https://github.com/M7MMAD-OMAR/sbarbase /opt/sbarbase
sudo -u sbarbase -H bash -c 'curl -fsSL https://bun.sh/install | bash -s bun-v1.3.14'
cd /opt/sbarbase && sudo -u sbarbase /usr/bin/python3 lab/operator_file.py /home/sbarbase/operator.json
sudo deploy/server-acceptance.sh --rehearse --install-unit --first-project --service-user sbarbase --home /home/sbarbase --bun-dir /home/sbarbase/.bun/bin --bootstrap-file /home/sbarbase/operator.json

The last command installs the service, creates a first project, proves supabase-js works through it and checks that the service comes back after a reboot.

Project setup and sign-in

New projects automatically create and provision a production environment, then start and open the original Supabase Studio in a new tab while keeping the console open. Choose Stay in console to cancel automatic opening. Existing projects retain Open Supabase dashboard. Studio opens as its original full page, without an added navigation bar or iframe. Management MFA is required by default; the installation owner can make it optional with a fresh authenticator verification under Account security. Enrolled accounts still verify MFA. See Studio, management MFA, the UX research and journey audit and the complete implementation plan.

Documentation

Explanations	why it exists and how it is built, with diagrams
Guides	quickstart, choosing a server, upgrades, backup and restore
Reference	glossary, configuration, API, status
Decisions	what was chosen, what was rejected, and why
Security · Contributing · Changelog

Reader guides and references are in English and Arabic. The dated engineering notebook is primarily in English. See the project layout for the repository structure.

Status

The current version is 0.9.1 (changelog). AI agents such as Claude Code can deploy to it through an access token and its MCP endpoint (AI agents). It runs on a real server with up to eight environments, encrypted off-site backups whose restore was tried there, and notifications by Telegram, and that server updated to 0.7.1 through the update channel and passed its health checks. The upgrade work (graceful stop, shared ports, in-place handover, rolling replacement, database window) is proven by unit tests and by that one update, and has not been measured under load or by fault injection on a server. The next release (0.8.0) is planned to turn the handover and the rolling replacement of rest on by default, with opt outs (upgrades). Docker install and VM rehearsals have scoped passing evidence. The project is not independently accepted for production. What works, with every number, is in status.

Current work is the upstream currency plan; longer-term priorities are in the product and portability plan, with the execution contract defining how each claim is verified.

Support

Sbarbase is free and built in the open. If it is useful to you, you can support its development:

Or buy a coffee.

A report of something that does not work is worth as much; see Contributing.

License

Apache-2.0. Supabase, PostgreSQL and other dependencies keep their own licenses.