- WireGuard mesh networking
- unregistry - direct image push to servers without a registry
Give it a listen on any podcast platform and let me know what you think! 🎧👇
gopodcast.dev/episodes/078...
go podcast()
🎙️ I went on go podcast() this week to talk about why I’m building Uncloud - Docker Compose for production, bridging the gap between Docker and Kubernetes.
We covered:
- why most projects don't need k8s and what alternatives we have
- a hybrid setup mixing cloud VMs and on-prem
1/2
🎙️go podcast ep. 78 is out, we received Pasha Sviderski, the creator of Uncloud a tool that bridge the gap between Docker and K8, it's helping with infra / deployment on self-hosted servers and of course, built with Go. gopodcast.dev/episodes/078...
Thank you for sponsoring my work on Uncloud! 🙌
Hey, thank you so much ❤️
GH is fine, maybe I need to create open collective as well to not depend oh gh? Will this work better for you?
Would love to learn more about what you’re buildin
Lol I wish I knew about that earlier. Would definitely call it unc and added ‘unc status’ command. Might be worth adding an alias
Haha but why?
Looks very promising and reminds me somewhat of taubyte.com
Following to see where it goes, tho so far it kinda "feels" nicer than coolify
Finally sent my first newsletter: A year of building Uncloud
(a simpler Kubernetes alternative for small teams and solo developers)
What happened, where we are now, and what’s coming in 2026
open.substack.com/pub/psviders...
Look ma’ I’m on the orange site
As far as I know @luislavena.info uses it with tailscale together, including tailscale ssh for provisioning and access without ssh keys
Thanks for the public appreciation! ❤️
Could you please tell me more about what you liked in uncloud compared to coolify? Happy to chat in DM too if that’s easier.
Thank you Niklaas for trying it out and nice words! Please let me know if you have any feedback 🙏
Thank you for following my journey and supporting me.
Thank you for following my journey and supporting me. Will keep sharing more technical and non-technical insights along the way. You are awesome! ❤️
I know that I need to code less and write more (docs, guides, blogs, etc.) but writing is perhaps my least developed skill so I procrastinate a lot. You have no idea what it takes for me to write even this post but I keep practicing and making little progress.
I hope you can help me figure out what value-added product we can build on top. Whether it’s a PaaS everyone else is building or something more niche. I doubt there is a good business model for it as-is. Feel free to share your ideas.
I do explore options for how to make the project development sustainable. This is truly my dream job and I will try hard to make it profitable.
I’m working on uncloud full-time now and have enough savings to get it to a point where I’m happy to fully shut down my K8s clusters and manage everything with uncloud. The scope turned out to be huge but I don’t care anymore, I want a simpler Kube alternative to exist.
Since June I started connecting with such nice people who just want to say hi or help with their advice or contributions and encourage me to keep going. I hope we’re on the right track as a few supporters are voting with their wallets for a simpler deployment solution.
The turning point was a successful launch of unregistry on HN in June. Before that, almost a year of grinding with almost no reward. But damn it was worth it.
First income from my open source work!
Someone actually paid me to bring back 2015 Docker vibes. Some reflections 👇
It took me more than a year to reach this point but I had no idea how much fun it would be. But only after a certain point, when I got a bit of attention.
I've been blown away by Uncloud and unregistry from @psviderski.bsky.social, to the point that I'm actually enjoying deploy again!
Build and deploy under seconds. No need for external container registry, all streamlined.
Previous deploy metrics: k8s: 5min!. Swarm: 30s, Uncloud: < 5s. 👏🚀
Another syscall is sendfile() used by io.Copy for file → socket transfers only. It directly copies data from page cache to socket in kernel space, reducing CPU usage and cache polution.
splice() moves data between file descriptors without copying between kernel and user space. This allows creating quite performant proxies with little effort.
io.Copy in Go is actually zero-copy on Linux.
When you io.Copy between TCP connections it automatically detects the WriterTo/ReaderFrom interfaces and uses splice() syscall under the hood.
- builds new image locally (or in remote builder) from compose.yaml
- pushes image directly to remote machine(s) without a registry
- rolls out containers without downtime
Most of the building blocks are already in place so need to glue everything together. Should be fun
I’m back to the drawing board. Designing the main deploy flow uncloud was essentially created for.
Integrating unregistry to make a kick-ass DX.
Just one ‘uc deploy’ command:
Love developers spreading kindness on GitHub and Discord. It doesn't take much but makes a total difference.
A special shout out to @luislavena.info who just had a baby but still champions sleep-deprived testing and early adoption. This is amazing!
Be nice and attract more love! ❤️
