←back to thread

152 points rgun | 1 comments | | HN request time: 0s | source
Show context
psviderski ◴[] No.46144570[source]
Hey, creator here. Thanks for sharing this!

Uncloud[0] is a container orchestrator without a control plane. Think multi-machine Docker Compose with automatic WireGuard mesh, service discovery, and HTTPS via Caddy. Each machine just keeps a p2p-synced copy of cluster state (using Fly.io's Corrosion), so there's no quorum to maintain.

I’m building Uncloud after years of managing Kubernetes in small envs and at a unicorn. I keep seeing teams reach for K8s when they really just need to run a bunch of containers across a few machines with decent networking, rollouts, and HTTPS. The operational overhead of k8s is brutal for what they actually need.

A few things that make it unique:

- uses the familiar Docker Compose spec, no new DSL to learn

- builds and pushes your Docker images directly to your machines without an external registry (via my other project unregistry [1])

- imperative CLI (like Docker) rather than declarative reconciliation. Easier mental model and debugging

- works across cloud VMs, bare metal, even a Raspberry Pi at home behind NAT (all connected together)

- minimal resource footprint (<150MB ram)

[0]: https://github.com/psviderski/uncloud

[1]: https://github.com/psviderski/unregistry

replies(11): >>46144726 #>>46144768 #>>46144784 #>>46144846 #>>46144978 #>>46145074 #>>46145335 #>>46145652 #>>46145808 #>>46146155 #>>46146244 #
olegp ◴[] No.46144726[source]
How's this similar to and different from Kamal? https://kamal-deploy.org/
replies(1): >>46144913 #
psviderski ◴[] No.46144913[source]
I took some inspiration from Kamal, e.g. the imperative model but kamal is more a deployment tool.

In addition to deployments, uncloud handles clustering - connects machines and containers together. Service containers can discover other services via internal DNS and communicate directly over the secure overlay network without opening any ports on the hosts.

As far as I know kamal doesn’t provide an easy way for services to communicate across machines.

Services can also be scaled to multiple replicas across machines.

replies(2): >>46144944 #>>46146343 #
olegp ◴[] No.46144944[source]
Thanks! I noticed afterwards that you mention Kamal in your readme, but you may want to add a comparison section that you link to where you compare your solution to others.

Are you working on this full time and if so, how are you funding it? Are you looking to monetize this somehow?

replies(1): >>46145037 #
psviderski ◴[] No.46145037[source]
Thank you for the suggestion!

I’m working full time on this, yes. Funding from my savings at the moment and don’t have plans for any external funding or VC.

For monetisation, considering building a self-hosted and managed (SaaS) webUI for managing remote clusters and apps on them with value-added PaaS-like features.

replies(1): >>46145056 #
olegp ◴[] No.46145056{3}[source]
That sounds interesting, maybe I could help on the business side of things somehow. I'll email you my calendar link.
replies(1): >>46145731 #
1. psviderski ◴[] No.46145731{4}[source]
Awesome, will reach out!