Yesterday a project called Cloud in a Bottle hit the Hacker News front page with over 500 points and 250+ comments. The pitch: self-hosting should feel like using a smartphone that serves web apps, not a sysadmin side job. One login for everything, apps sandboxed in rootless containers, a curated app store.
I run my own infrastructure on a VPS, including a growing stack of AI agent tooling, and I have spent way too many evenings wiring up reverse proxies and SSL certificates by hand. So this launch grabbed me. But I have also been burned by shiny new self-hosting platforms before, and the obvious incumbent here is Coolify, which claims more than 55,000 GitHub stars and a stable v4 release.
Full disclosure up front: I have run Coolify-adjacent tooling and my own Docker deployments in production, but I have not yet run Cloud in a Bottle myself. It launched yesterday. This comparison is based on the launch post, the project docs, Coolify's documentation and pricing, and a long read through the Hacker News comment thread. Where something is my opinion rather than a fact from the source, I say so.
Here is how they actually compare.
The core idea is different, and that matters more than the feature list
Coolify is a deployment platform. It is the open-source answer to Heroku, Vercel, and Railway, running on servers you own. You get git-push deployments, automatic Let's Encrypt SSL, a visual dashboard, and a catalog of 280+ one-click services: PostgreSQL, MySQL, Redis, n8n, Grafana, WordPress, Ghost, even Ollama for local AI inference. Reverse proxying runs through Traefik or Caddy. It is built for developers who want to deploy applications without stitching together nginx config files at midnight.
Cloud in a Bottle is a personal cloud. At its core it is, in the project's own words, "just an Ubuntu machine with a web server that hosts a dashboard and routes HTTP(s) requests to containerized apps." Apps run as rootless, hardened containers. But the platform layer is where it diverges: if you are logged into your instance, you are automatically logged into all your apps. No separate accounts per app. There is also a permissioned interface for apps to share data and capabilities with each other, which the creator explicitly models on the APIs that Android and iOS give mobile apps: notifications, sensor access, data sharing.
That is the real philosophical split. Coolify treats every app as its own deployment with its own domain, its own login, its own everything. Cloud in a Bottle treats your server like a phone and the apps like apps on that phone: integrated, shared-identity, permission-gated.
Unified auth: killer feature or dealbreaker?
This was the most contested point in the Hacker News thread, and both sides have a case.
The case for unified auth. One commenter put it well: "The unified auth + inter-app permissions are the real differentiator vs Coolify/CapRover-style container hosts." Anyone who has self-hosted more than three apps knows the pain. Your photo manager has a login. Your note app has a login. Your password manager has a login. You either maintain three credential sets or wire up Authentik or Authelia yourself, which is its own weekend project. Cloud in a Bottle makes that problem disappear by design.
The case against. Another commenter pushed back directly on the project's dismissal of Coolify: "I want each application to be a separate login, so I can have one pointed to a different subdomain or domain not all in one login and location." If you host things for other people, a client, a family member, a small team, shared identity becomes a liability. One compromised session touches everything.
My take: if the Bottle is genuinely for you and your family, unified auth is a genuine upgrade. If you are hosting anything with multiple tenants or public exposure, Coolify's per-app isolation is the safer default.
Security models: both containerize, but the baselines differ
Cloud in a Bottle runs rootless, hardened containers and markets this as central to the design. Its own docs page on security is the reference here, and commenters who dug in noted the containers are rootless but found no mention of network-level isolation like VLAN segmentation between apps. That means one compromised app might still be able to reach its neighbors over the network. Worth watching as the project matures.
Coolify gives you Docker containers with whatever isolation Docker provides, but the platform itself does not enforce a hardened sandbox per app. You bring your own discipline. The flip side is flexibility: Coolify will deploy essentially anything that builds, across Node.js, Python, Go, Ruby, PHP, or raw Docker Compose.
Compare both with the cautionary tale in this space. The Cloud in a Bottle launch post itself calls out YunoHost, a beloved predecessor, because "apps run directly on the host, no sandboxing. one insecure app compromises the entire server." It also points at Sandstorm, which made almost exactly the same argument in 2014, as "long abandoned." The graveyard of this category is real. Both tools sandboxing by default is the lesson learned from it.
Cost: both are nearly free, but the shapes differ
Coolify self-hosted is free forever under the Apache 2.0 license, with no feature limits, no user caps, and unlimited servers and team members. Your only cost is the VPS. The maintainers also sell Coolify Cloud at $5/month base, which includes two connected servers, with additional servers at about $3/month each. A commonly cited setup: one $5/month Hetzner box runs Coolify with enough headroom for 5 to 10 small apps plus PostgreSQL and Redis. Reviews comparing real workloads put the savings versus managed platforms at 70 to 85 percent.
Cloud in a Bottle is open source under AGPL-3.0, self-hostable at zero software cost, and zero telemetry. Imbue, the company behind it, sells a managed version and gives new users a $10 credit to try it. That is a similar "pay only for convenience" model to Coolify Cloud, just earlier stage.
One licensing note worth knowing: AGPL-3.0 is a stronger copyleft than Apache 2.0. For personal self-hosting this changes nothing. But if you ever build a product on top of the platform itself, the obligations differ. Check the license text before you build a business on either.
Maturity: this is where they are not remotely comparable
Coolify v4 reached stable in April 2026 after roughly two years in beta, and v4.1 added a new Railpack build pack, structured audit logging, and MCP support. Version 5, focused on full multi-server scalability, is in active development. It has a community Discord reported at over 19,000 members, years of production war stories, and hundreds of one-click service templates that have survived contact with real users.
Cloud in a Bottle launched on September 5, 2026, after 6+ months of private testing at Imbue. The curated app catalog is intentionally small, with the team saying they aim to "maintain a high bar, only adding things that actually deliver a great user experience." Early users, by the project's own admission, "will likely need a bit of technical familiarity (or a coding agent)" to get the apps they want running.
And then there is the part of the launch nobody wanted. Sharp-eyed Hacker News users noticed that an account had been filing issues across multiple unrelated GitHub projects, asking maintainers to add Cloud in a Bottle compatibility. It turned out to be an Imbue employee, and commenters observed the account appeared to be controlled with the help of an AI coding agent. It was 11 issues in 48 hours, the account was deleted, and the project acknowledged it was being addressed. I mention it not to torch the project, but because it is a perfect microcosm of 2026: even a well-meaning open-source launch now has to manage what its agents do unsupervised. If a self-hosting platform cannot keep its own automation polite on day two, that is a data point on operational maturity.
The hard problem neither fully solves
The most insightful comment in the whole thread, in my view, came from a user who argued that app deployment is no longer the hard part of self-hosting at all: "To make self-hosting 'easy' we need to solve domain registration, DNS management, and port-forwarding configuration." Their proposal was something like OpenWRT for the whole stack, a router that owns your domain registration and DNS APIs so a self-hosted box becomes reachable by anyone, not just someone with Tailscale.
He is right, and neither tool really fixes this. Coolify gets you automatic SSL once a domain already points at your server. Cloud in a Bottle gives you a beautiful dashboard that is still only as reachable as your port forwarding. The last mile of self-hosting is bureaucratic, not technical, and it is still on you.
My decision framework, if I were choosing today
Save this list. It is how I would actually decide.
- Choose Coolify if: you are deploying apps you or a team built, you want git-push deploys, you need per-app domains and logins, you value two years of production mileage, and you want the 280+ service catalog. It is a PaaS.
- Choose Cloud in a Bottle if: you are building a household personal cloud, you want one login across everything, you like the phone-style app model with inter-app permissions, and you can tolerate v0.1 maturity. It is a consumer product for technical families.
- Choose neither if: your real blocker is DNS, domains, or port forwarding. Fix that first with a good registrar API, or go the Tailscale private-network route and skip public exposure entirely.
- What I would actually do: keep Coolify for my project workloads, and run Cloud in a Bottle in a VM for the family stack, photo backup, media, notes, where the unified-auth experience is worth the early-adopter risk. Reassess in six months when the app catalog has grown.
The self-hosting wave feels different this time. The comment thread was full of people saying the appetite to leave subscriptions behind is stronger than ever, and for once the tooling might be catching up to the sentiment. Whether it is this project or the next one, the direction is clear: owning your corner of the cloud is getting easier.
I write about developer tools, self-hosting, and AI infrastructure every week. Subscribe, it's free.
Have you tried Cloud in a Bottle or Coolify? Which one won you over, and what broke? I am genuinely curious whether the unified-auth model survives contact with real households.
Top comments (0)