Introducing Sahabti

Self-hosting a service shouldn't be a project. Provisioning, networking, TLS, firewalls, public endpoints — the boring parts stand between you and a running service. We built Sahabti to handle them, so you don't have to.

Isolated by design

Every service on Sahabti runs in its own unprivileged container on a private VXLAN network. Tenants are isolated at the network layer, not just behind a password — neighbors can never reach each other.

Launch one from the dashboard, or from a script with a workspace token:

curl -X POST https://api.sahabti.com/v1/servers \
  -H "Authorization: Bearer $SAHABTI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"engine":"postgres","name":"orders","plan":"small","orgId":"<workspace-id>"}'

About seventy-five seconds later you have an isolated instance with a public hostname and a connection string — and you can watch each provisioning step land on the instance page while it happens.

Reachable from anywhere

Each instance gets a public hostname and port that proxies straight into your private network, so your laptop, your CI, and your app all reach it the same way. PostgreSQL and MySQL come up with TLS enabled and the platform certificate installed.

What's next

We're just getting started. Follow along here for product updates, engineering deep-dives, and stories from the team.