← Templates · Applications
A(
Appwrite (core)
Community8 services
Appwrite, the open-source backend-as-a-service — auth, databases, storage and realtime for web and mobile apps.
| Runs | 8 services |
|---|---|
| Stack | appwrite-apiappwrite-consoleappwrite-realtimeappwrite-workerappwrite-schedulerappwrite-dbappwrite-redisappwrite-clickhouse |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 8 services in this stack together — appwrite-api, appwrite-console, appwrite-realtime, appwrite-worker, appwrite-scheduler, appwrite-db, appwrite-redis, appwrite-clickhouse — wired to reach each other over the private network, on a server you already pay for.
Deploying Appwrite (core) is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Self-hosted backend-as-a-service: auth, database, storage and functions
- An open-source Firebase alternative for a small team
Good to know
- Postgres, Redis and ClickHouse are all wired up automatically
- Runs one combined worker instead of Appwrite's 15+ split workers behind its 'separate' compose profile, and the function-execution runtime is left out entirely — Cloud Functions won't run on this stack
- Email and SMS delivery need your own provider configured by hand — Appwrite ships no default sender