Choosing the Right Instance

Why instance choice matters less than people fear, what each major instance signals, and when to run your own.

Jump to module

Banner

Lesson 1: Why Instance Choice Matters (and Why It Doesn't)

Most new Mastodon users get stuck on choosing an instance. Don't.

What instance choice does affect

  1. The handle in your address. @you@mastodon.social vs @you@hachyderm.io.
  2. The local timeline you see. Every instance has a "local" feed of posts from that server.
  3. The moderation rules. Some instances are stricter than others.
  4. Server uptime and stability. Some instances are run professionally; some by hobbyists.
  5. First-impression signal. Some instances signal "tech," some "politics," some "art."

What instance choice doesn't affect

  1. Who you can follow. Federation means you can follow accounts on any instance.
  2. Who can follow you. Same — anyone on any instance can follow you.
  3. Discoverability. Cross-instance discovery works the same regardless of where you're hosted.
  4. Content reach. Federation handles distribution.

Why account portability matters

Mastodon supports account migration. If you sign up on mastodon.social and later want to move to hachyderm.io, you can — and your followers come with you.

This means: pick something reasonable now. Don't agonize. You can always move.

The "just pick one" answer

If you're stuck:

  1. Generalist: mastodon.social (the original; large and stable).
  2. Tech-focused: hachyderm.io (run by Mastodon's CTO; tech-focused community).
  3. Indie/maker: indieweb.social or similar small communities.

Pick one. Spend 30 seconds. Move on.

Lesson 2: Instance Themes and What They Signal

Even though instance doesn't restrict who you can follow, your handle's instance signals something to others.

Tech-themed instances

Examples: hachyderm.io, fosstodon.org, infosec.exchange, mastodon.online

Signal: "I'm in the tech world. Devs, engineers, open-source community."

Best for: founders, developers, security, infra, anything technical.

Generalist large instances

Examples: mastodon.social, mas.to

Signal: general-purpose. Doesn't lock you into a niche.

Best for: newcomers who don't yet know their niche, or who span multiple niches.

Topic-specific instances

There are instances for: writers, photographers, artists, journalists, academics, vegan folks, and many more.

Signal: "I'm in this specific community."

Best for: if your niche has a clear topical instance, joining it gives you a built-in local audience.

Country / language instances

Examples: mstdn.jp, mastodon.uno, social.tchncs.de

Signal: "I post in this language" or "I'm in this region."

Best for: if your audience is regional or language-specific.

Personal instances

You run your own server. Your handle is @you@yourdomain.com.

Signal: "I'm serious about Mastodon" or "I care about ownership."

Best for: advanced users — covered in next lesson.

How to pick

  1. Match your primary niche if a strong topical instance exists.
  2. Generalist if not. mastodon.social is fine.
  3. Don't over-think. You can move later.

Lesson 3: When to Run Your Own

Running your own Mastodon instance is a real option. It's also a real commitment.

Why people run their own

  1. Branded handle. @max@boltastartup.com reads cleaner than @maxbolta@mastodon.social.
  2. Full ownership. No instance admin can ban you or shut down your home.
  3. Customization. You can tweak rules, themes, and federation as you like.
  4. Signaling. Running your own signals "I'm serious about the fediverse."

What it costs

  1. Money. $5-20/month for a small server.
  2. Time. Initial setup is a few hours. Ongoing maintenance is real (security patches, server updates, occasional debugging).
  3. Attention. You're now a small server admin. Things break.

Single-user vs multi-user

You can run a single-user instance just for yourself. Easier to maintain, less moderation work.

You can also open it to others (friends, your team, your community). More work, but higher reach.

Hosted alternatives

If you want a custom domain handle without running your own server, services like masto.host will run an instance for you. ~$10/month, no maintenance.

Should you run your own?

Yes if:

  • You're a developer comfortable with server admin.
  • You have a custom domain you want to use.
  • You're in this for the long haul.

Probably not if:

  • You're new to Mastodon.
  • Server admin sounds like work you don't want to do.
  • You're not sure how committed you are to the platform.

Migration is real

If you start on a generalist instance and decide to move to your own, Mastodon's account migration tooling handles it. Followers come with you. Your old posts stay on the old account; new posts go to the new account.

Common myths

  1. "Instance choice is permanent." It isn't. Migration works.
  2. "Running your own instance is required to be taken seriously." It isn't. Plenty of well-respected Mastodon users are on shared instances.
  3. "All instances federate with all others." Most do, but some have defederation policies. If your instance defederates with another, you can't see their posts.

Action Steps

  1. Pick an instance. Apply Lesson 2's framework. Don't take more than 5 minutes.
  2. Sign up. Verify. Set up basic profile.
  3. Tell yourself: this isn't permanent. You can move later if needed. Move on.

Instance choice is a small decision dressed up as a big one. Make it; move on. Next lesson: profile setup and the content warning convention.