What is cloudseeder?

Cloud Seeder by IPv6rs is a cross-platform desktop application written in Go with a Fyne GUI that simplifies self-hosting by deploying pre-configured server appliances as Podman containers. Users download the native installer for their OS (Windows, macOS, Linux), create an IPv6.rs account for external static IPs, enter their domain and credentials, and launch appliances like Mastodon, Nextcloud, Jellyfin, Ghost, Gitea, and 30+ others with one click. The app handles automated updates, runs containers on Ubuntu 24.04 LTS base with security hardening (sshd disabled, syslog disabled, minimal capabilities), and requires Podman pre-installed. It is licensed under the custom COOLER license which restricts commercial use by enterprises with >$1M revenue.

Should you self-host cloudseeder?

cloudseeder scores 42/100 on selfhost.directory (how scoring works) and ranks #13 of 20 in Application Management. It has 199 GitHub stars.

There was no stable release in the past 12 months, so check the repository's recent activity before you rely on it.

Setup is moderate: expect some configuration beyond a single command. It is Other-licensed and written mostly in Shell.

Its closest alternative on selfhost.directory is hot-updater (62/100, 1 797 stars). It scores higher overall, so compare the two before you pick. See cloudseeder vs hot-updater side by side.

Features

Automated Updates
Cross-platform Desktop App
External static IP via IPv6.rs
Fat container appliances
One-click appliance deployment
Security hardening

FAQ

How do we donate?

Donate to the respective appliance projects. For external IPs, consider IPv6.rs service.

When will more appliances come?

The team is always working on more appliances and they should arrive soon.

Can I install other stuff on my appliance?

Not recommended as updates may conflict. Better to launch another container or request a new appliance package.

How do I get the syslog?

Use journalctl commands: `journalctl`, `journalctl -e` for end of file, or `journalctl -f` to follow.

Why a fat container? Why not VM?

Initially built as a VM launcher using Multipass, but pivoted to containers after researching CVEs. Containers don't require reserving RAM/CPU per appliance, allowing more appliances to run simultaneously.

Why did you use Go and not Electron?

Go was chosen for cross-platform ability and small binary size versus Node.js. The project also built Configurator and Tray as separate reusable modules.