Anso
bb85e08b36
* feat(gitops): capture a recovery point before Git-managed rollout applies A rollout rollback needs a recovery point that names the generation the node was running before the deploy, and Git-managed rollout applies did not create one. applyLocalUnderLock now captures the pre-deploy project (with the hub-supplied GitOps binding) before the incoming compose reaches disk, owns the recovery lifecycle from acquire through verified, and compensates from the recovery point when the apply fails. A remote target does the same over apply-local, and the request carries the binding because a leaf has no GitOps rows of its own. The binding resolves the deployed pointer for Direct mode and the ack's applied pointer for Blueprint mode: nothing writes the deploy-bound pointer for a Blueprint-managed stack. A re-capture that cannot resolve the owning application (a leaf backup, for example) carries the previous binding forward, since re-capturing does not change what the node is running. * feat(gitops): add rollout lifecycle controls and rollback coordination Adds the operator lifecycle routes for a Git-managed Blueprint rollout: pause and resume (application or one target), replan (re-derives placement and reopens review instead of invalidating an accurate one), supersede (withdraws the live authorization and reports the abandoned rollout), and rollback. Rollback restores an explicit prior application generation on one target, the failed targets, or every changed target in the frozen set. Selectable generations come from the application's rollout-generation history; targets already running the selected generation are out of scope; every target is authorized before any work starts; and the abandoned generation is superseded first so nothing can dispatch it mid-restore. Each target is restored from its own captured recovery point, in process for the local node and through the node's stack rollback route for a remote, where the node must confirm it restored the requested generation. Every exit records a terminal per-target result, and a partial failure lifts the application out of recovery rather than leaving a restore nobody drives. The application detail read and the Blueprint summary now carry the prior generations a rollback can select, plus the bound Blueprint's enabled state so the surfaces can withhold execution controls. * feat(gitops): add rollout controls to the GitOps application surfaces The GitOps application view and the Blueprint sheet's GitOps section gain a rollout controls row: pause and resume as first-row actions, with replan, supersede, and rollback behind the overflow menu and each destructive choice behind a confirmation. Rollback selects a prior generation and a target scope (one target, the failed targets, or every changed target) and states the configuration-versus-data boundary before anything runs. Controls are offered only from the projection's own statuses and gated by the permission the route requires, and execution controls are withheld while the bound Blueprint is disabled. The superseded rollout copy now covers an operator withdrawal as well as replacement. * docs(gitops): document rollout lifecycle controls and rollback Covers pausing, resuming, replanning, and superseding a rollout, the rollback generation and scope selection with its configuration-versus-data caveat, and the drift-enforce interaction that re-applies the current revision after a rollback. The GitOps portfolio page names the in-place actions on a Git-managed application, and What's New gains an entry for the lifecycle controls. * fix(gitops): sanitize logged error messages on rollout recovery paths CodeQL flagged log injection on the new rollout lifecycle and recovery handlers: a remote node's response body, a recovery row, or a candidate payload can reach the logged Error object, so the logs now record the sanitized message string instead. No behavior change. * fix(gitops): sanitize the logged target id on rollout recovery paths The target node id on these paths can come from the rollback request's scope selector, so CodeQL reads it as a user-provided value flowing into the log entry even though it is a number. Pass it through sanitizeForLog, the same barrier the other logged values use. No behavior change. * fix(gitops): hold rollout dispatch while it is paused Pause was recorded and rendered but no execution path honored it: boot-time reconstruction re-dispatched a paused rollout, and the sequential dispatch loop kept deploying targets the operator had paused. The adapter now blocks while the application is paused, re-reads the pause before every target, skips individually paused targets, and reports a hold instead of progress when nothing was dispatched because every remaining target is paused; reconstruction skips paused applications outright. A dispatch that pauses during the preflight window no longer mints or supersedes the authorization it is holding. The continuation a target resume triggers is covered by the route test: the queue is dispatched again and any still-paused target is skipped. * fix(gitops): continue the queue on target resume and refuse empty pauses A per-target resume cleared the pause but never continued the rollout, so the target it released waited for the next restart to be retried; the route now runs the same continuation as an application resume, and the adapter skips targets that are still individually paused. Pausing an application with no authorized rollout and no partial record is now refused with ROLLOUT_PAUSE_REFUSED: recording a hold on nothing makes the surface read as held when no rollout ever ran. * docs(gitops): state the per-node restore limit for rollout rollback A node keeps only the recovery generation captured immediately before its latest rollout, so an older selectable generation has nothing to restore from and is reported as a failed target. The rollback dialog and the feature page now say so instead of implying every listed generation is restorable.
Self-hosted Docker Compose management for one machine or a fleet.
Docs · Tutorials · Website · Roadmap · Discussions · Sponsor · Buy Me a Coffee
Note
Sencho is used in production for day-to-day Docker Compose and fleet management. As a pre-1.0 project it still evolves quickly, so review the known limitations and validate against your own setup before deploying it on critical infrastructure.
What Sencho is
Sencho is a Docker Compose control plane for DevOps engineers, platform teams, system administrators and homelab users who run services on Compose and need a real operational surface: a graphical interface that does not give up file-on-disk workflows, and the ability to manage more than one machine without SSH gymnastics or a VPN.
It runs as a single container on your hardware and provides a UI for common Compose operations: deploying, editing files, watching logs, restarting containers, browsing volumes, and recovering from failures. Your compose files stay on the host filesystem and remain the source of truth.
Multi-node was part of the architecture from the start, not bolted on later: every Sencho instance is the same autonomous node, whether it runs alone or as one of many in a fleet. To manage another machine, you install a second Sencho on it and connect them with a long-lived API token; the primary dashboard then acts as an authenticated HTTP and WebSocket proxy across your fleet. Use TLS, a VPN, or a private network for any untrusted link. Each node still uses its local Docker socket (see Quick start), but Sencho does not require SSH and does not expose a remote Docker socket on the network. For nodes behind NAT or strict firewalls, the Pilot Agent establishes a single outbound WebSocket tunnel to the primary, so the remote host opens no inbound port at all.
Sencho is free, open-source software under AGPLv3. Everything below is included in the Community tier with unlimited nodes and users.
Capabilities
Stacks
- Full Compose lifecycle: create, deploy, restart, stop, take down, pull
- Atomic deployments with automatic rollback on failure
- Monaco editor with diff preview before save and one-click rollback to any prior deploy
- Health-gated updates that hold a rollout until health checks pass, with stalled-update detection and in-app recovery
- Git-sourced stacks pulled and synced from any repository, with ordered multi-file Compose
- File explorer for compose, env, and supporting files, with move and rename across directories
- Drift detection that compares running containers against the effective Compose model and flags exactly what changed
- Environment and secrets guardrails that inventory every variable a stack uses and flag missing or duplicate values, without ever exposing a value
- Storage portability checks that show whether a stack's mounts can move cleanly to another node before you move it
- Compose Doctor preflight checks that catch compose problems before deploy
- Stack labels for grouping and bulk operations
- App Store with LinuxServer.io templates by default, or any custom Portainer-compatible registry
Observability
- Aggregated log search and stream across every container in the fleet
- Live container stats, health checks, and image-update notifications on a configurable cadence, with links from each image to its registry and source
- Threshold alerts for CPU, memory, and network
- Read-only audit log of every action, with a 14-day recent-activity window
- Network topology view of containers, networks, and nodes
- Documentation-drift flags when a stack dossier diverges from the running stack
Fleet
- Multi-node management via authenticated HTTP and WebSocket proxy
- Fleet view with grid and topology layouts
- Fleet snapshots of compose and env across the fleet
- Fleet Federation: cordon nodes and pin Blueprints to specific hosts
- Fleet Actions: bulk label operations, fleet-wide stop-by-label, and fleet-wide prune
- Fleet Dossier: export the whole fleet as a single browsable Markdown archive
- Fleet Secrets: author environment-variable bundles once, push them to labeled nodes' stacks, with an audit trail of every change
- Fleet Sync: push scan policies, CVE suppressions, and misconfig acknowledgements from a control instance to its replicas
- Docker Label Audit across every node, for labels that drive external automation
- Remote updates: pull the latest image and recreate any node in the fleet from the Fleet view, no SSH session required
- Node labels and grouping
- Pilot Agent for nodes behind NAT or strict firewalls
- Node compatibility checks before deploying
Automation
- Auto-heal policies for failed containers
- Auto-update policies for image rollouts
- Scheduled operations on cron
- Webhooks on stack lifecycle events
- Blueprints: declarative fleet templates with drift detection
Security
- SSO: custom OIDC and presets for Google, GitHub, and Okta
- Two-factor authentication with TOTP and backup codes
- RBAC with five built-in roles and stack or node scoped assignments
- Security overview with a chart-led scan summary, sortable images, and searchable scan history
- Vulnerability scanning via Trivy, with on-demand node-wide scans, VEX-based suppression, SARIF export, and SBOM upload
- Compose network inspector with an exposure-intent guard for unintended published ports
- Node-wide network inventory, topology, and exposure findings across every stack on a node
- Scan policies that set severity thresholds and can block a deploy
- Private registries for Docker Hub, GHCR, and custom registries, plus deploy enforcement for non-compliant images
- API tokens for automation
Operations
- Off-site stack archives via custom S3-compatible storage
- Notification routing to Slack, Discord, and any generic webhook
- Global search across pages, nodes, and every stack in the fleet
- Resources view for images, volumes, and networks with scoped prune actions
- Host console: an interactive terminal on the host OS in the browser, no SSH session required
Before you install
Sencho talks to Docker through the host's /var/run/docker.sock. Mounting this socket grants Sencho the same privilege as sudo docker on the host. This is the same model used by Portainer, Dockge, Komodo, and other Compose dashboards. If your threat model requires stricter isolation, see running with a non-root container user and front Sencho with a reverse proxy that enforces authentication.
Quick start
Sencho runs in a single container.
services:
sencho:
image: saelix/sencho:latest
container_name: sencho
restart: unless-stopped
ports:
- "1852:1852"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./data:/app/data
# 1:1 Compose Path Rule: the host path MUST match the container path
- /opt/docker:/opt/docker
environment:
- COMPOSE_DIR=/opt/docker
- DATA_DIR=/app/data
docker compose up -d
Open http://your-server:1852 and create your admin account.
Always front Sencho with a TLS-terminating reverse proxy in production. See the self-hosting guide for hardening, environment variables, and reverse-proxy examples.
Run with docker run instead
docker run -d --name sencho \
-p 1852:1852 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v sencho_data:/app/data \
# 1:1 Compose Path Rule: the host path MUST match the container path
-v /opt/docker:/opt/docker \
-e COMPOSE_DIR=/opt/docker \
saelix/sencho:latest
For the full walkthrough, see the quickstart guide.
Adding remote nodes
To manage a second machine, install Sencho on it the same way, then add it from the primary dashboard with its URL and a long-lived API token. The primary proxies authenticated HTTP and WebSocket requests to the remote instance. The remote node does not run SSH for Sencho, does not expose its Docker socket on the network, and does not run a separate agent process. The local Sencho on each node manages its own Docker through the standard socket mount described in Quick start. Nodes behind NAT or strict firewalls can opt into the Pilot Agent for outbound-only connectivity.
See the multi-node guide for the full token-bearer flow.
Screenshots
 |
 |
 |
 |
 |
 |
 |
 |
