Deploy Activepieces

Open-source Zapier alternative: 600+ integrations, AI agents and MCP

Deploy Activepieces

Just deployed

Just deployed

/data

/var/lib/postgresql/data

Deploy and Host Activepieces on Railway

Activepieces is an open-source automation tool, an alternative to Zapier and Make. You build flows in a visual editor from triggers and actions across 600+ integrations ("pieces"), and add branches, loops, code steps, human approvals and AI agents. It can also expose your pieces as MCP tools for AI assistants.

About Hosting Activepieces

Activepieces runs as one Node.js container that serves the API and web app and runs a worker that executes flows. It needs PostgreSQL for flows, runs, connections and files, and Redis for its job queue. This template builds Activepieces 0.93.0 from a GitHub repo that pins the official image by digest, and adds Railway Postgres (with pgvector, for the knowledge base) and Railway Redis. The encryption key and JWT secret are generated, and the public URL comes from the Railway domain, so it deploys with no questions. Database migrations run on start, and the health check waits for /api/v1/health.

Common Use Cases

  • Automate work between SaaS tools, for example a new form entry creates a CRM contact and posts to Slack
  • Receive webhooks and run scheduled jobs that call APIs, transform data with code steps and store results
  • Build AI agents and MCP servers that act on your apps, with your own model provider keys

Dependencies for Activepieces Hosting

  • PostgreSQL (Railway Postgres; its image includes pgvector)
  • Redis (Railway Redis)

Deployment Dependencies

Implementation Details

  • First login: open the Railway domain and sign up. The first account becomes the platform admin. There is no default user or password.
  • Custom domain: after adding it in Railway, set AP_FRONTEND_URL to https://YOUR-DOMAIN so webhook and OAuth redirect URLs use it.
  • Sandboxing: the default AP_EXECUTION_MODE=UNSANDBOXED suits a single team and lets code steps use npm packages. If people you don't trust will write code steps, set AP_EXECUTION_MODE=SANDBOX_CODE_ONLY (V8 isolates, no npm). Both work on Railway. The kernel-namespace modes need a privileged container and don't.
  • Optional settings: SMTP for invitations and password resets (AP_SMTP_HOST, AP_SMTP_PORT, AP_SMTP_USERNAME, AP_SMTP_PASSWORD, AP_SMTP_SENDER_EMAIL), S3 file storage and Google sign-in can be added as variables later. See the environment variable reference above.
  • Updates: the version is pinned in the repo's Dockerfile. When the repo's main moves to a new release, Railway offers you the update, and you choose when to apply it. Read the repo's CHANGELOG.md first.

Why Deploy Activepieces 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 Activepieces 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

More templates in this category

View Template
N8N Main + Worker
Deploy and Host N8N with Inactive worker.

jakemerson
121
View Template
Evolution API with n8n
Automate WhatsApp workflows with Evolution API, n8n, and Postgres.

codestorm
113
View Template
Postgres Backup
Cron-based PostgreSQL backup to bucket storage

Railway Templates
867