Cloud in a Bottle

Cloud in a Bottle is a self-hosting platform that wants running your own web apps to feel like installing apps on a phone rather than doing a sysadmin job. It comes from Imbue, whose engineer wrote the launch post on 2026-09-05 after six months of private building and testing. The source for this page is that launch post, not the repository README, so the technical detail below is the post's level of detail.

The argument behind it

The post's motivation is a version of enshittification. Software moved to the cloud because cloud delivery is convenient: no install, every device, easy sharing. Serving something from the cloud costs money, so nearly everything on the web has a company behind it whose incentives run against its users. Before the cloud, open source worked because everyone ran their own copy. The missing piece, in this reading, is an accessible way for individuals to run web software for themselves.

It surveys the options it did not pick. Sandstorm was closest in spirit and made the same argument in 2014, but is long abandoned and required changing apps to run on it. Nextcloud is called slow, unreliable and increasingly enterprise-focused. YunoHost runs apps directly on the host with no sandboxing, so one insecure app exposes the server. Coolify runs containers but leaves each app an island with its own login. These are the author's characterizations.

How it works

At the core it is an Ubuntu machine running a web server that hosts a dashboard and routes HTTP(S) requests to apps. Each app is a rootless, hardened container, which means existing software can run with small changes and still sit in a reasonable sandbox. On top of that are opt-in platform features that apps can use. Logging in to your instance logs you in to every app, with no separate accounts. There is also an interface for permissioned access to data and capabilities between apps, which the post models on the APIs a phone OS gives apps (notifications, sensors, shared health data). It says a lot of thought went into what those APIs should be for a personal cloud; the post does not list them.

The project describes itself as open source, self-hostable, zero telemetry and deliberately "magic-free". Setup documentation covers a cloud VPS, a VM on a shared home server, and bare metal.

Catalog and business model

The app catalog is curated to a high bar and small at launch, with additions weekly. Until it grows, the post says, early users will need some technical skill, or a coding agent, to find or adapt the apps they want, and it links documentation on packaging an app. The self-hosting apps already in the toolbox, such as cal-diy, romm and rsshub, are the kind of software that would need that packaging.

Imbue also sells a managed version, with a $10 free credit at launch, and the post calls that the business model supporting the project. It promises the self-hosted path runs the same code and will stay first-class. Hosted services as the funding source are one of the patterns in oss-sustainability; here the sponsor is a company rather than a single maintainer, which moves the risk from maintainer bandwidth to the company's priorities.

On watchlist: publicly launched a week before ingest, a small catalog, and a single corporate sponsor whose managed product is the revenue. The inter-app permission APIs are the part worth seeing documented, since they are what separates it from a container host.

AGPL-3.0, 1,125★, 71 forks, repository created 2026-04-16, last push 2026-09-10. Repo: https://github.com/cloud-in-a-bottle/cloud-in-a-bottle