

Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- This is a great idea and I wish it success. Self-hosting shouldn't be a nightmare of researching and setting up 20 different applications.
Is there something similar in progress for a "tech company tech stack"? As in, rather than trying to assemble your own custom infrastructure by finding an RPC system, permissions/group manager, credential management, storage, database, service discovery, job management, monitoring etc. one "opinionated" stack that you can easily deploy, as long as you're OK accepting their choices, with all these parts already bundled and wired up.
- 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.
by bob1029 - This isn't the hard part of self-hosting, at least not anymore. In the comments here there are lots of examples of similar projects that solve basically the same problem (app selection and deployment). To make self-hosting "easy" we need to solve domain registration, DNS management, and port-forwarding configuration.
This probably requires a project more like OpenWRT that includes an API-driven relationship with a registrar. The lack of a standard (consumer accessible) domain registration API is a huge hole in automating this. If such a project gets some traction, then it could migrate to a physical router that prospective self-hosters could buy. With domain registration, DNS management, and port forwarding all in the router's software, then the remaining hard parts can be sufficiently automated to make self hosting accessible to the average gaming console owner.
by mawise - 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/
by kolleraa - "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.
by jerf - 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.
by drunner - 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...
by KomoD - The cloud space is absurd, we've sat by for 2 decades while the likes of AWS define every aspect of deployment, auth, even containerisation.
Containerisation was supposed to mean host anywhere, literally redeploy a complex set of services and their connections on any cloud provider at the drop of a hat. That is what a f**ing shipping container is, you rock up to any port in the world and the same container is lifted by any crane onto any ship or truck.
Amazon, Google, Microsoft - these people have sold vendor lock-in to the very segment of tech society that should have been fighting it tooth and nail. 20 years ago you ftp'd some PHP files and it just worked, now you have to figure out 20 IAM profiles and shit your files across buckets because everything must be 1000000x scalable out of the box.
No joke I was building a static firebase site the other day and just wanted a simple way to password protect it (like http auth) for staging so my client could see it - of all the useless shit firebase tries to lock you into they can't even do something as simple as basic http auth without a shit show and spinning up a cloud run instance or something to check a static password.
Yes we 100% need fix hosting, everything should be portable, simple, generic.
by jiaosdjf