Connect applications and run repeatable workflows. Compare single-service setups with database-backed deployments, and check persistence and worker requirements before choosing a template.
Deploy Activepieces on Polyer to build no-code automations between your business apps. The template runs the public Activepieces 0.75.0 service with private PostgreSQL 18 and Redis services; flows, connections and run history are stored in PostgreSQL. Review the default code execution mode before deploying.
Run n8n on Polyer to connect services and build automated workflows. The standard catalog template runs n8n with a separate task-runner service and local SQLite storage; use the related PostgreSQL variant if you need a separate database. Review the actual service composition and configuration before deploying.
Run n8n with a dedicated PostgreSQL database on Polyer to build and host automated workflows. Alongside n8n and its external task runner, this variant adds a private PostgreSQL 16 service that stores workflows, credentials and execution history instead of SQLite. Review both persistent volumes before deploying.
To connect SaaS apps visually, compare n8n and Activepieces. n8n's standard template runs 2 services with SQLite and offers JavaScript or Python code nodes; Activepieces runs 3, including PostgreSQL and Redis.
For background jobs defined in your own code, consider Inngest, Trigger.dev or Hatchet. Inngest runs 3 services; Trigger.dev and Hatchet run 7 and 6 and have compatibility warnings to review first.
For Python data pipelines and scheduled ETL, look at Prefect, which runs 3 services, or Mage AI as a single service. Windmill also runs scripts and internal apps, but with 7 services and compatibility warnings.