Deploy Hollo
Your own fediverse microblog server, media on a volume, no S3 needed
Just deployed
/var/lib/postgresql/data
Just deployed
/var/lib/hollo
Deploy and Host Hollo on Railway
Hollo is federated, single-user microblogging software built on Fedify. It speaks ActivityPub, so you can follow and be followed by people on Mastodon, Misskey and other fediverse servers from your own domain. It has no timeline UI of its own: you use it through Mastodon-compatible client apps such as Phanpy or Elk.
About Hosting Hollo
Hollo needs a Node.js server, a PostgreSQL database and somewhere to keep uploaded media. This template deploys Hollo 0.9.25 from the official image, pinned by digest, plus Railway Postgres for accounts, posts, followers and the federation queue. Media (avatars, headers, attachments, custom emojis) goes on a Railway volume and Hollo serves it itself, so you don't need an S3 bucket or any keys. The session secret is generated per deploy, the public domain and health check are set up, and database migrations run on every start. Nothing is asked at deploy time. Your fediverse handle is fixed by your domain when you create the account, so pick the domain first.
Common Use Cases
- Your own fediverse identity (@you@your-domain) that you control, instead of an account on someone else's Mastodon server
- A personal or project microblog that people on Mastodon, Misskey and other ActivityPub servers can follow and reply to
- Moving an existing Mastodon account to a server you own, with follower migration and data import
Dependencies for Hollo Hosting
- PostgreSQL (Railway Postgres, included)
- A Railway volume for media (included, mounted at /var/lib/hollo)
Deployment Dependencies
- Hollo source and releases: https://github.com/fedify-dev/hollo/releases
- Hollo documentation: https://docs.hollo.social/
- Environment variables reference: https://docs.hollo.social/install/env/
- Template repository (Dockerfile, changelog): https://github.com/aalfath/hollo-railway-template
Implementation Details
After deploy:
- If you want a custom domain, add it to the Hollo service first and set
STORAGE_URL_BASE=https://YOUR-DOMAINon the service. Your handle can't change after the account exists. - Open
https://YOUR-DOMAIN/setupand create the owner login (email and password). There is no default password, and until you do this anyone who opens the URL can claim the instance, so do it right away. - Create your account at
/accounts, then sign in from a Mastodon client app using your domain as the server.
Variables (Hollo service): DATABASE_URL (reference to Postgres), SECRET_KEY (generated, 64 characters) and PORT (3000). The start script turns on BEHIND_PROXY and stores media on the volume (DRIVE_DISK=fs). Optional settings such as TZ, LOG_LEVEL, MEDIA_PROXY, HOME_URL or SENTRY_DSN can be added later; see Hollo's environment variable docs. To keep media in S3-compatible storage instead, set DRIVE_DISK=s3 and the S3_*, AWS_* and STORAGE_URL_BASE variables.
Updates: the Hollo service builds from the template's GitHub repository, which pins a specific Hollo release. When we pin a new release, Railway shows an update notice in your project and you decide when to apply it. Read the repository's CHANGELOG.md first; breaking changes are listed at the top.
Why Deploy Hollo on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Hollo on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content