Deploy appwrite
Open-source Firebase alternative: auth, databases, storage, realtime.
appwrite
Just deployed
console
Just deployed
worker-webhooks
Just deployed
gateway
Just deployed
worker-mails
Just deployed
task-maintenance
Just deployed
worker-audits
Just deployed
mongodb
Just deployed
/data
worker-databases
Just deployed
redis
Just deployed
/data
postgresql
Just deployed
/var/lib/postgresql/18/data
realtime
Just deployed
worker-deletes
Just deployed
storage
Bucket
Just deployed
Deploy and Host Appwrite on Railway
Appwrite is an open-source backend-as-a-service: authentication (email, OAuth, magic links, teams), databases, file storage with on-the-fly image transforms, realtime subscriptions, and messaging — all behind one API with SDKs for web, mobile, and server.
About Hosting Appwrite
Appwrite 1.9 is a genuinely multi-service stack — API, console, realtime, MongoDB (primary), PostgreSQL (vectors), Redis, and a fleet of background workers. This template decomposes it into 13 Railway services wired over private networking, replacing the stock Traefik ingress with a small nginx gateway that replicates its routing (/v1/realtime → realtime, /console → console, everything else → API). MongoDB runs as a single-node replica set on a Railway volume (member on loopback so redeploys never lose the primary), and file storage goes to a Railway bucket over S3 — no shared-volume juggling. First boot initializes the databases in about a minute; then open your gateway domain and create the admin account (first signup owns the instance).
Common Use Cases
- Full backend for web/mobile apps: auth, database, storage, and realtime from one endpoint
- Self-hosted alternative to Firebase/Supabase with your data on your infrastructure
- Identity provider for side projects — magic links, OAuth, teams, and sessions out of the box
Dependencies for Appwrite Hosting
- All bundled: MongoDB 8 (replica set), PostgreSQL, Redis, and an S3-compatible Railway bucket are provisioned by the template
Deployment Dependencies
Implementation Details
After deploying, open the gateway service's domain and sign up — the first account becomes the instance owner.
Known limitations on Railway:
- Functions and Sites are not available: Appwrite's executor spawns Docker containers via
docker.sock, which Railway does not expose. Auth, databases, storage, realtime, and messaging all work fully. - Custom domains for projects should be added on the gateway service (Railway handles TLS).
- SMTP is unset by default — configure
_APP_SMTP_*variables on theappwriteandworker-mailsservices to enable email delivery.
Why Deploy Appwrite 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 Appwrite 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
appwrite
nomideusz/appwrite-railway_APP_OPENSSL_KEY_V1
console
appwrite/console:8worker-webhooks
nomideusz/appwrite-railwaygateway
nomideusz/appwrite-railwayworker-mails
nomideusz/appwrite-railwaytask-maintenance
nomideusz/appwrite-railwayworker-audits
nomideusz/appwrite-railwaymongodb
nomideusz/appwrite-railwayMONGO_INITDB_PASSWORD
MONGO_INITDB_ROOT_PASSWORD
worker-databases
nomideusz/appwrite-railwayredis
redis:7-alpinepostgresql
nomideusz/appwrite-railwayPOSTGRES_PASSWORD
realtime
nomideusz/appwrite-railwayworker-deletes
nomideusz/appwrite-railwaystorage
Bucket
