Back to browse
GitHub Repository
2 starsTypeScript

Sencho: a multi-node Docker-compose manager

by ansocode·Jun 9, 2026·1 point·0 comments

AI Analysis

●●SolidSolve My ProblemShip It

Portainer alternative keeping compose files on disk with outbound-only agent connectivity.

Strengths
  • Outbound-only Pilot Agent manages NAT hosts without opening inbound firewall ports.
  • Compose files remain on host filesystem instead of abstracting into a database.
  • Single container install handles RBAC, SSO, and image scanning out of the box.
Weaknesses
  • Public beta status means critical infrastructure deployment requires careful testing first.
  • Crowded category competes directly with established tools like Portainer and Coolify.
Target Audience

Homelab operators, small DevOps teams, platform engineers

Similar To

Portainer · Dockge · Coolify

Post Description

Hi HN, I am the creator of Sencho (https://github.com/Studio-Saelix/sencho). It's a self-hosted docker-compose control plane for managing one server or a small fleet of hosts from a single interface.

Here's some the core architectural decision i built it around:

- compose files and .env files stay on the host filesystem. It operates on them but does not replace them as the source of truth. - each node uses its local Docker socket. There's no exposing Docker's TCP socket over the network. - remote hosts can be connected directly via a distributed API mode or through an outbound-only Pilot Agent for hosts behind NAT or stricter firewalls. - multi-node management is not an afterthought.

It supports stack deployment and updates, Git-backed stacks, webhooks, rollback, logs, container and resource management, image scanning, backups, scheduled operations, fleet views, RBAC, SSO, and other operational tooling that I found myself wanting while managing compose environments.

This is 100% docker-compose to make fleet management feels like kubernetes without being the complexity of kubernetes.

Similar Projects