Showcase

What Portoser actually looks like

Captured from a 6-host demo cluster. The web UI and the CLI are two faces on the same registry.

Web UI

Drag-deploy

Drag a service onto another machine. The deployment panel stages a plan; clicking Deploy runs it via SSH.

Health Dashboard

Per-service health, problem frequency from the knowledge base, and a one-click diagnostics path.

Service dependencies

Hierarchical graph of every service with its upstreams and downstreams.

Monitoring

CPU, memory, disk, and availability for every machine and service, refreshed live over WebSocket.

Knowledge base

Browse playbooks generated from past incidents. Each carries occurrence counts and success rates.

CLI

Terminal capture: 01-deploy

portoser deploy

Auto-heal enabled deploy: observe → grasp → solve → standardize. Clean success path.

Terminal capture: 04-diagnose

portoser diagnose

Analyzer fingerprints a failing dependency, scores health, and points at the matching playbook.

Terminal capture: 02-learn-flow

portoser learn

Knowledge base summary, playbook list, and per-service insights.

Terminal capture: 03-cluster-status

portoser status

17 services across 6 hosts in one view, scoped to the registry.

Terminal capture: 05-health-watch

portoser cluster status (watch)

Cluster health re-run on a fixed interval — same loop watch(1) gives you on a single host.

Try it locally