Deploy and Host Activepieces on Railway

Activepieces is an open-source, AI-powered workflow automation platform for connecting applications, APIs, data, and business processes. It is a self-hosted alternative to platforms such as Zapier, Make, and n8n.

About Hosting Activepieces

Hosting Activepieces on Railway provides a simple way to build and run automated workflows without managing servers or complex infrastructure.

This template deploys Activepieces with PostgreSQL and Redis as separate services. PostgreSQL stores application and workflow data, while Redis is used for queues and background processing.

Railway provides private networking, persistent storage, HTTPS, environment variable management, and an easy deployment workflow.

After deployment, open the generated Activepieces public URL to access the visual workflow builder and create your automations.

Common Use Cases

Marketing Automation: Automate campaigns, lead capture, notifications, and customer journeys.
Sales and CRM: Automate lead routing, follow-ups, data synchronization, and sales processes.
Customer Support: Automate notifications, data processing, and customer service workflows.
Data Integration: Synchronize data between databases, spreadsheets, SaaS applications, and APIs.
AI Automation: Build workflows using AI models, AI agents, and automated data processing.
Webhook Automation: Receive events from external applications and trigger workflows.
Scheduled Automation: Run recurring workflows for reports, synchronization, maintenance, and notifications.
Internal Workflows: Automate repetitive business processes across teams and applications.

Dependencies for Activepieces Hosting

PostgreSQL: Used as the primary database for Activepieces application and workflow data.
Redis: Used for job queues, background processing, and workflow execution.

Deployment Dependencies

Why Deploy Activepieces on Railway?

Deploying Activepieces on Railway combines open-source workflow automation with managed cloud infrastructure.

This template provides:

Activepieces workflow automation platform
PostgreSQL database
Redis queue
Automatic HTTPS through Railway
Private service networking
Persistent database storage
Automatically generated security keys
Simple environment-based configuration
Easy resource scaling

The result is a straightforward self-hosted automation platform for connecting applications, APIs, databases, AI services, and business systems.

Getting Started

After deployment:

Open the generated Railway public URL.
Create your Activepieces account and workspace.
Create your first flow.
Choose a trigger such as a webhook, schedule, or application event.
Add actions to process data or interact with other applications.
Test and publish the flow.

A typical workflow looks like:

Trigger
   ↓
Action
   ↓
Condition / Branch
   ↓
API / Database / AI
   ↓
Notification / Business Process

Automation and Integrations

Activepieces can connect applications, APIs, databases, webhooks, AI services, and business systems.

It is suitable for workflows involving:

SaaS applications
REST APIs
Webhooks
Databases
CRM platforms
Communication tools
AI services
Cloud services
Custom applications

Activepieces can also be combined with other automation platforms when different tools are required in the same architecture.

AI Automation

Activepieces supports AI-powered automation and can be used to build workflows involving LLMs, AI agents, data processing, and external AI services.

Common use cases include:

AI lead qualification
Text classification
Content generation
Summarization
Data extraction
Customer support automation
AI agents
Automated decision workflows
AI-powered API pipelines

A typical AI automation architecture is:

Trigger
   ↓
Activepieces
   ↓
AI Model / Agent
   ↓
Business Logic
   ↓
CRM / Database / API / Messaging

Webhooks and APIs

Webhooks allow external applications to trigger Activepieces workflows.

This makes it possible to connect:

Application
   ↓
Webhook
   ↓
Activepieces
   ↓
Automation
   ↓
External Services

Use webhooks to connect websites, forms, SaaS platforms, custom applications, APIs, and other systems.

PostgreSQL

Activepieces uses PostgreSQL as its production database.

This template provisions PostgreSQL as a separate Railway service and connects Activepieces to it using Railway service variables.

PostgreSQL stores application data, workflow configurations, connections, and execution data.

Redis

Redis is used by Activepieces for job queues and workflow execution.

This template provisions Redis as a separate Railway service.

Redis does not need to be publicly exposed and should normally be accessed through Railway private networking.

