An open source, federated social media platform (microblogging) that runs on the ActivityPub fediverse protocol.
fedify-dev/hollo
Hollo is a single-user, headless microblogging server that joins the fediverse and exposes Mastodon-compatible APIs for existing clients.
Open-source alternative to:Mastodon
- Stars
- 496
- Forks
- 58
- Open issues
- 29
- Last commit
- 6 days ago
What is it?
Hollo is a simple microblogging tool built on Fedify, aimed at running a personal, single-user presence on the fediverse. It is intended as a stripped-down alternative to running a full Mastodon instance for one person.
Hollo speaks ActivityPub, so accounts on Mastodon, Misskey and other fediverse servers can follow and interact with it. It has no built-in web interface; instead it implements Mastodon-compatible APIs so that most existing Mastodon clients can be used to post and read.
The project provides deployment guides for Railway, Docker and manual installation, along with documentation on environment variables, initial setup, separating worker nodes and split-domain WebFinger.
Key features
- 01Single-user microblogging server with no bundled web interface
- 02Implements Mastodon-compatible APIs for use with existing clients
- 03Federates over ActivityPub with Mastodon, Misskey and other fediverse servers
- 04Built on the Fedify framework
- 05Deployable via Railway, Docker or manual installation
- 06Supports worker node separation and split-domain WebFinger
Use cases
- Running a personal fediverse account on your own domain
- Hosting a lightweight single-user alternative to a full Mastodon server
- Posting to the fediverse from familiar Mastodon apps
Quick start
- 1
Open the installation docs linked in the README
- 2
Choose a deployment route: Docker, Railway, or manual installation
- 3
Set the environment variables and complete the setup guide
Things to know
- Hollo is single-user only, so it cannot host multiple accounts.
- It has no built-in web interface and needs a separate Mastodon-compatible client.
- It is licensed under AGPL-3.0, a copyleft license with network-use obligations for modified versions.
In collections
Topics
FAQ
- What is hollo?
- Hollo is a single-user, headless microblogging server that joins the fediverse and exposes Mastodon-compatible APIs for existing clients. Hollo is a simple microblogging tool built on Fedify, aimed at running a personal, single-user presence on the fediverse. It is intended as a stripped-down alternative to running a full Mastodon instance for one person.
- Is hollo free to use? What license does it have?
- hollo is open source under the AGPL-3.0 license. Check the license terms before using it in commercial products.
- Is hollo still maintained?
- Actively maintained. The last commit to hollo was on Nov 2, 2026.
- What can I use hollo for?
- Running a personal fediverse account on your own domain Hosting a lightweight single-user alternative to a full Mastodon server Posting to the fediverse from familiar Mastodon apps
- How do I install hollo?
- Open the installation docs linked in the README Choose a deployment route: Docker, Railway, or manual installation Set the environment variables and complete the setup guide
- Where can I get hollo?
- The source code and installation instructions are on GitHub: https://github.com/fedify-dev/hollo
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
A lightweight ActivityPub server for individual users and small trusted groups, using SQLite instead of a multi-service stack.
A free, open-source federated social network that interoperates with Mastodon, Lemmy, Diaspora, Misskey, Pixelfed and other Fediverse platforms.
A self-hosted bridge that lets static sites take part in the Fediverse, handling follows, post delivery and redirects automatically.
A self-hostable, federated social network server built on ActivityPub, letting users follow and interact across independent Mastodon and other Fediverse servers.
Self-hostable, ActivityPub-federated video platform where independent instances share content and use WebRTC P2P to lighten server load.