Scatter a few cheap VPS boxes, a home server, and one bare metal machine across three different providers, and Uncloud still treats them as a single place to run your applications. You describe services in ordinary Docker Compose files, deploy them with the uc command line tool, and publish any container port as a public HTTPS endpoint in a single command. Every machine joins an encrypted WireGuard mesh with its own container IP addresses, so services on different continents reach each other directly without VPN configuration or exposed ports. A built-in DNS server resolves service names to container IPs, and the integrated Caddy reverse proxy provisions and renews Let's Encrypt certificates automatically, sharing them across the cluster. Rolling updates replace containers with zero downtime, persistent Docker volumes keep stateful services safe, and the Unregistry integration pushes image layers straight to your machines when no registry is available. There is no control plane to babysit: each machine keeps a synchronised copy of the cluster state, and SSH access to any single node is enough to manage the whole fleet. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One server, treated properly: Nanocl runs your containers and full virtual machines from a single declarative Statefile, reconciling what is running against what the file says, so a lone host gets cluster discipline without cluster ceremony. Containers group into Cargoes with replica counts, ordered init containers, and health-aware restarts; finite jobs run to completion and stop. When a workload needs a real kernel or a custom disk image, it boots as a QEMU virtual machine beside the containers instead of forcing a second platform. Publishing is built in: the proxy controller terminates TLS and routes HTTP and TCP traffic, and the DNS controller keeps service names resolving while workloads come and go. Secrets for registries, certificates, and environment variables attach where they are used, never inside the file itself. The daily loop is a CLI and an API: list processes, follow logs, exec into a container, watch events, and back up the entire deployment state before you change it. Namespaces keep projects apart on the same host, and Statefile arguments, templates, and sub-states carry one definition from staging to production. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT or Apache-2.0 licensed.

With over 32,000 GitHub stars and a decade of production use since 2013, Dokku is the original self-hosted Heroku alternative — a Docker-powered PaaS that turns any single Ubuntu server into a full application platform with a simple git push. Deploy applications written in Node.js, Python, Ruby, Go, Java, PHP, Scala, and Clojure using Heroku-compatible buildpacks, Cloud Native Buildpacks via pack-cli, standard Dockerfiles, or pre-built Docker images, with automatic language and framework detection handling the rest. Every deployment runs through zero-downtime checks that health-test new containers before routing traffic via the built-in Nginx reverse proxy, which handles virtual host configuration, WebSocket proxying, and HTTP/2 support automatically. The official plugin ecosystem provides managed datastores including PostgreSQL, MySQL, MariaDB, MongoDB, Redis, RabbitMQ, and Elasticsearch, each provisioned with a single CLI command and linked to apps via environment variables. Automated TLS certificates arrive through the Let's Encrypt plugin with auto-renewal, while persistent storage volumes, cron job scheduling, user ACL management, and process scaling round out the platform capabilities. The entire system is CLI-driven — no web dashboard — keeping resource overhead minimal enough to run multiple applications on a $5/month VPS. Dokku also supports Lambda function builds, custom builder plugins, and app.json-based healthcheck configuration for advanced deployment workflows. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Stateful serverless actors that run indefinitely, sleep when idle, and persist state across restarts without external database round trips. Rivet provides a vendor-neutral alternative to Cloudflare Durable Objects, delivering long-running processes with co-located in-memory state and per-actor SQLite databases on any infrastructure you choose. The Rust engine comprises four packages: Pegboard for actor orchestration, Gasoline for durable execution, Guard for traffic routing via Envoy, and Epoxy implementing multi-region KV storage through EPaxos consensus. Each actor maintains instant-access in-memory state plus a dedicated SQLite database for relational queries, backed by RocksDB on single nodes or PostgreSQL with NATS pub/sub for multi-node clusters. RivetKit SDKs in TypeScript, Rust, and Python support built-in WebSocket connections, task queues, scheduling, and CRDT-based real-time collaboration. The v2.3 rewrite moved the core runtime from JavaScript to native Rust via WebAssembly, eliminating main-thread blocking across Node.js, Bun, Deno, and Cloudflare Workers. A built-in dashboard provides actor inspection with real-time Prometheus metrics. Deploys as a single Docker container on port 6420 with optional PostgreSQL for persistence. Available on RepoCloud with a dedicated VPS under the Apache 2.0 license.

For self-hosters who want Git-driven container deployments without surrendering control of their existing reverse proxy or host networking, Dockerizalo provides a lightweight web platform that clones repositories, builds Docker images, and manages running services from a single dashboard. Point an application entry at any Git-compatible repository or public container registry image, configure custom build paths, and let the platform build and launch the container directly on your host Docker engine. A built-in template library accelerates database provisioning with pre-configured variables, networks, and persistent storage mounts. Through the web interface, operators manage environment secrets, bind-mounted volumes, custom Docker labels, and published TCP or UDP ports while coexisting peacefully alongside Caddy, Nginx, or Traefik setups. Per-application HTTP webhook triggers let teams automate continuous delivery from GitHub, GitLab, Gitea, or custom CI pipelines on every push event. Real-time paginated build and runtime container log streams prevent memory exhaustion on chatty APIs while keeping every deployment event visible. Configurable image retention policies automatically prune older tags and remove dangling images after each rollout so disk space stays clean. Multi-user account management allows homelab administrators to invite collaborators to the dashboard without sharing a single root credential. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.