FAQ
Quick answers to the questions operators ask first.
Do I need a domain name to install?#
A real domain is recommended for public SSL, but not required. The
local-install flow detects .local/.lan hostnames and falls back to
self-signed or no TLS — see Installation.
Is ZenSailor free?#
The Community plan is free, fully self-hosted, and not time-limited — one node, one user, one organization, one concurrent deploy. Paid plans add nodes, team seats, previews and backups. See Requirements and Plans.
Where does my data live?#
On your servers. Volumes live under /opt/zensailor/volumes/, secrets are
encrypted at rest, and backups you configure go to your own S3 destination.
Nothing is shipped to the vendor. See
Persistence and Volumes and
Service Backups.
Can I use my own registry or Git host?#
Yes. Custom Git over SSH supports any provider, and services deploy from any public or private image registry. See Services and Sources.
What happens to a deployment when a node dies?#
Stateless services reschedule to healthy nodes. A service with managed volumes stays bound to its data node and waits (or is migrated to a new one through the volume migration flow) — see Storage Across Nodes.
Does ZenSailor use my data to train AI models?#
No. AI features either run on providers you connect with your keys, and diagnostics treat logs as untrusted transient data. See AI Providers.
How do updates work?#
In-dashboard, zero-downtime: the control plane flips blue/green, agents self-update. See Updating.
Can I undo a bad deploy?#
Yes — the previous release stays healthy when the new one fails its health gate, and restores/rollbacks are never delayed by windows. See Deployment Pipeline.
Only one person in the team needs this?#
The Community plan is a solid single-operator setup. When the team grows, Pro adds members, more nodes and previews — a license key activates it in-place with no reinstall. See Licensing and Activation.