What shipped, and when.

First public release

• AddedA published Docker Compose install: two generated secrets and a database password, one command, no source checkout, no registry login and no account. The images are public.
• AddedAgentless server management over plain SSH. Nothing is installed on the machines you manage, and read-only discovery reports OS, kernel, runtimes, containers and database engines without changing anything.
• AddedTen project types from one control plane: bare servers, Frappe/ERPNext, Docker, Kubernetes, application deployments, databases, hypervisors, and AWS, Azure, GCP and Oracle.
• AddedEvery action runs as a queued job with live log streaming, and what you watch is exactly what lands in the audit ledger.
• AddedBackups with verified restores — a backup is only marked verified after it has actually been restored into a throwaway instance and checked — plus point-in-time recovery for managed Postgres and tiered retention per database.
• AddedDestructive operations are plan-then-apply: you see exactly what will be destroyed, and how each item was identified, before anything runs. A server reset requires a verified backup first.
• AddedAn optional AI engine on your own API key, across multiple providers. It cannot act directly — it writes a proposal, a human reviews the exact diff, and only on approval does the work enter the same job queue a human would have used. No model provider is contacted unless you configure one.
• AddedPer-project dashboards, scheduled reports, and a read-only assistant for asking questions about your own fleet without granting write access.
• SecurityThe backend refuses to start on a missing or published-default JWT_SECRET or ENCRYPTION_KEY, before it opens a network connection — rather than warning and carrying on with a signing key that is published in a public repository.
• SecuritySSH keys, cloud credentials and database passwords are encrypted at rest under your ENCRYPTION_KEY, decrypted in memory only for the duration of a job, and never written to a log line or a job payload.
• SecurityPer-resource permissions are enforced on visibility, proposal, approval and execution independently, and every route is organization-scoped. The control plane itself is not indexable and serves no public page — the first thing it presents is a login form.
• AddedOne switch selects self-hosted or multi-tenant mode against a single shared schema, so the isolation a hosted deployment relies on is the same code a self-hosted install runs.