GNU Social
Hosting

I've been hosting fediverse software in one form or another since the StatusNet days, which is what GNU social grew out of. Back then, federated microblogging was a curiosity rather than a movement. There were a handful of public instances, a few hundred regular users between them, and a strong sense that the technology was searching for an audience. The audience eventually arrived, but it landed mostly on Mastodon, not on GNU social.

That puts GNU social in an interesting spot today. The protocol still works, the federation still functions for a meaningful slice of the network, and the codebase still runs on modern PHP. But the gravitational pull of the wider fediverse is now on ActivityPub-native platforms, and GNU social's position in that conversation is smaller than it was a decade ago.

"GNU social is the right tool if you specifically want what GNU social does. It's the wrong tool if you want a turnkey way into the fediverse in 2026. Choose deliberately, not by inertia."

Mark McNeece, Founder, 365i Hosting

If you've been running a GNU social instance for years and your community is settled there, hosting it on a £5.99 shared plan with PHP 8.5 and daily backups is a reasonable home for it. The application is light, the database stays small for a small community, and the cron-driven background queue handles federation without much fuss. We've moved a couple of long-running GNU social instances onto the platform in the past year and they've been quiet tenants since.

Where I'd hesitate is the new-instance scenario. If you're standing up a federated microblog from scratch in 2026, the question is whether you want to be part of the broader Mastodon-flavoured network with full ActivityPub support, or whether you have a specific reason to choose GNU social. Specific reasons do exist (lighter resource footprint, simpler codebase, the appeal of the older OStatus protocol for technical reasons), but they're niche. For most new fediverse projects, Mastodon, Pleroma or one of the lighter ActivityPub servers will give you broader compatibility and more active development.

Resource-wise, GNU social is gentle on shared hosting. Even a moderately active instance with a few dozen regular posters and a federated timeline pulling from many remote servers fits inside the unlimited LVE resources on our autoscaling cloud platform. The cron job runs every minute or so to process the outgoing queue, which our shared platform handles natively. Disk and database growth are slow if media uploads are reasonable.

The federation piece is the part that needs honest attention. GNU social's federation works, but compatibility with the wider ActivityPub network has gaps depending on which fork you run and which server is at the other end. Some interactions work cleanly. Some require workarounds. Some don't work at all. If you go in expecting full Mastodon-equivalent reach, you'll be disappointed. If you go in expecting a smaller but functional federated experience, you'll be fine.

For anyone running GNU social today on an ageing host, the migration to our platform is straightforward. Files, database, config, cron. We'll test it on PHP 8.3, fix any deprecation issues, and switch DNS once the test instance behaves. Free SSL is automatic. The federation re-establishes itself once the new server starts processing the queue.