← Templates · Monitoring & Analytics
RU
RudderStack
Community3 services
RudderStack, the open-source customer data pipeline — collect events once and route them to every destination you configure.
| Runs | 3 services |
|---|---|
| Stack | rudderstack-dbrudderstack-transformerrudderstack |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 3 services in this stack together — rudderstack-db, rudderstack-transformer, rudderstack — wired to reach each other over the private network, on a server you already pay for.
Deploying RudderStack 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
- Open-source Segment alternative for collecting events from SDKs/APIs and routing them to destinations
- Warehouse-first customer data pipeline — push events straight into your own Snowflake/BigQuery/Redshift
- Identity resolution and event routing without per-event vendor pricing
Good to know
- Postgres (the jobs queue) and the transformer service are both wired up automatically
- By default the server still pulls its workspace/source/destination config from RudderStack's hosted control plane — add a WORKSPACE_TOKEN from a free RudderStack Cloud account after deploy, or switch to RSERVER_BACKEND_CONFIG_CONFIG_FROM_FILE for a fully offline config instead