Misskey: A Federated Social Platform That Won't Sell Out
You've probably watched the social platforms you use get acquired, change their rules, or slowly turn into an ad-delivery engine. If you've ever wanted to run your own social network—or at least join one that isn't owned by a company with a quarterly earnings call—Misskey is worth a look. It's an open source, federated social media platform that, per its own README, is "free forever."
What It Does
Misskey is a social media platform you can self-host. It's federated, which means instances can talk to each other rather than living in isolation—you join a server, and that server can interoperate with others across the network. The project positions itself as a complete social platform rather than a component or a library.
The README itself is lean on architecture details, but it points to several things worth noting. There's a dedicated hub site (misskey-hub.net) where you can find an existing instance if you don't want to run your own, plus install guides for admins who do. The project maintains a contributing guide and a Discord community, and it has a Patreon for ongoing support. The README also credits the infrastructure around the project: Sentry for error tracking, Chromatic for visual regression testing, Codecov for test coverage, Crowdin for translations, and Docker for running Misskey in production.
Why It's Cool
-
The licensing promise is the headline. "Free forever" is a strong claim, and it's the kind of thing that matters when you're deciding where to put your community. You're not building on top of something that can be rug-pulled by a pricing change.
-
Federation means portability of community, not just data. If you pick an instance and later want to run your own, the federated model gives you a path. The README's two primary calls to action—find an instance or create one—reflect that you can start small and grow into hosting.
-
The tooling credits tell you this is maintained, not abandoned. Sentry, Chromatic, Codecov, Crowdin, and Docker aren't the marks of a weekend project. Visual regression testing in particular suggests the team cares about UI stability, which is often the first thing to rot in open source frontends.
-
Translation is treated as infrastructure. Crowdin being called out means the project is actively localized into many languages. For a social platform, that's a meaningful signal about who it's built for.
-
You can contribute beyond code. The README links a contributing guide and a community Discord, so if you're not a developer, there's still a route in—translations, testing, or just being part of the community.
How to Try It
The README gives you a few clear entry points depending on what you want to do.
-
Just want to use it? Find an instance through the hub:
https://misskey-hub.net/servers/ -
Want to run your own? Follow the admin install guides:
https://misskey-hub.net/docs/for-admin/install/guides/ -
Want to contribute? Start with the contributing guide in the repo (
CONTRIBUTING.md) and join the Discord community for questions. -
Want to support the project financially? There's a Patreon linked from the README.
The repository itself lives at github.com/misskey-dev/misskey, and the README also links a DeepWiki page if you want to explore the codebase with some AI-assisted orientation before diving in.
Final Thoughts
Misskey isn't trying to be everything to everyone, and the README doesn't oversell it—it hands you the links and lets the platform speak for itself. If you're a developer curious about federation, an admin who wants to run a community on software you control, or someone who's tired of platform decisions being made without you, this is a reasonable place to start. The "free forever" framing is the part to hold onto: it's a commitment, and commitments like that are worth paying attention to in a landscape where they're increasingly rare.
Follow @githubprojects for more developer tools and open source projects.