Cloud in a Bottle: making self-hosting accessible to everyone (cloudinabottle.org)

These guys have been spamming issues in repos trying to promote this project and no disclosure whatsoever that they are associated with the project.

https://github.com/search?q=%22cloudinabottle.toml%22&type=i...

I think the time for this space is here. The appetite to depart from subscriptions and loaning your personal data to ad/ai companies is stronger than ever.

Currently, a lot of this space is docker compose based and simply inaccessible to so many who may otherwise be interested. Whether or not it's this project or another, I hope something gathers enough steam soon to truly break the barriers to entry.

"We (Imbue, the company I work for) also offer a managed version, which I think is really important to making this widely accessible - and it gives us a straightforward business model to support the project."

Looking at your hosted page, I see no reference to backups. I see in your docs reference to backup, but you should definitely offer some sort of turnkey, appropriately-marked-up backup solution. Configuration difficulty is what kills self-hosting on the front end, updates make it hard over time, but when it all dies and then I have no backup is when I give up.

I can't find any reference to disk size limits anywhere. Can I host Immich on this? Can I host my media server? What will it cost? Surely not $10/month for my media collection. I'm not a hoarder and mostly have stuff ripped from my personally-owned media, which limits the size, and you're still not hosting that for $10/month. I see you have Jellyfin in the set of apps but I don't know what it will cost. The CPU & RAM limits I understand from the deploy page.

Oh, and I'm specifically referring to your hosted service here.

If your "opt-in platform features" and "interface to allow permissioned access to data and capabilities between different apps" is more expressive/discoverable than eg Cloud Foundry's "Service Broker" approach[0], then I am pretty excited! I run a lot of disparate services which don't interoperate except through explicit workflow automation pipelines (I use ConcourseCI to eg upload images to Immich [1] albums, but others might use n8n[2] for the same purpose).

The "workflow automation" approach is a lot of resource overhead and broker-config maintainance, but my kingdom to be able to arbitrarily compose apps' states, eg commutimemap.com + Craigslist.

0. https://www.cloudfoundry.org/technology/open-service-broker-...

1. https://github.com/gavmor/immich-concourse-resource

2. n8n.io

There seems to be a lot of variance between stated and revealed preferences around self-hosting.

It often seems like presenting the image of being autonomous to our peers seems more important than actually achieving it.

It takes a lot of energy to replicate what AWS and friends have done once we factor in concerns like the passage of time and entropy. I've never been able to keep a media/NAS appliance alive for much longer than 3-4 years. Inevitably, there is some kind of catastrophic event and I have to start all over with new vendors, etc. Even without any data loss this gets old. I promise you get tired of this after a while. It might seem like that would never happen and then one day it does.

You can get so much more done if you can actually afford to use the cloud. I have a really hard time believing that many people are genuinely winning on total cost of ownership with self hosting.

This is a great project! Yes, the personal cloud is coming and it's going to be for everyone.

I'm working on a project with similar goals but some different design decisions - instead of the typical containers I'm going for thin-client apps that hit a common data layer built on a fully serverless architecture. Not ready for production quite yet, but for those interested: https://starkeep.app/

So many docker app supervisors nowadays.

I'm surprised there's no such thing as a self-hosted deployment spec. An opinionated docker-compose file (or similar) with well defined inputs, outputs, and requirements that works for the average use-case.

In the age of LLM agents, still going for Docker/Podmam on anything besides local development box seems like a weird choice.

Docker has poor tooling for network level security between the containers, has issues with different runtimes per container, etc.

It is just a bit primitive if you want to expose multiple services to the internet on the same server. One of those apps will get compromised and then all the others will follow.

If you want a decent self hosted server, ask your frontier LLM agent of choice to configure kubernetes (on something like k3s) with mandatory userns mapping so nothing runs as root on the host, default deny firewall so inter-container communication is as locked down as possible, and if your router supports, set up VLANs so none of the containers can access your other devices on the LAN. Use something like backrest to handle backups, alertmanager and Grafana for monitoring, Keel for auto updates. Also consider separating ingress for public and internal services and use Tailscale with split DNS to acces the internal entrypoint. Set up Crowdsec as WAF and subscribe to their free blocklists to filter out bots. Ask it to set this all up using Ansible, so it can be maintained.

