Say hello to Co-op Cloud. It’s a system designed for small libre hosting providers based upon docker swarm.

Find out more:

We also have a public matrix room at

We imagine this is particularly interesting for the folks looking at Cloudron, YunoHost and other similar systems for self-hosting management.

Delighted to finally get this out public and looking forward to comments/questions/critique/testing.

🎊 🎆 💕 🖥️

@autonomic This looks really cool! i noticed something that was a bit confusing in the getting started guide - the section with the example Nextcloud deployment has different domains in different commands.

@redoak @autonomic thannkkkksss yeah i fixed that :blobpats: if you have any issues with diving into it please let us know! docs can always get better

@autonomic @kawaiipunk do you have defined security and privacy policies/processes yet that you can share with members or is that coming later?

@Orwelldonesteak @autonomic In what regards?

Do you mean our co-op in general or co-op cloud specifically?

@Orwelldonesteak @autonomic Nooo, that's fine.

Here's what we've written so far on that ^^

A interesting thing to note is that you can do compartmentalisation in any way you want. You could have one app per VPS or a separate VPS per client etc. It's really up to you.

@Orwelldonesteak @autonomic You can also follow all the standard procedures for securing Docker as well. Defence in depth!

@federico3 @autonomic @kawaiipunk policies/procedures, not technical controls
Like, process for usinn root password in the event that Sudo accounts are locked, infra admin password strength requirements, etc

@Orwelldonesteak @autonomic We do have that stuff but it's not public yet sorry.

That's more general server hardening stuff that's outside of the scope of Co-op Cloud project itself.

Digital Ocean and Mozilla have some good guides for that.

@kawaiipunk @autonomic so I thought you were hosting docker images, or did I misunderstand

@kawaiipunk @autonomic so what I’d be looking for is the policies pertaining to YOUR accounts. So like I’d want to see the policies you hold yourselves to.

@Orwelldonesteak @kawaiipunk @autonomic Co-op Cloud app definitions use upstream Docker images (with a couple of small exceptions); the "security policy" on Docker images is "do whatever upstream does" 🙃

@handle @kawaiipunk @autonomic
Yeah so what I want to know is “are their formal policies for how the people running the underlying infrastructure operate and behave”. This isn’t a question about guest security, I’m asking about the host level controls. Think of it like I’m asking for a SOC-2 type 2.

@Orwelldonesteak @kawaiipunk @autonomic ah that makes sense 🙏

Co-op Cloud doesn't currently have "people running the infrastructure", at this point it's a software project rather than an organisation that provides hosting services.

Autonomic, the group that's launched Co-op Cloud, does host services using Co-op Cloud (including some of the Co-op Cloud infrastructure), and like @kawaiipunk says that information isn't published yet.

@raphaelbastide @autonomic Oh nice!! Thanks so much. We love it. Are you 100%? I'll ask on our end.

Our graphic designer will hate me if they see how I stuck a black background on their lovely transparent logo 😅

@autonomic this is great, something i've been dreaming about :) unfortunately, in-dream-version was #ansible with (which would help with publishing and sharing roles, one of the cons for ansible you point out). that would also keep the #debian package as the packaging unit instead of docker images. this would be a simpler architecture. would require the implementation of the cluster/ha logic in ansible, but it'd be leaner and more modular and reusable, i think.

@autonomic Verrry interesting! It will be good to have a solid alternative to Cloudron.
Sign in to participate in the conversation
Sunbeam City 🌻

Sunbeam City is a anticapitalist, antifascist solarpunk instance that is run collectively.