Understand how Optizen works before you rely on it in production.
Run your own Optizen on a VPS with Docker Compose and HTTPS.
For contributors: fork, clone, install dependencies, and run Optizen locally.
How to make changes, test them, and keep contributions easy to review.
Get from zero to a running deploy in six steps.
Manual, imported, compose, image, proxy, and custom — what each one means.
How to deploy, edit env files, read logs, and interpret health checks.
What CPU, load, uptime, memory, disk, inodes, and containers actually mean.
How to keep a VPS stable, predictable, and easy to recover.
Session controls, re-auth, demo privacy, and the audit trail.
Optizen organises everything into four distinct layers.
SSH trust and machine telemetry. If a server record is wrong, everything beneath it is suspect.
An application or managed infra unit. Holds deploy commands, runtime type, health settings, and key file paths.
Execution records. When it ran, what happened, whether the service checked in healthy afterward.
Env files, proxy configs, compose definitions. Kept explicit so another operator can understand the system quickly.