
I write JS, sometimes Rust & Go, I also build stuff at @techulus
Sydney, Australia
Joined May 2009
- Tweets5.3K
- Following203
- Followers526
- Likes2.5K
So why am I building a PaaS (platform as a service)?
Short answer: It's because I love @Railway and I want the same experience with my own servers.
Long answer: I self-host several services on my home lab servers. This was a very manual task with minimal automation; I pulled code into servers, set up Docker Compose files, Tailscale, Traefik, DNS, pretty much everything was manual. On the other hand, when I deploy my side projects to services like Railway or @vercel, everything is just a few clicks away and feels magical. I want to bring this seamless experience to my infrastructure.
In case you're wondering, yes, I've tried @coolifyio / @getdokploy / @dokku / @portainerio and some other self-hosted PaaS solutions, but they didn't work well for me. There were some flaws that I couldn't fix (private networking, load balancing workloads across servers, ease of swapping servers, self-healing workloads etc.).
So I started to rethink how I could build the perfect self-hosted PaaS. FYI, it's heavily inspired by platforms like Railway, Fly.io, etc. My research was mostly reading their engineering blogs and chatting with LLMs.
Here's how my solution differs:
> Coolify/Dokploy = centralised control which is SSH-driven, push-based orchestration, not multiple server native.
> What I'm building = a distributed peer-to-peer container fabric: agent-driven, pull-based orchestration, private-first networking, disposable workloads, proxy nodes to handle ingress, and finally, a touch of magic.
5
5
467
THE ANNOUNCEMENT: We’re going to make the prophecy of The Year of Linux on the Desktop come true. All the pieces are now in place. Time to go all in! omarchy.org/news/2026/08/oma…
Postgres rewrite by Turso team, LFG 🐐
I am excited to announce that we are officially writing a new version of Postgres. In Rust - and creating the LLVM of databases in the process.
In the span of a year, we have rewritten SQLite. Keeping the compatibility, increasing its feature set. MVCC, Types, (Live) Materialized Views, among other things. In the process of doing that, we have realized: At the end of the day, what makes SQLite special is that it compiles SQL to a database-specific bytecode. So why can't we compile *Postgres* to the same bytecode?
Turns out we can. I ran an experiment called pgmicro as a way to prove this hypothesis, and it works very well. It is time to make this official, and put the weight of Turso behind it. We shall give the world a modern take on Postgres. Wire compatible, but built on a new architecture.
We have already heard of others wanting to extend this. MySQL? Redis? the sky is the limit. What can we do if we do for databases what LLVM did for compilers? To prove how powerful the SQLite bytecode is, we are actually running DOOM compiled to the unmodified SQLite instruction set. And because Turso runs natively in the browser, you can play the game in your browser. With the database executing it.
Read the full story below! 👇
1
100
$230 🫠
Meet kbd-1.0-codex-micro, built with @work_louder.
Map the buttons and joystick to your workflow, and keep your pinned chats in view.
Get yours before stock returns 410.
1
90
Last few days having been very fun and tons of learning;
I added serverless (aka sleeping) containers capability to my OSS deployment platform, the containers would be stopped and started based on incoming requests.
Unfortunately the wake time was terrible, it would ~9 seconds for the TCP request to connect even though containers would start in under 300ms.
After 3 days of research, several long debugging sessions and chats with Fable / GPT 5.5, I've got it under 400ms now.
2
2
96
This is the magic PR with the fix
github.com/techulus/cloud/pu…
12












