HN Showcase
Back to browse
GitHub Repository
1 starsTypeScript

Sencho – a self hosted Docker Compose UI with multi-node fleet support

by ansocode·Jun 5, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemBig Brain

Outbound-only Pilot Agent beats Portainer for NAT traversal without exposing Docker socket.

Strengths
  • •Outbound-only Pilot Agent enables NAT traversal without opening inbound ports on remote nodes.
  • •Compose files remain on disk as source of truth instead of being captured in a database.
  • •No Kubernetes complexity for teams managing small fleets of Docker Compose services.
Weaknesses
  • •BSL-1.1 license restricts some commercial use cases compared to fully open alternatives.
  • •Portainer already dominates this space with 20K+ stars and enterprise features.
Target Audience

Homelab operators and small DevOps teams managing Docker Compose across servers

Similar To

Portainer · Dockge · CapRover

Post Description

Hey HN I’ve been managing docker compose apps on multiple remote servers over the years and I got tired of using multiple tools for simple tasks.

I wasn’t happy with the current available options so I built Sencho. It’s a self-hosted Docker Compose control plane for people managing one machine or a small fleet, without moving to Kubernetes and without exposing the Docker socket over the network.

Connect your remote nodes either by direct authenticated HTTP/WebSocket proxying, or through the outbound-only Pilot Agent. There’s no restriction on the number of nodes you can connect.

Manage the entire compose lifecycle from a central place and most importantly Your compose file are not “captured” and stay on disk as source of truth.

GitHub: https://github.com/Studio-Saelix/sencho

Docs: https://docs.sencho.io

Similar Projects