Configuration

This template is configured for a simple self-hosted deployment.

Main configuration includes:

PostgreSQL database
Redis queue
Automatically generated JWT secret
Automatically generated encryption key
Public Activepieces URL
Production environment
Telemetry disabled
One concurrent worker execution
600-second flow timeout
30-second webhook timeout
5-minute default polling interval
Database-based file storage

For advanced options, see the official Environment Variables Reference.

Resource Requirements

Activepieces requires more resources than lightweight web applications because workflow executions run in worker processes and resource usage depends on workflow complexity.

Resource requirements depend on:

Number of concurrent flows
Flow complexity
AI workloads
File processing
API calls
Worker concurrency

For larger workloads, increase CPU and memory resources or use a separated application and worker architecture.

See the official Production Setup documentation.

Scaling

This template uses a simple architecture:

                 Railway
                    │
        ┌───────────┼───────────┐
        │           │           │
   Activepieces  PostgreSQL   Redis

For larger installations, Activepieces supports separate application and worker services.

Workers can be scaled horizontally, with the current production architecture recommending one concurrent flow per worker and additional worker replicas as workload increases.

See the official Workers Documentation and Production Setup.

Execution and Security

This template uses the UNSANDBOXED execution mode for compatibility with the simple all-in-one deployment.

Use this mode for trusted workflows and controlled self-hosted environments.

For stronger execution isolation and larger or multi-tenant deployments, Activepieces supports sandboxed execution and separated workers.

See the official Sandboxing Documentation.

Persistent Data

PostgreSQL is provisioned as a separate Railway service with persistent storage.

Workflow configuration, application data, connections, and execution data are stored in PostgreSQL.

Activepieces also supports S3-compatible storage for larger deployments and advanced file storage requirements.

See the official Environment Variables Reference for storage configuration options.

Webhooks and Custom Domains

The template automatically configures:

AP_FRONTEND_URL=https://YOUR-RAILWAY-DOMAIN

This URL is important because Activepieces uses it when generating webhook and application URLs.

When using a custom domain:

Add the custom domain to the Activepieces Railway service.
Update AP_FRONTEND_URL to the custom HTTPS domain.
Redeploy the Activepieces service.

See the official Railway Deployment Documentation.

Troubleshooting

Activepieces is still starting

Check the Activepieces logs and verify that PostgreSQL and Redis are running.

Initial startup can take longer while the application initializes the database.

Webhooks are not working

Verify that AP_FRONTEND_URL matches the public HTTPS URL of your Activepieces instance.

For custom domains, update AP_FRONTEND_URL after configuring the domain in Railway.

Database connection errors

Verify that PostgreSQL is running and that the Activepieces database configuration correctly references the PostgreSQL service.

Redis connection errors

Verify that Redis is running and that AP_REDIS_URL correctly references the Redis service.

Flows run out of memory

Reduce worker concurrency or increase the memory allocated to Activepieces.

The recommended production architecture uses one concurrent flow per worker and scales by adding workers.

Flows time out

The default flow timeout is 600 seconds.

This can be configured with:

AP_FLOW_TIMEOUT_SECONDS

See the official Limits Documentation.

Updates

This template uses the official Activepieces Docker image.

Before upgrading to a new version:

Review the Activepieces release notes.
Check the breaking changes documentation.
Test the new version with your existing workflows.
Redeploy after confirming compatibility.

License

Activepieces Community Edition is released under the MIT license.

Enterprise features are distributed under a separate commercial license. Third-party components remain subject to their respective licenses.

📚 Official Documentation

🔗 Project Resources

Build with Activepieces

Activepieces can be used to automate:

Marketing workflows
Sales operations
CRM processes
Customer support
Data synchronization
API integrations
Webhook workflows
Scheduled jobs
AI workflows
AI agents
Internal business processes

Activepieces is especially useful when you want a self-hosted automation platform with control over your workflows, integrations, data, and infrastructure.

Build your automation workflows on Railway with Activepieces, PostgreSQL, and Redis.