Activepieces Self-Hosted
Self-hosted workflow automation platform with integrations, triggers, actions and worker execution.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented.
Runs in
Documented customer environment
Application and worker containers with deployment-specific database and queue services
- AWS: Customer cloud account
- Google Cloud: Customer cloud account
- Railway: Customer platform workspace
- AWS
- Google Cloud
- Railway
Servers / containers
Operated by
Your team
Customer manages application configuration, secrets, integrations, backups and upgrades. AWS and Google Cloud paths require customer-managed infrastructure; Railway operates the underlying platform within the customer project.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Activepieces deployment into a customer AWS account with Pulumi ↗ · Source checked 2026-11-13
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Google Cloud VM deployment ↗ · Source checked 2026-11-13
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Railway project deployment ↗ · Source checked 2026-11-13
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official AWS Pulumi stack, Google Cloud VM guide or Railway template; Docker Compose and Kubernetes/Helm are also documented. |
|---|---|
| Infrastructure | Servers / containers The documented deployments run long-lived application and worker containers with persistent data services. Railway operates the underlying platform; managed databases and load balancers do not make the application runtime serverless. |
| Licensing model | Open Source / Open Core Activepieces Community Edition core is MIT licensed. Enterprise and cloud feature directories use a commercial license; confirm the selected edition and entitlements. |
| License | MIT-licensed Community Edition core; enterprise and cloud feature directories use commercial terms. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
The paid SSO guide explicitly documents SAML for self-hosted Enterprise. Company-domain verification and identity-provider setup are required; Google sign-in has separate self-hosted credentials.
Self-hosted Enterprise SAML; not the free hobbyist mode · Source ↗ · Reviewed 2026-11-14
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official Compose workflow generates secrets and runs application/worker/database/cache services. Its worker replica count needs sizing and encryption keys need backup; the hobbyist single-container mode has different limits.
Compose deployment; not the embedded-database hobbyist mode · Source ↗ · Deployment artifact ↗ (repository default branch (moving; select matching application release)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Compose guide requires at least 2 vCPU and 4 GB RAM. Workflow concurrency and the default worker replica count require workload-specific sizing; the hobbyist embedded-database install is a different topology.
Activepieces Compose baseline; not guaranteed workflow throughput · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The 0.93.0 licensing guide identifies the core as MIT-licensed and enterprise/cloud feature code as commercially licensed. Using those enterprise features in a self-hosted installation requires an Activepieces licence obtained from sales.
Self-hosted core versus commercially entitled enterprise features; no hosted-plan price used as a self-hosted quote · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was 0.93.0, published 2026-11-08. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream activepieces/activepieces release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry covers self-hosted Activepieces, not Activepieces Cloud. The AWS template can provision RDS PostgreSQL, Redis, load balancing and Route 53 integration. The Google Cloud guide uses a VM/container example with SQLite and in-memory Redis; confirm release compatibility and use the current production database and queue requirements. Railway deploys into a customer project on platform-managed infrastructure. Enterprise features require a separate license.
Category fit
- Workflow automation
- Builds event-driven business automations from triggers and actions, with customer-operated workers and integrations.
Compare within Workflow automation
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- Documenso Self-HostedSelf-hosted electronic-signature and document workflow application with a Railway deployment path.
- Railway
- DocuSeal Self-HostedSelf-hosted document forms and electronic-signature workflows with API and webhook integration.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Linode
- Vultr
- Hostinger
- LumaDock
- DocuWare On-PremiseCustomer-operated document repository, email capture and document-workflow platform on Azure VMs.
- Azure
Showing 8 of 25 other listings in Workflow automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow automation →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-hosting and installation options ↗www.activepieces.com
- Official AWS Pulumi deployment ↗www.activepieces.com
- Community and enterprise licensing ↗github.com
- Google Cloud VM deployment ↗www.activepieces.com
- Railway project deployment ↗www.activepieces.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Activepieces deployment into a customer AWS account with Pulumi ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor-maintained Pulumi template deploys Activepieces into the operator's AWS account and can create VPC, compute, RDS PostgreSQL, Redis, load-balancing, ECR and Route 53 resources. Review template defaults, image versions, IAM permissions, secrets and production hardening.
- Google Cloud VM deployment ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents running the Activepieces application container on a Google Cloud VM or instance group. Its example uses SQLite and in-memory Redis; confirm compatibility with the selected release and follow current production database, queue and security requirements.
- Railway project deployment ↗ · Railway
Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor documents a Railway template that deploys the Activepieces application with PostgreSQL and Redis into the operator's project. Railway manages the underlying infrastructure; the operator configures secrets, application access, persistence and backups. This is separate from Activepieces Cloud and does not establish ownership of an underlying hyperscaler account.
- Activepieces deployment into a customer AWS account with Pulumi ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked