Cloud in a Bottle vs Umbrel, CasaOS, YunoHost, Coolify

Cloud in a Bottle is an open-source self-hosting platform that Imbue released under the AGPL-3.0 license on September 5, 2026. Installed on a single Ubuntu machine, its Python control plane serves a dashboard and routes incoming HTTP(S) requests to individual apps running in rootless, hardened Podman containers. Its headline feature is unified authentication: log into the dashboard once, and you don't need to sign in separately to each connected app.

At the core of the architecture sit Caddy, which terminates HTTPS, and CoreDNS, which issues wildcard subdomains. Together they give every installed app its own HTTPS-secured subdomain automatically. Each app is defined by a cloudinabottle.toml manifest, and the project says any Dockerfile-based, containerized app can be added this way without forking the core project.

- Unified auth: One dashboard login grants access to every connected app
- Container isolation: Each app runs in its own rootless, hardened Podman container, keeping permissions separated between apps
- Automatic HTTPS: Caddy plus CoreDNS issues a dedicated subdomain and TLS certificate for every app automatically
- App catalog: Apps can be added from cloudinabottle.org/apps, but the team says it is deliberately curated to keep UX quality high — as of September 2026, the supported list is still limited

The only requirements the official docs spell out are a freshly installed Ubuntu 24.04 machine and a root filesystem that supports idmapped mounts (ext4, xfs, or btrfs). Specific minimum RAM, CPU, or disk figures are not publicly stated as of September 7, 2026. The documentation walks through three separate deployment scenarios: a cloud VPS, a dedicated home server, and a home machine shared with family.

This provisioning script creates an unprivileged host user, installs the required packages plus rootless Podman, clones Cloud in a Bottle onto the machine, and registers it as a systemd service — all in one pass. If you don't want to run your own server, Imbue also offers managed hosting (with a $10 starting credit). The idea of logging into a dashboard and then operating each app under your own account echoes the philosophy behind self-hosting the dev environment itself, as seen in Coder.

- Get a domain and point its A record at your server's IP address
- Run the provisioning script above to initialize the Ubuntu machine as a "host"
- Open the dashboard in a browser and create the owner account
- Pick and launch apps from the catalog — from then on, the same login works for all of them

Self-hosting platforms already exist in this space: Umbrel and CasaOS, which feel closer to a consumer NAS; YunoHost, with years of community track record; and Coolify, closer to a developer-facing PaaS. What sets Cloud in a Bottle apart is putting unified authentication front and center from day one. That said, YunoHost also ships its own SSO layer (SSOwat) with LDAP integration, giving compatible apps a unified login too — so unified auth by itself isn't unique to Cloud in a Bottle.

- Good fit: A solo developer who wants to consolidate several self-built or open-source apps behind one login
- Good fit: Someone comfortable with Ubuntu and containers who can manage their own server
- Poor fit: An organization that needs to run a specific existing business application as-is, given the still-limited app catalog
- Poor fit: Anyone without server-operations experience who isn't willing to handle incident response themselves (unless using the managed option)

Before launch, an account believed to be linked to Imbue opened roughly eleven issues on unrelated GitHub repositories requesting cloudinabottle.toml support, without disclosing the affiliation. This was called out in the Hacker News discussion (around 600 points and roughly 300 comments as of September 2026). Creator Zack Polizzi acknowledged the issue, saying such requests should have come from a real, disclosed account, and characterizing it as a mistake rather than a deliberate spam campaign. Because self-hosting projects ask users to hand over personal data — family photos, password managers, and the like — trust matters more here than in most software categories, so this episode is worth noting as a matter of record.

Self-hosting can cut cloud subscription costs, but it also shifts every operational responsibility that a cloud provider used to shoulder back onto your own organization. The question of how much to keep in the cloud versus running in-house echoes the trade-offs discussed in hybrid cloud and local LLM cost reduction. Before adopting it, decide in advance who inside the company owns each of the following.

- Backups: You are responsible for designing and testing regular off-site backups against failure, human error, or ransomware
- Power and connectivity: If the machine sits at home or in your office, a power outage or line failure takes the service down directly
- Security patching: Deciding when to apply OS and container-runtime security updates is now your call, not a cloud provider's
- Domain and network management: Exposing the service externally requires a domain and a stable connection, and managing those contracts and settings becomes your team's job