Same screens in OLED
 |
 |
 |
 |
 |
 |
 |
 |
Same screens in Light
 |
 |
 |
 |
 |
 |
 |
 |
Telemetry and data handling
Sencho does not emit telemetry, analytics, or crash reports, and makes no outbound calls to Sencho-controlled endpoints. Stack metadata, container inventory, and user activity never leave your instance.
Admiral
Admiral is Studio Saelix's paid business assurance plan on top of everything in Community: Hardened Build, Recovery Vault (managed off-site snapshots), priority support, and governance depth (LDAP / Active Directory, full audit log export and anomaly detection, and related organizational controls). Built-in RBAC (five roles and scoped assignments) is included on Community. AWS ECR registry credentials currently require Admiral as well; that access rule is temporary availability, not the reason Admiral exists. See sencho.io/pricing for current plan details.
Documentation, community, and license
- Documentation: docs.sencho.io
- Blog: sencho.io/blog
- Known limitations: KNOWN_LIMITATIONS.md
- If something breaks: the Recovery guide covers getting back to a working state when Sencho, a deploy, sign-in, Docker, or a node fails.
- Community: GitHub Discussions
- Contributing: CONTRIBUTING.md
- Security: SECURITY.md. Do not open public issues for security vulnerabilities.
- License: GNU Affero General Public License v3.0 (
AGPL-3.0-only). Copyright (c) 2026 Studio Saelix. Sencho is free software; see LICENSE and Licensing for terms. Studio Saelix trademarks are described in TRADEMARKS.md.