A clear workspace for people
Your team gets one place for services, deployments, domains, databases, logs, and infrastructure.
A Heroku & Vercel alternative you run yourself
Deploy from Git, Docker, or Compose through a dashboard your team can trust. Then hand your coding agents an MCP, CLI, and API surface that drives the same control plane you do — on servers you own.
$ curl -sfL https://get.zensailor.com | bashSame control plane, either driver.
Explore a complete sample workspace built from the same screens your team uses to ship services, watch their health, and operate every connected node.
Control roomSee health, capacity, and activity across the platform at a glance.
3 nodes · 38 containers · 11 healthy servicesCoding agents can write the code. Shipping still stalls when production only exists as buttons and screens. ZenSailor gives your team a polished dashboard and gives agents authenticated, machine-readable access to the same platform.
Your team gets one place for services, deployments, domains, databases, logs, and infrastructure.
MCP tools, a matching CLI, and live API schemas give coding agents structured context instead of a dashboard to screen-scrape.
Organization-scoped credentials and role-aware actions keep agent access inside the same boundaries as the people who invited it.
Find out why checkout-api failed and prepare the safest next step.
get_system_statusLive revision healthy · latest deployment failedget_deploymentBuild log: DATABASE_URL is missingget_api_referenceEnvironment endpoint and exact input schema foundThe missing variable is identified. The healthy live revision was never touched.
Redeploys stay role-aware and are recorded in the audit trail.
There is no third step. No YAML to learn, no platform worker to configure by hand, no registry to stand up first.
Run one command on any Ubuntu or Debian server — from a Raspberry Pi to bare metal. The control plane is live in under a minute.
$ curl -sfL https://get.zensailor.com | bashConnect GitHub or paste an existing docker-compose.yml, then push. Buildpacks detect your stack, and health-gated blue/green swaps, SSL certificates, and safe serialized cutovers for single-writer stores happen automatically.
$ git push origin mainEvery other way of getting an app onto a server makes you give up one of them. Here is what each one costs you.
Ships fast — owns your stack
One click to deploy, and your app lives in their account. The bill grows with your traffic, egress fees make leaving expensive, and the platform decides what you are allowed to run.
Owns your stack — doesn't ship fast
A $5 VPS and total control, paid for in deploy scripts, certificate renewals, the health check you meant to add, and the pager at 2am.
Both, on paper
Credible, open-source platforms — and the right call when source access decides the purchase. ZenSailor's edge is the operating experience: safer releases, accountable templates, and one control plane for people and agents.
Compare workflow for workflowRead the case for both products. The better choice should survive a feature-by-feature comparison, not a vague superiority claim.
Push to Git. ZenSailor builds the image, boots the new version beside the running one, waits for it to pass health checks, then switches traffic. HTTPS is already handled. 160+ reviewed stacks are one click away. When one server stops being enough, add another and tag it.
Yes, ZenSailor is closed source. The Community Edition is still free forever for one developer, and that model pays for full-time development rather than a sponsorship drive. It changes nothing about ownership: underneath it is standard Docker, Docker Compose and Traefik, so your containers, volumes and data stay manageable without us — and stay yours if you leave.
| The moment | By hand | With ZenSailor What you get |
|---|---|---|
| Shipping a change | SSH in, git pull, docker compose up, watch and hope. | git push. Build, health check, traffic switch, done. |
| Downtime on release | The old container stops before the new one is ready. | The new version boots beside the live one. Traffic moves only once it is healthy. |
| HTTPS | Certbot, a cron job, and a renewal that fails on a Sunday. | Let's Encrypt certificates issued and renewed for you. Bring your own wildcard if you have one. |
| Adding Postgres, Redis or Grafana | Find a compose file from 2021, hope it still works, wire the volumes, guess the env. | One click from 160+ reviewed stacks: image versions pinned, storage mapped, secrets prompted. |
| When something breaks at 2am | docker logs | grep, and a lot of scrolling. | The crash is read for you and the fix is suggested in plain English. |
| Outgrowing one server | Swarm, Kubernetes, or a second pile of SSH scripts. | Add a node, tag it builder or runner, schedule onto it. |
| What it costs | Nothing — except your weekends. | $0 for one developer. Forever, on your own hardware. |
By handSSH in, git pull, docker compose up, watch and hope.
With ZenSailorgit push. Build, health check, traffic switch, done.
By handThe old container stops before the new one is ready.
With ZenSailorThe new version boots beside the live one. Traffic moves only once it is healthy.
By handCertbot, a cron job, and a renewal that fails on a Sunday.
With ZenSailorLet's Encrypt certificates issued and renewed for you. Bring your own wildcard if you have one.
By handFind a compose file from 2021, hope it still works, wire the volumes, guess the env.
With ZenSailorOne click from 160+ reviewed stacks: image versions pinned, storage mapped, secrets prompted.
By handdocker logs | grep, and a lot of scrolling.
With ZenSailorThe crash is read for you and the fix is suggested in plain English.
By handSwarm, Kubernetes, or a second pile of SSH scripts.
With ZenSailorAdd a node, tag it builder or runner, schedule onto it.
By handNothing — except your weekends.
With ZenSailor$0 for one developer. Forever, on your own hardware.
Build, route, observe, scale, and recover through one platform — whether the next action comes from you, a teammate, or an agent.
Connect GitHub or self-hosted Git. ZenSailor uses Cloud Native Buildpacks to detect your language and build optimized images automatically. No Dockerfiles, no maintenance, just push to deploy.
Deploy maintained stacks in one click. Applications live in the template picker, while 20 database and data-store engines have their own guided provisioning flow.
Version-pinned and ready to configure
Bring your existing projects. Paste a docker-compose.yml and we handle the routing, persistent storage, and health checks automatically.
Add remote Linux servers and tag them for build or run placement. NATS coordinates each agent while deployments, logs, metrics, drains, and domain routing stay in one dashboard.
builderrunner · gpuZenSailor starts the replacement beside the live version, then switches Traefik only after its readiness gate. Services backed by a single-writer store such as SQLite are automatically given a serialized cutover; multi-writer databases keep the full blue/green path. Let's Encrypt certificates are handled automatically.
Traffic moves only when the gate clears.
Connect your coding agent over MCP. It can inspect services, deployments, build logs, runtime logs, and system health; redeploy with your approval; and discover the live API schema when it needs a deeper operation.
REDIS_PASSWORD is missing. The live revision is still healthy; here is the exact environment endpoint to update.Let's Encrypt certificates are provisioned and renewed automatically. Need more? Upload your own wildcard certs from the Security dashboard.
Secure your data with automated DB dumps and volume snapshots to any S3 bucket. Scheduled and encrypted.
Use the dashboard, CLI, MCP server, authenticated API, or browser terminal. People and agents work with the same services, deployments, domains, and infrastructure instead of maintaining separate automation paths.
$ zensailor service deploy svc_01h...
Triggering deployment...
Deployment queued successfully.A maintained application and infrastructure library, not a directory of logos. Database engines have a dedicated provisioning flow; applications stay in the template picker. Every stack ships with its release, storage, variables, and routing defined.
Every catalog image sits on a real release line: zero untagged images and zero floating :latest tags. Your database stays on the version you deployed, restart after restart.
Databases, uploads, configuration, and media libraries are mapped to durable service storage where the application needs them.
Required passwords, API keys, and signing secrets are requested before deployment and wired into the services that consume them.
Web services arrive with Traefik routing, HTTPS, and the correct internal port. Protocol services clearly identify any direct host ports they require.
Your running deployment stays yours. Installing from a template creates standard Docker Compose services and persistent data on your server. Later catalog edits affect new deployments; they do not silently swap the software or erase the data in an existing service.
One developer, one node, unlimited apps and deployments, and all 160+ templates, free forever on your hardware. You only pay when you need a team, a cluster, or managed backups.
$0/forever
The complete platform for an individual developer.
Sends usage & diagnostic telemetry linked to your account. See what’s collected.
$29/month
Billed monthly
For startups scaling their infrastructure.
Sends usage & diagnostic telemetry linked to your account. See what’s collected.
Go Pro$129/month
Billed monthly
Mission-critical scale and unlimited power.
Telemetry can be disabled instance-wide.
Contact SalesThe things people ask before they run the install command.
Install ZenSailor on any Linux server, invite the way your team works, and give coding agents a real production interface. The individual edition runs unlimited apps and deployments for $0 — no credit card, no trial clock, and your containers and data remain yours.
$ curl -sfL https://get.zensailor.com | bash