psviderski / uncloud
A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing psviderski/uncloud in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Repository Overview (README excerpt)
Crawler view▸ Deploy and scale containerised apps across servers without Swarm or Kubernetes overhead ◂ Uncloud is a lightweight clustering and container orchestration tool that lets you deploy and manage web apps across cloud VMs and bare metal with minimised cluster management overhead. It creates a secure WireGuard mesh network between your Docker hosts and provides automatic service discovery, load balancing, ingress with HTTPS, and simple CLI commands to manage your apps. Unlike traditional orchestrators, there's no central control plane and quorum to maintain. Each machine maintains a synchronised copy of the cluster state through peer-to-peer communication, keeping cluster operations functional even if some machines go offline. Uncloud is the solution for developers who want the flexibility of self-hosted infrastructure without the operational complexity of Kubernetes. ✨ Features • **Deploy anywhere**: Combine cloud VMs, dedicated servers, and bare metal into a unified computing environment, regardless of location or provider. • **Docker Compose**: Familiar Docker Compose format for defining services and volumes. No need to learn a new bespoke DSL. • **Zero-downtime deployments**: Rolling updates without service interruption. Automatic rollback on failure is coming soon. • **Unregistry integration**: Build and push your Docker images directly to your machines without an external registry. It will transfer only the missing layers, making it fast and efficient. • **Service discovery**: Built-in DNS server resolves service names to container IPs. • **Persistent storage**: Run stateful services with Docker volumes managed across machines. • **Zero-config private network**: Automatic WireGuard mesh with peer discovery and NAT traversal. Containers get unique IPs for direct cross-machine communication. • **No control plane**: Fully decentralised design eliminates single points of failure and reduces operational overhead. • **Imperative over declarative**: Favoring imperative operations over state reconciliation simplifies both the mental model and troubleshooting. • **Managed DNS**: Automatic DNS records for services with public access via managed Uncloud DNS service. • **Automatic HTTPS**: Built-in Caddy reverse proxy handles TLS certificate provisioning and renewal using Let's Encrypt. • **Docker-like CLI**: Familiar commands for managing both infrastructure and applications. • **Remote management**: Control your entire infrastructure through SSH access to any single machine in the cluster. 🎬 Quick demo The screenshot below demonstrates how I use Uncloud to deploy https://uncloud.run website to 2 remote machines from the file on my local machine. It exposes the container port as HTTPS on the domain , served by the Caddy reverse proxy on the remote machines. All managed by Uncloud. Here is a more advanced use case. Deploy a highly available web app with automatic HTTPS across multiple regions and on-premises in just a couple minutes. > **📚 Want more examples?** Check out the **uncloud-recipes** > repository for community recipes and templates for deploying popular services on Uncloud. 💫 Why Uncloud? Modern cloud platforms like Heroku and Render offer amazing developer experiences but at a premium price. Traditional container orchestrators like Kubernetes provide power and flexibility but require significant operational expertise. I believe there's a sweet spot in between — a pragmatic solution for the majority of us who aren't running at Google scale. You should be able to: • **Own your infrastructure and data**: Whether driven by costs, compliance, or flexibility, run applications on any combination of cloud VMs and personal hardware while controlling your data and maintaining the cloud-like experience you love. • **Stay simple as you grow**: Start with a single machine and add more whenever you need without changing your workflow. No worrying about highly-available control planes or complex YAML configurations. • **Build with proven primitives**: Get production-grade networking, deployment primitives, service discovery, load balancing, and ingress with HTTPS out of the box without becoming a distributed systems expert. • **Support sustainable computing** 🌿: Minimise system overhead to maximise resources available for your applications. Uncloud's goal is to make deployment and management of containerised applications feel as seamless as using a cloud platform, whether you're running on a $5 VPS, a spare Mac mini, or a rack of bare metal servers. 🚀 Quick start • Install Uncloud CLI: See Installation for more options. • Initialise your first machine: • Deploy your app from a Docker image and publish its container port 8000 as HTTPS using domain: • Create a DNS A record in your DNS provider (Cloudflare, Namecheap, etc.) that points to your server's IP address. Allow a few minutes for DNS propagation. That's it! Your app is now running and accessible at https://app.example.com ✨ • Clean up when you're done: If you want to fully uninstall Uncloud on a machine, run: View the Documentation for more information. ⚙️ How it works Check out the design document to understand Uncloud's design philosophy and goals. Here is a diagram of an Uncloud multi-provider cluster of 3 machines: Peek under the hood to see what happens when you run certain commands. **When you initialise a new cluster on a machine:** • The CLI SSHs into the machine and installs Docker, the machine daemon and corrosion service, managed by systemd. • Generates a unique WireGuard key pair, allocates a dedicated subnet for the machine and its containers, and configures accordingly. All subsequent communication happens with through its gRPC API over SSH. • Configures and starts , a CRDT-based distributed SQLite database to share cluster state between machines. • Creates a Docker bridge network connected to the WireGuard interface. • This machine becomes an entry point for the newly created cluster…