Six steps from zero to a working deploy.
On first run, Optizen prints a one-time setup code to the API log and asks for it along with a new master password, so only someone with access to the machine can claim the instance. The password encrypts all credentials stored on disk. Keep it somewhere safe — there is no recovery path.
Go to Servers and add a host with the SSH user, port, and key path. Use a dedicated deploy user when possible. Optizen never stores your private key — only the path.
After saving, click "Test SSH". This confirms Optizen can reach the machine and pulls a telemetry snapshot. If it fails, check the key path and user permissions first.
Open the server and add a project. Choose the right type (compose, image, custom, etc.), set the working directory, and write out the exact deploy commands.
Add a health endpoint like /health or a TCP port check. This gives you a signal beyond "container is running" — Optizen polls it after every deploy.
Review the command preview, confirm the target, and watch the live log stream. Check the health status after it finishes. If everything is green, you are ready for production.
name: marketing-site type: compose working_dir: /var/www/marketing-site env_path: /var/www/marketing-site/.env health: GET /health deploy: docker compose pull docker compose up -d