← Templates · Databases
EL
Electric
Community2 services
Postgres sync engine — real-time partial replication of your data into client apps and local-first software.
| Runs | 2 services |
|---|---|
| Stack | electric-dbelectric |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 2 services in this stack together — electric-db, electric — wired to reach each other over the private network, on a server you already pay for.
Deploying Electric 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
- Real-time sync of Postgres data into web and mobile apps (local-first software)
- Partial, filtered replication of a subset of your data to the client, instead of polling an API
- Building collaborative or offline-capable apps on top of an existing Postgres database
Good to know
- Electric needs Postgres logical replication (wal_level=logical) — this stack runs its own dedicated Postgres with that set at startup, since Railyard's shared Postgres addon can't have its server-level WAL settings changed per app
- Runs with ELECTRIC_INSECURE=true (no auth) — switch to ELECTRIC_SECRET-based auth before exposing this beyond your own team
- This Postgres is dedicated to Electric's sync state; point your own app's writes at a separate database and have Electric read from it via a foreign/shared connection, or migrate your app's data into this one