What's new in Sahabti.

Every meaningful change to the platform, in reverse-chronological order. Subscribe to the RSS feed and we'll keep you posted.

Subscribe to RSS Browse history

May 28, 2026

v0.2.0-betaFeature

Quota-based billing, live provisioning logs, and API tokens

A shared pool of vCPU, memory, and disk instead of per-service bills, a real-time provisioning timeline, live instance metrics, and scoped tokens for automation.

Quota-based billing, live provisioning logs, and API tokens

Three things that make running more than one service on Sahabti easier to manage.

What's new

Quota-based billing. Your plan grants a shared pool of vCPU, memory, and disk — spin up as many instances as fit, instead of paying per service. Start free, upgrade when you outgrow it.
Live provisioning timeline. Watch each step — network setup, container creation, engine install, health check — stream in on the instance page as it happens, instead of a spinner.
Live instance metrics. CPU, memory, disk, and network read straight off the hypervisor, over whichever window you pick — no agent to install.
Scoped API tokens. Create a workspace token to drive instances from a script or CI, and revoke it from the same page the moment you're done with it.

Read how to wire up a token in the API docs.

May 12, 2026

v0.1.0-betaFeature

Managed services, isolated by design

PostgreSQL, MySQL, MariaDB, Valkey, Memcached, and RabbitMQ — each in its own private network, with a public endpoint, ready in about 75 seconds.

Managed services, isolated by design

Sahabti is live: pick an engine from the catalog and get a running, isolated instance in about 75 seconds — no networking, TLS, or firewall config to write yourself.

What's new

Six engines at launch. PostgreSQL 17, MySQL 8.4, MariaDB 11, Valkey 8, Memcached, and RabbitMQ. The rest of the catalog is listed in the dashboard and marked coming soon until its provisioning script ships.
Isolated by design. Every instance runs in an unprivileged container on its workspace's own private network. Tenants can never reach each other — isolation is enforced at the network layer, not just a password.
Reachable from anywhere. Each instance gets a public hostname and port that proxies straight into your private network, and the SQL engines come up with the platform certificate already installed.
Fast provisioning. Pick an engine and a size; the network, container, and endpoint are provisioned automatically, and connection details are ready the moment it's up.

Launch your first instance from the dashboard — the catalog, sizing, and connection details are all one page.