Self-hosting
Any community can run their own Aviary server. It federates automatically with every other instance — and with Mastodon, Pixelfed, and the wider Fediverse. No permission needed. No vendor lock-in.
Your community's data lives on your server. You control backups, exports, and access.
Your instance connects to the global Aviary and Fediverse network automatically.
Change the name, colours, or rules to fit your community's needs.
git clone https://github.com/sunnypawat/aviary.git cd aviary
cp .env.example .env # Edit .env and set: # DATABASE_URL=postgresql://... # NEXTAUTH_URL=https://your-domain.com # NEXTAUTH_SECRET=your-random-secret # UPLOADTHING_TOKEN=your-token # NEXT_PUBLIC_APP_URL=https://your-domain.com
docker-compose up -d
docker-compose exec app node node_modules/drizzle-kit/bin.cjs push
# Your instance is running at https://your-domain.com # Users on Mastodon can find your members at: # @username@your-domain.com
🌿
Self-hosting is a permacomputing choice. Your community's data doesn't depend on any company's continued goodwill or funding. Even if the main Aviary instance disappears tomorrow, your server keeps running — and your sightings, your followers, and your connections to the Fediverse remain intact.
Not ready to self-host? Use the hosted version — it's free.
Join aviary-neon.vercel.app →Questions? Open an issue on GitHub