Cloud in a Bottle: A Personal Cloud With Cross-App APIs

1 min read
self-hostingopen-sourcecontainershomelab
View as Markdown
Originally from cloudinabottle.org
View source

My notes

Summary

Cloud in a Bottle is a new open-source personal cloud platform built by Imbue: an Ubuntu host running a web server that reverse-proxies to hardened, rootless containerized apps behind a single unified login. The pitch is that self-hosting today requires either running your own sysadmin shop (Nextcloud, YunoHost) or accepting siloed, non-integrated container hosting (Coolify). This aims for “cloud smartphone” territory where installing apps is trivial and they share auth, data, and notifications the way iOS and Android apps share OS-level APIs.

Key Insight

  • Names the specific gap in existing self-host options, worth knowing if evaluating any of them: Sandstorm (dead since around 2014, required app rewrites), Nextcloud (slow, now enterprise-leaning), YunoHost (apps run unsandboxed on the host, so one compromised app owns the whole server), and Coolify (containers work but each app is an island, with no shared login or cross-app data).
  • Core architectural idea: apps run as rootless, hardened containers so existing software works with minimal porting, similar to Coolify, but the platform layer adds opt-in APIs for cross-app integration, shared auth, and permissioned data and capability sharing between apps. That is modeled explicitly on how mobile OS APIs let apps compose into one coherent experience.
  • Business model is open-core: fully open source and self-hostable with zero telemetry, but Imbue also sells a managed hosted version. The same codebase runs both paths, and the managed version funds the open-source development.
  • Explicit chicken-and-egg admission: the project’s value depends on a deep app catalog, and the catalog is currently small because self-hostable apps with real UX polish are rare. Their curated app catalog is the forcing function, with a high bar and growing weekly.
  • It has been running privately for 6+ months before this public launch, so it is not a day-one experiment.