Deploy and Host Activepieces on Railway

Activepieces is the open-source, AI-first automation platform — 23k+ GitHub stars, MIT licensed, Y Combinator backed — with a clean drag-and-drop builder and 280+ integrations ("pieces") written in TypeScript. Its standout feature: every piece is automatically exposed as an MCP server — roughly 400 tools that Claude Desktop, Cursor, and Windsurf can call directly, making Activepieces the largest open-source MCP toolkit for AI agents.

Zapier's Team plan is $195/month for 50,000 tasks; heavier usage runs ~$990/month. Activepieces self-hosted on Railway gives you unlimited tasks at ~$5–15/month flat — no per-task billing, no per-piece fees, and your automation data on infrastructure you own.

What This Template Deploys

All three services connect over Railway's private network. AP_ENCRYPTION_KEY, AP_JWT_SECRET, and database credentials are generated and wired automatically — the secret management that trips up manual installs is handled for you.

About Hosting Activepieces

Activepieces combines a visual builder for non-technical users, a TypeScript pieces framework for developers, human-in-the-loop steps, AI agents, and a built-in MCP server. Running it in production needs PostgreSQL, Redis for the execution queue, encryption secrets, and a public HTTPS endpoint. This template does the official Docker Compose setup on Railway with nothing to wire by hand — private networking, generated secrets, migrations, and HTTPS all handled.

Typical cost: ~$5–15/month on Railway's Hobby plan for the full stack, with unlimited task executions. Zapier's Team plan is $195/month for a 50,000-task cap; scaling to 200,000 tasks runs ~$990/month. Activepieces self-hosted removes per-task billing entirely — you pay flat compute no matter how many automations run.

Deploy in Under 5 Minutes

1. Click Deploy on Railway — Activepieces, PostgreSQL, and Redis build automatically (~3–4 min)
2. AP_ENCRYPTION_KEY, AP_JWT_SECRET, and database credentials are auto-generated and wired
3. Set AP_FRONTEND_URL to your Railway public domain (required for webhooks and links)
4. Open your Railway URL and create your admin account
5. Build your first flow, or connect the MCP server to Claude Desktop or Cursor to drive integrations from an AI agent

No Docker Compose. No secret generation. No queue configuration.

Common Use Cases

• Largest open-source MCP toolkit for AI agents — connect the built-in MCP server to Claude Desktop, Cursor, or Windsurf and let an agent call 400+ integrations as tools without custom wiring
• Self-hosted alternative to Zapier — unlimited task executions with no per-task billing; rebuild your Zaps in a cleaner drag-and-drop builder at flat compute cost
• Self-hosted alternative to Make — advanced multi-step logic and branching without Make's per-operation pricing or its steeper learning curve
• AI-native workflow automation — native GPT and Claude pieces let flows generate text, classify data, and make decisions inline, with human-in-the-loop approval steps
• No-code automation for non-technical teams — marketers and ops staff build email-to-CRM, Slack, and Google Sheets flows without code; developers extend with TypeScript pieces
• Private automation for data-sensitive workloads — connections, credentials, and run data stay in your Railway PostgreSQL instead of a third-party automation cloud

Configuration

AP_ENCRYPTION_KEY encrypts your saved app connections — if it changes after you've added credentials, those connections can't be decrypted. This template generates it once and keeps it stable. On Railway Hobby, use an HTTPS email relay (Resend, Brevo) for email pieces.

Activepieces vs. Automation Alternatives

Dependencies for Activepieces Hosting

• Railway account — Hobby plan (~$5–15/month) covers all three services
• SMTP provider (Resend or Brevo) for email pieces — raw SMTP is blocked on Railway Hobby
• Optional: API keys for the apps you connect (added per-connection in the UI)

Deployment Dependencies

• Activepieces GitHub Repository — source and releases
• Activepieces Documentation — self-hosting and piece guides
• Activepieces MCP Docs — connect the MCP server to AI agents

Implementation Details

This template deploys Activepieces alongside PostgreSQL 16 and Redis over Railway's private network, with AP_EXECUTION_MODE=UNSANDBOXED for single-container self-hosting. AP_ENCRYPTION_KEY and AP_JWT_SECRET are generated once and shared via reference variables; database and Redis connection strings are injected automatically. Migrations run on deploy.

Set AP_FRONTEND_URL to your Railway public domain immediately — without it, webhook triggers and OAuth callbacks point to the wrong host. All flows, connections, run history, and tables persist in PostgreSQL independently of the containers, so redeploys never touch your automations. The built-in MCP server exposes your pieces as agent tools at a project-scoped, OAuth-authenticated endpoint.

Frequently Asked Questions

How much does Activepieces save versus Zapier? Zapier's Team plan is $195/month for 50,000 tasks, and heavy usage climbs toward ~$990/month. Activepieces self-hosted on Railway costs ~$5–15/month with unlimited task executions and no per-task billing. For any team running thousands of automations monthly, self-hosting pays for itself almost immediately.

What makes Activepieces different from n8n? Both are self-hostable and open source. Activepieces has a cleaner drag-and-drop builder that non-developers pick up faster, a permissive MIT license (vs n8n's fair-code), and its defining feature — ~400 MCP servers exposing every piece as a tool for Claude, Cursor, and Windsurf. n8n has more integrations and deeper code nodes. Choose Activepieces for MCP-first AI work and ease of use; n8n for maximum integration breadth.

How does the MCP server work? Every Activepieces piece is automatically available as an MCP server. Connect the project-scoped, OAuth-authenticated MCP endpoint to Claude Desktop, Cursor, or Windsurf, and your AI agent can call hundreds of integrations — send Slack messages, append Google Sheets rows, query APIs — as native tools without custom wiring.

What are Activepieces' limitations? The integration catalog (280+ pieces) is smaller than Zapier's 6,000+ or Make's 1,500+, so niche apps may need a custom TypeScript piece or the universal HTTP piece. Failed runs are retried from the execution log rather than a visual retry UI. For the widest integration catalog, Zapier still leads; for open-source MCP-first automation, Activepieces leads.

Do I lose my flows if Railway redeploys? No. All flows, connections, run history, and tables are stored in the Railway-managed PostgreSQL database. Redeploys, updates, and restarts don't affect your automations. Keep AP_ENCRYPTION_KEY stable so saved connections stay decryptable.

Can I migrate my Zapier zaps? There's no automatic importer, but the mapping is straightforward — each Zap trigger and action maps to an Activepieces trigger and piece. Common apps have full-featured pieces; anything missing uses the HTTP piece against a REST API.

Why Deploy and Host 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 get an MIT-licensed, AI-first automation platform — 280+ pieces, a clean visual builder, and the largest open-source MCP toolkit for AI agents — at ~$5–15/month flat with unlimited tasks and full ownership of your automation data.