While this would be extremely time consuming to set up and maintain by hand, an agent can do and test it in a few hours.

This pitch is somewhat interesting, but, much like Sandstorm, browsing the library of pre-built apps kind of leaves me cold. It's too much like browsing a rather tiny mobile app store. There are maybe three apps that I might be interested in.

Since we have AI now, I think exe.dev's pitch is better: they provide Linux VMs, a web proxy, and integrations. You can ask the AI to build whatever web app you like. I'd love to have exe.dev, but running on my Mac Mini.

Your headline is literally the slogan of Magic Cloud. It's been around since 2019, and does this "exact thing" - Basically, "your cloud, on premises" ...

> 53 is required because instance runs its own authoritative DNS server.

Are you planning to offer alternative solutions for this, e.g. pointing a wildcard A record at the server running the instance? I'd rather not run a publicly accessible DNS server.

If this can largely automate the backup and update side of things, then it seems like a great middle ground for people like me:

I’m trying to self-host as much of my stuff as possible, but don’t have time to tinker like I used to. Hence updates, backups (etc) fall by the wayside in favour of “set and forget”.

There is a bit more mature project that does the same: https://selfprivacy.org

I have been working on literally this exact project for the past 6 months, down to the nomenclature used. Running into this on HN is… strange.

I'm trying to understand the difference between this project and FreedomBox. I mean it's great to have options, but have any of them looked over that way? Heck, FreedomBox is even built into Debian now.

Found this and never looked anywhere after: https://github.com/opencloud-eu/opencloud

golang.

App catalog looks good, but they miss Home Assistant which is a major inconvenience

Now the key question, can the hardware be made accessible to everyone. Its definitely an improvement to make self hosting software easier but the process of setting even a raspberry pi for an average consumer interested in self hosting is still a barrier. They probably will be able to figure it out via youtube and some reddit posts but there should be an easier process or way

I really like the idea, and I would like to see Tailscale evolve Aperture in this direction. Tailscale is already an easy way for anyone to connect their devices, which is essential for any sort of "personal cloud", and Aperture, while initially something of an AI gateway, is also facilitating connections to other services and apps.

If you're building a personal cloud, you also want your AI connected to it, but probably with some degree of management. Aperture already provides a fair amount in this area, and probably with a connector for Cloud in a Bottle, could give your AI safe access.

Reminds me of my old idea dating back to 2014 (https://linuxdreams.blogspot.com/2015/03/cloud-in-box-applia...). Interestingly the blog is still active.

I did a few pitches related to this at Nasscom Startup warehouse and IITM RTBI. Though this was welcomed by the panel members but it never took off due to lack of capital for such a startup during those times in India. I had to abandon and focus on my day job.

Making self-hosting really accessible isn't that easy, even if it's easy to setup the server machine itself. One needs to make their server machine accessible to everyone, which isn't generally possible due to how networks work, one needs a white IP address and making sure no incoming connections are rejected by the internet provider. Also one needs a domain. Obtaining it requires some bureaucratic burden, costs money and pricing isn't always transparent.

These barriers are high enough, so that common people can't create/host their own sites. Only skilled enthusiasts or professionals can afford having their own site.

Looks really interesting! I'd like to see immich in the available apps. For me the Auth part is not super important. But has it one-click updates?

Cloudron does something very similar (I'm a user): https://www.cloudron.io/

> Rent a box from whoever you like, and turn it into your own personal cloud.

Yeah, that’s not what cloud computing is.

Interesting project! I've found self hosting a lot more approachable with the advent of AI to help with inevitable errors. I run every new app in its own service account and as a rootless podman quadlet. There are three main difficulties that I come up against with every app. First is backups, or more accurately restoring data. My understanding is that just taking a snapshot doesn't always give you a working restore point because an app could be mid-database migration or something like that. Second is updates, and third is accessibility outside the network. I am slowly working on my own solutions, interested to know how you tackle those though?