Pasha Sviderski

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

A year of building Uncloud And what's coming in 2026

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.

GitHub - psviderski/uncloud: A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨ A lightweight tool for deploying and managing containerised applications across a network of Docker hosts. Bridging the gap between Docker and Kubernetes ✨ - psviderski/uncloud

github.com/psviderski/u... omg this is what i wanted out of coolify

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! ❤️

Ingress & HTTPS | Uncloud Uncloud uses Caddy as its reverse proxy to handle incoming traffic, provide automatic HTTPS

uncloud.run/docs/concept...
github.com/psviderski/u...

Uncloud v0.12 brings full Caddyfile support to your Compose deployments

Configure reverse proxy per service:
- custom routing & redirects
- auth & headers
- dynamic upstreams with {{upstreams 8080}}
- inline or load from file with x-caddy

Docs and release notes in 🧵

How to connect Docker containers across multiple hosts with WireGuard | Uncloud Learn how to configure a WireGuard overlay network that lets Docker containers securely communicate across multiple hosts. No exposed ports needed.

Ever wanted your Docker containers running on different hosts to securely talk to each other without exposing ports?

Here's my guide on using pure WireGuard to make this work across clouds and even behind NAT +a sneak peek at Uncloud, the tool I built to automate it all

uncloud.run/blog/connect...

It works. But at first I tried to convert my tailwind-styled page into a regular docusaurus page and it was a nightmare to fight with react and all the automatic docusaurus injections into the page. Don’t try this at home kids

4. After creating a docusaurus build, overwrite the generated /index.html with my landing page. I couldn’t put it into docusaurus static because it caused conflict with the generated index.html 🙈

1. Need to create an empty docusaurus page for root path / (pages/index.js)
2. Set navbar.logo.href to fqdn
3. Swizzle the DocBreadcrumbs component and overwrite baseUrl (/ → /docs) so that home leads to the root of docs instead of the empty page

Managed to deploy docusaurus-generated docs and a landing page (static html with tailwind css) as one bundle of static html such that:

/ → standalone landing page html
/docs and /blog → html generated from markdown

Finding the right incantation was non-trivial 👇