A control plane for your
self-hosted VPS fleet.
Optizen gives small teams a clear operating model for servers, projects, and deploys. SSH trust, runtime health, env files, and proxy config — all visible and under control. No cloud dependency. Runs on your own machine.
No account or sign-up. Clone it and run it on your own server.
The model
Four layers, clearly separated
Each layer owns its responsibility. Mixing them is how production incidents start.
Store SSH trust once. Optizen keeps the host, user, key path, and connection state in one place — and tests connectivity on demand.
Model each app with its runtime type, deploy commands, working directory, env path, and health expectations. No more undocumented deploy notes.
Every deploy is a reviewable, logged execution record. Commands, outcome, live stream, and health result — all stored for rollback.
Env files and proxy configs edited with previews, remote backups, and revision history. No more guessing what changed last week.
Runtime support
Works with what you already run
Docker Compose, Caddy, Nginx, raw images, and custom scripts. If it runs on your VPS, Optizen can manage it.
Point Optizen at a working directory. It runs docker compose pull and docker compose up -d — with a live log stream and health check after.
Load the config file, edit it in-browser, preview the diff, save with a backup, and reload the proxy — all without touching the terminal.
Pull a specific image tag or roll back to a previous one. Optizen tracks image history alongside deploy records.
Any shell commands you'd normally run over SSH. Write them once, review them before every run, and keep the log forever.
How it works
From SSH key to safe deploy in four steps
Add a host with SSH credentials. Optizen tests connectivity and takes a telemetry snapshot: CPU, RAM, disk, uptime, load average, and container counts.
Run a scan to discover running Docker workloads — Optizen infers the runtime type, working directory, env path, and compose structure. Or model projects manually for full control.
Set a health endpoint like /health or a TCP port check per project. After every deploy, Optizen polls it and stores the result alongside the deploy record.
Review the exact commands, confirm the target, watch the live log stream. Re-auth can be required before any destructive action. Rollback if needed.
Deploy config
Define it once, deploy with confidence
Every project has a deploy contract — the exact commands, health check, working directory, and env path. Optizen shows you this before every deploy so there are no surprises.
- Commands are reviewable before execution
- Working directory is explicit, not assumed
- Health check runs after every deploy
- Env path is tracked — editor shows current live value
- Full log stream stored per deploy record
name: api-service type: compose server: prod-01 working_dir: /srv/api-service env_path: /srv/api-service/.env health: GET /health :3000 deploy: docker compose pull docker compose up -d --remove-orphans
Infra file editing
Edit env files and proxy config safely
Stop editing .env files over raw SSH with no undo. Optizen’s built-in editors give you guardrails for every write — including Caddy and Nginx config with live reload.
Proxy management
Caddy and Nginx, in the browser
Optizen auto-detects running Caddy and Nginx services. Load the config file, edit it, preview the diff, save with a backup, and reload — all from the dashboard.
Observability
Know the state of every server at a glance
Optizen collects a telemetry snapshot every time you test SSH or open the dashboard. No agents, no sidecar processes.
Email alerts
Stay informed on deploy outcomes
Connect your own SMTP server to receive instant email notifications. Get notified automatically when deploys succeed or fail, and when your servers experience critical disk storage pressure.
Webhooks
Outbound webhook integrations
Trigger external workflows in Slack, Discord, or your own microservices. Outbound webhooks send rich JSON payloads and support HMAC signature verification for security.
Security
Trust-first from the ground up
Every dangerous action has a confirmation, a preview, or a re-auth gate. Nothing happens silently.
Deploys, rollbacks, deletes, env writes, and proxy reloads can require a fresh password check. Configurable per workspace.
Passwords and passphrases are encrypted at rest. SSH private keys are never stored — only the path is referenced.
Session elevations, security setting changes, and sensitive value reveals all appear in the security audit log.
Mask all sensitive values in the UI while screen-sharing or recording — without touching actual data.
Why Optizen
Replace SSH rituals with a real operator workflow
- Deploy commands live in Slack messages and Notion docs
- Env changes made over SSH with no history
- Proxy reloads done manually, sometimes forgotten
- "Is it healthy?" means checking container state and hoping
- Shell history is the only audit trail
- Rollback means digging through git and guessing
- No alerts when deployments fail or disks fill up
- Deploy commands are modeled, versioned, and reviewable
- Env edits have previews, backups, and revision history
- Proxy reloads are a dashboard action with validation
- Health checks run automatically after every deploy
- Every dangerous action appears in the audit trail
- Rollback picks a previous deploy record and re-runs it
- Instant email and webhook alerts for failures and disk pressure
Ready to stop guessing what’s running in production?
Optizen is free, open source, and runs entirely on your own infrastructure. No SaaS, no subscription, no vendor lock-in.