Activepieces on Railway
Open-source no-code workflow automation with a visual flow builder, self-hosted on Railway.
Activepieces is an open-source automation platform for building workflows without code. You pick a trigger such as a webhook or a schedule, chain steps made of app integrations, and run the flow on your own server. It is often compared with Zapier and Make, with the difference that you can host it yourself and keep the workflow data in your own infrastructure.
Teams and solo builders use it for glue work between services: forwarding payment events to a chat channel, syncing form entries to a spreadsheet, or calling an API when a repository changes. Its integrations are called pieces.
Check the project's repository for the exact licence terms of the edition you run, since some features may be offered under different terms than the open-source core.
What Activepieces can do
- Visual flow builder with triggers and steps
- Webhook triggers and scheduling
- Library of app integrations called pieces
- Self-hosted, so workflow data stays in your project
- Background execution of flows
What people use it for
- Webhook-driven integrations such as Stripe to Discord or GitHub to Slack
- A self-hosted automation platform for a team or agency
- Private automations where data must stay in your own infrastructure
- Replacing a Zapier or Make account for simple flows
Videos
Running Activepieces on Railway
The Railway template deploys three services in one project: Activepieces from the activepieces/activepieces image on the latest tag, Postgres 17 and Redis 8.2.1. The image is not pinned to a version, so a redeploy can pull a newer release. Railway bills the CPU and memory the three services use.
Activepieces templates on Railway
Tracklayer templates are listed first. Other Activepieces templates follow, ordered by total deployments on Railway. How this works.
Deployment numbers as of 2026-11-20.
Questions about Activepieces
What does the Activepieces template deploy?
Three services: Activepieces, Redis and Postgres. The Activepieces service uses the latest image tag, so the version can change between deploys.
How do I log in?
The marketplace README does not describe the sign-in flow. Check the Activepieces service variables and logs after deploy, and the Activepieces documentation.
Is data kept across redeploys?
The marketplace README does not say whether volumes are attached. Check the Postgres and Redis service settings in your project before relying on it.
How do I pin a version?
Replace the latest tag on the Activepieces service with a specific release tag in the service settings and redeploy.
Similar apps
Tracklayer maintains the templates marked as such; Activepieces is a trademark of its owners and this site is not affiliated with them.
