Self-hosted Twitter alternative: own your corner of the fediverse with GoToSocial

Twitter used to feel like a public square. Then it became X, the checkmarks went up for sale, and an algorithm decided which of your friends you actually saw. Your followers, your posts, your reach -- none of it was ever really yours. The fediverse is the way out: an open network of independent servers that all talk to each other, with no single owner, no ads and no ranking machine. GoToSocial is how you plant your own flag in it, on your own domain, in software small enough to run almost anywhere.

What GoToSocial is

GoToSocial is a fediverse server that speaks ActivityPub -- the same protocol Mastodon, Misskey and Pixelfed use. It's written in Go as a single lightweight binary, and it federates with all of them. This isn't a stripped-down demo. Your account lives at your own domain, your posts reach the whole network, and anyone on any other server can follow you, reply to you and boost you.

Where X wants you inside its app, watching its ranked feed and paying for reach or a checkmark, GoToSocial hands you the whole thing and gets out of the way. The timeline is plain reverse-chronological -- newest first, no ranking, no "suggested for you." And because it speaks the Mastodon client API, nearly every existing Mastodon phone app works with it out of the box.

The features that actually matter

• One lightweight binary. GoToSocial is a single Go executable that runs in a few hundred megabytes of RAM -- no Ruby, no Redis, no Sidekiq, no Elasticsearch to babysit. By default it keeps everything in one SQLite file, so there's no separate database service to run either, though it speaks Postgres too when you outgrow that. It's happy on a Raspberry Pi or the smallest server you can rent.
• Any Mastodon app just works. It implements the Mastodon client API, so Tusky on Android, Feditext on iOS and Semaphore in the browser connect straight to it. You post and scroll from an app you already like, not a second-rate web page.
• Genuinely granular post privacy. Every post gets its own visibility -- public, unlisted, followers-only or direct -- and you can require manual approval for new followers even on a public account. Uploaded images have their EXIF metadata stripped automatically.
• Interaction policies. Decide per post who's allowed to reply, like or boost it. Reining in a pile-on is a setting here, not a prayer.
• Federation you control. Run in the default blocklist mode like a normal instance, or switch to allowlist mode so your server only talks to communities you've explicitly approved -- a genuinely small, private network option.
• Your domain, not a blue check. X sells a checkmark; on the fediverse your handle is `@you@yourdomain`, hosted somewhere you control. That's an identity you own outright, not one you rent by the month -- and a feed with no ads in it, ever.
• Your data stays portable. Account migration with aliases and redirects, CSV import and export of your follows, followers, blocks and mutes, and an opt-in RSS feed per account mean you're never locked in -- not even to your own server.

Why self-host it instead of the hosted version

• Your data, your server. On someone else's instance you're a guest. The admin can suspend you, defederate on your behalf, read what passes through, or shut the whole thing down and take your handle with it. On your own server you're the admin, and nobody sits between you and the network.
• Cost that doesn't scale per seat. Managed fediverse hosting and "premium" social tiers bill monthly and climb with users or reach. A GoToSocial instance is a fixed, tiny amount of compute whether it's just you or you and twenty friends -- no per-seat pricing, no paying to be seen.
• Your domain, your brand. Your handle is `@you@yourdomain`, your identity across the entire fediverse, under a name you own rather than a subdomain of whatever instance you happened to sign up on. And if you ever want to move, migration is built in.

Who it's for

GoToSocial fits three kinds of people especially well. The individual who wants a personal handle at their own domain -- one account, a tiny footprint, no monthly bill for the privilege. The small community -- a family, a friend group or a club running a single instance, optionally in allowlist mode so it only federates with servers you trust. And the creator or organisation that wants an official fediverse presence under its own name, with the reach of Mastodon but none of Mastodon's sprawling stack of services to stand up. What none of them wants is to become a part-time sysadmin for the privilege -- which is the honest catch, and the next thing to talk about.

The honest setup notes

A few things are genuinely your job if you run this yourself. GoToSocial is still beta software -- solid and widely used, but actively developed, so you're expected to read release notes and update deliberately rather than blindly. Your domain is your identity, permanently. The handle bakes the domain in; there's no clean rename later, so choose the domain you'll want for years before you federate a single post. And there's the usual server upkeep: TLS and a public address so other servers can reach you, a database and a growing media cache to back up and occasionally prune, and SMTP if you want email confirmations to work.

None of that is hard, exactly. It's just ongoing -- the difference between owning a thing and babysitting it. Or let us run it: we handle the TLS, the updates, the backups and the storage, and you get the account.

Deploy it in one click

Rolling your own means renting a box, pointing DNS, configuring a reverse proxy and certificates, writing the config file, initialising the database, creating your admin account from the command line, and then owning every update and backup after that. It's a good weekend if you enjoy that sort of thing.

On Caliber Node it's the short version: pick a subdomain, and we stand up GoToSocial behind proper TLS with the database, storage and backups already wired in. You can deploy GoToSocial in one click and have a working fediverse server before you've settled on a profile picture. When an update lands upstream it's there for you -- not another chore on your list -- and your data is still yours, exportable whenever you want it.

First run

1. Deploy the app and open your new instance at your subdomain.
2. Sign in to the settings panel with your admin account and set your display name, avatar and bio.
3. Install a Mastodon client -- Tusky on Android, Feditext on iOS or Semaphore in the browser -- and log in by entering your own domain.
4. Find a few people: search a handle such as `@account@mastodon.social`, or paste a profile URL, and follow them to start filling your timeline.
5. Post your first status, choose its visibility, and watch it federate out across the network.

The bigger picture

Social media convinced us that reach is something you rent -- pay for the checkmark, feed the algorithm, and hope the platform doesn't change the rules again next quarter. The fediverse quietly proves otherwise. Your posts, your followers and your identity can live on infrastructure you control, speaking an open protocol that a hundred other servers already understand. Owning your social presence used to mean running a lot of software. With GoToSocial it means running one small binary -- or letting someone run it for you.

Deploy GoToSocial in a few minutes →

Or browse the full app catalog to see what else you can own.

One-click self-hosted apps, managed for you -- real logs, SFTP, and your data always exportable. Never a black box.