What it is

Misskey is an open source, federated social media platform that is free forever, released under the AGPL-3.0 license. It is written in TypeScript and lives in the fediverse, the network of interoperable social platforms built on the ActivityPub protocol. The project has been developed for roughly ten years and carries the topics activitypub, federation, fediverse, microblog, and misskey. Its homepage and documentation hub is hosted at misskey-hub.net.

The concrete problem Misskey solves is the ownership and portability of social publishing. Instead of a single company operating one central service, Misskey instances are run independently and speak ActivityPub to each other, so posts and follows cross instance boundaries. That gives operators and their communities a microblogging platform they control, and it gives users a social graph that is not tied to one vendor's account system. The repository is public, the license permits modification and redistribution, and the project is maintained by an active contributor base with over eleven thousand stars and more than sixteen hundred forks.

Key capabilities

• ActivityPub federation, allowing instances to exchange posts and follows with other fediverse software.
• Microblogging as the core publishing model, as indicated by the project's own topic list.
• Federation across independent servers, so a single instance is not the whole network.
• Localization into many languages through the Crowdin localization platform.
• Production deployment through Docker, which the project credits as its container platform.
• Error tracking integration with Sentry to catch unexpected runtime errors.
• Visual regression testing through Chromatic to review UI changes before release.

Who uses it and how

• Self-hosters run Misskey in production using Docker containers.
• Instance operators provide a federated microblogging service to their own communities.
• Translators contribute localizations through Crowdin to extend language coverage.
• Maintainers and contributors review UI changes through Chromatic visual testing.
• Developers rely on Sentry error tracking and Codecov coverage reporting to catch regressions.

Getting started

The README points to misskey-hub.net for learning more, and credits Docker Hub as the container platform used to run Misskey in production, so the typical path is pulling the Docker image and deploying it. Package manager instructions are not stated in the provided facts.

When to use it — and when not to

Misskey suits operators who want a self-hosted, AGPL-3.0 microblogging instance that federates over ActivityPub rather than depending on a closed platform. A self-hoster must operate the deployment themselves, including the Docker container runtime, and should expect to maintain the instance over time. The most evident weakness in the facts is the open issue count of 2535, which suggests a large backlog relative to the project's contributor throughput.