⚠️ THIS POST IS GENERATED WITH LLMs: This post is newly generated a few times a week based on trending articles from hacker news. It takes the tone of my writing style, takes the topic from Hacker News - throws in some LLM magic and generates this post. Please be aware I don’t read what gets generated here - it means I may agree, I may not - its a crap shoot - its not meant to be an opinion piece but merely an experiment with the services from OpenRouter - last updated Monday 07 September 2026
Well, here we are again. I’ve been quietly tinkering with this idea for a while now, and I finally felt ready to put it out into the open. If you’ve ever found yourself staring at a sea of subscription dashboards, tracking banners, and walled gardens, you’re probably right where I’ve been for the last couple of years: quietly frustrated, but figuring out how to fix it.
I’ve always believed that the best systems aren’t the most complex ones—they’re the ones that quietly eliminate friction. Lately, though, I’ve been noticing how our relationship with software has completely flipped. We used to “own” what we used. You downloaded it, installed it, ran it on your own machine, and if something broke, you fixed it or swapped it out. Then the cloud rolled in, and suddenly everything feels like renting a room where the landlord keeps changing the locks, injecting ads, and selling your habits to the highest bidder. The software itself is easier to build than ever, yet we’ve somehow ended up in a place where using it feels like managing a portfolio of corporate incentives rather than actually living our lives.
That disconnect is what eventually pushed me to take a swing at it myself. I wanted to build something that felt less like configuring a Linux server at 2am, and more like picking up a smartphone. You know the feeling: you buy the device, it just works, you find apps you like, and they all play nicely together without you having to babysit them. I kept coming back to that analogy. What if your personal cloud worked the same way? No more treating every self-hosted app like an isolated island with its own login, its own config file, and its own security liability. Just a clean dashboard, a unified identity layer, and apps that actually talk to each other when you want them to.
At its core, the project is pretty straightforward. It’s just an Ubuntu machine running a lightweight web server that routes traffic to containerized applications. But I’ve spent a lot of time thinking about how to make those containers actually feel like a platform rather than a hobbyist workshop. Everything runs in rootless, hardened sandboxes, so one misbehaving app doesn’t bring down the whole house. If you’re logged into the main instance, you’re automatically logged into everything else. Apps can optionally request permission to share specific data or capabilities, much like how iOS or Android handle sensor access or health data. It’s all designed to be open-source, zero-telemetry, and as magic-free as possible. The goal isn’t to build a walled garden; it’s to build a front yard that anyone can walk into.
Now, I won’t pretend it’s plug-and-play perfection. There’s definitely a chicken-and-egg problem going on right now. Without an accessible way to run open-source web apps, the audience stays small. Without a small audience, developers don’t rush to build apps for it. It’s a classic iteration loop. So for now, the curated catalog is intentionally small—we’re only adding things that actually deliver a clean, stable experience. Early users will probably need a bit of technical comfort (or a good coding agent) to find or adapt what they want to run, but it’s getting smoother every week. I’ve been slowly migrating my own digital life into it, and honestly, it’s felt like finally exhaling after holding my breath for years.
We’ve also set up a managed version alongside the self-hosted path. I think having that option is important, not just for accessibility, but for sustainability. Open-source work thrives when the people building it can actually eat, and a straightforward managed offering lets us keep the self-hosted code exactly the same while funding the ongoing polish. It’s all about pragmatic balance—lean principles applied to community-driven software.
Honestly, the best part has been the conversations it’s sparked. I’ve set this whole thing up because I want to share what I’m learning, not because I think I’ve solved everything. Every time a friend, a family member, or someone in a different industry actually uses it and says, “Oh, this is what I’ve been looking for,” it reinforces why I keep tinkering. Growth isn’t always linear, and neither is building tools for people. But when you strip away the noise and focus on what actually makes life easier, the path usually reveals itself.
If you’ve been meaning to dip your toes into self-hosting but didn’t know where to start, I’d love for you to give it a look. Try the managed instance, grab a free VPS, or dig into the code on GitHub. Drop me a line on Matrix if you hit a snag, have an idea, or just want to swap stories about the apps you run at home. I read every message, and I genuinely appreciate the time you take to share your thoughts.
Here’s to building things that actually serve us, not the other way around. Let’s keep iterating, keep sharing, and keep making the digital world feel a little more like our own. 🌮
