What is GoToSocial?

Updated

GoToSocial is a federated social networking server implementation that speaks ActivityPub and exposes a Mastodon-compatible client API. It is designed to be lightweight and "backend-first": there is no bundled web frontend, so you connect to it using existing Mastodon-compatible apps or clients rather than a built-in web UI. If you want to run your own fediverse instance with modest hardware and prefer to use third-party clients, GoToSocial is aimed at that use case.

Core positioning

GoToSocial is a server (an instance) that federates with the wider fediverse over ActivityPub. Because it implements the Mastodon API, many existing Mastodon clients can talk to it. The documentation lists "Mastodon API compatibility" as a feature, alongside "Backend-first design."

The practical consequence: you run the server, and you choose your own client. The project does not ship a first-party web interface the way Mastodon does.

Key features

From the documentation's feature list:

  • Mastodon API compatibility — existing clients can connect.
  • Granular post visibility settings — control who sees a post.
  • Reply controls — limit who can reply.
  • Local-only posting — posts that stay on your instance.
  • RSS feed — subscribe to timelines via RSS.
  • Rich text formatting — formatting in posts.
  • Themes and custom CSS — customize appearance.
  • Easy to run — low operational overhead.
  • Safety + security features — moderation and safety tooling.
  • Various federation modes — choose how open federation is.
  • OIDC integration — external identity provider login.
  • Backend-first design — no bundled frontend.

How it differs from Mastodon

The clearest distinction is the frontend. Mastodon ships its own web UI; GoToSocial is backend-first, so you use a separate client. GoToSocial also emphasizes being easy to run and lightweight, which matters if you are deploying on small or low-power hardware — the docs include a section on "Managing GtS on slow hardware."

Federation behavior is configurable through federation modes, and the project documents alternatives to GoToSocial for readers comparing options.

Running it

Installation paths documented include:

  • Bare metal
  • Container (Docker)
  • Binary release .tar.gz
  • From source
  • Third-party packaging

Supported platforms listed are 64-bit BSDs and 32-bit OpenBSD, with stable and snapshot release channels. Deployment guidance covers reverse proxies (NGINX, Apache HTTP Server, Caddy 2), WebSocket, TLS, and split-domain deployments.

Practical notes

  • You will need a Mastodon-compatible client to use the instance day to day.
  • Federation openness is a configuration choice, not a fixed default you can assume.
  • The documentation includes a "Known Issues" section — check it before committing to a deployment.
  • Sponsorship and funding are mentioned (crowdfunding, corporate sponsorship, NLnet); the docs do not state that the software itself is free of cost or login requirements, so verify licensing and any hosting costs separately.