Workflow automation on Heroku

Business automation, integrations, scripts and API workflows.

2 documented options on Heroku. Provider coverage reflects reviewed evidence, not an exhaustive compatibility claim.

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
DocuSeal Self-HostedAWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock, Azure, Google Cloud, Railway, Heroku, RenderCustomer-operated
Servers / containers
Open Source / Open Core

AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.

Vendor Azure, Google Cloud, DigitalOcean, Railway, Heroku and Render deployment paths, or a Cloudron package on a customer VM.Customer manages administrator access, signing workflows, HTTPS, secrets, database networking, mail, durable attachment storage, database/file/key recovery and image upgrades. Platform providers operate the underlying managed services. For 3.3.8 security remediation, restart every Ruby web and background process after deployment.
Scope and evidence

Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.

  • Cloudron EC2 AMI and application installation — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Cloudron customer Droplet deployment — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    Marketplace offer · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Cloudron customer Linode deployment — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Cloudron named-provider installation and Marketplace availability — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established. Cloudron currently names the Vultr Marketplace offer; use current Cloudron OS requirements, not the historical Ubuntu 20.04 tutorial.

    Package platform documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Hostinger customer VPS Cloudron template — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • LumaDock customer VPS Cloudron template — DocuSeal Self-Hosted 3.3.6 is available as Cloudron package 1.21.3. Pair its actual application package and persistent database/files with the documented Cloudron server in the customer provider account. This is a Cloudron-maintained application-platform route; upstream provider certification is not established.

    Provider guide · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor Azure Web Apps deployment — Installs the actual application container in a customer Azure resource group with PostgreSQL and Blob Storage. Configure secrets, storage and production database network restrictions rather than retaining permissive example firewall rules.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor Google Cloud Run deployment — Installs the actual application container in a customer project with Cloud SQL and Google Cloud Storage. Configure keys, bucket access and production database network restrictions. This is application hosting, not a storage-only integration.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor DigitalOcean application specification — Creates the vendor application container and PostgreSQL in a customer App Platform account. Database persistence does not preserve attachments: configure durable object storage and back up both. Pin the application image and configure real mail.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor-linked Railway application template — Installs the vendor application and PostgreSQL in a customer Railway project. The database volume alone does not preserve attachments: configure an application volume at the image data path or durable object storage. Review secrets, SMTP and backups.

    Community template · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor Heroku application specification — Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Vendor Render application blueprint — Creates the application and PostgreSQL in a customer Render account. The example selects free services; Render does not recommend those for production and the free database expires after 30 days. Use suitable paid compute/database, durable attachment storage, secrets and working outbound mail.

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-13

n8n Self-HostedAWS, Azure, Google Cloud, DigitalOcean, Heroku, HetznerCustomer-operated
Servers / containers
Source Available

Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components

Docker Compose with persistent data; database and worker topology selected for workloadCustomer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope and evidence

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

  • n8n deployment on AWS — Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • n8n deployment on Azure — Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • n8n deployment on Google Cloud Run — The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • n8n self-hosted deployment on DigitalOcean — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • n8n self-hosted deployment on Heroku — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

  • n8n self-hosted deployment on Hetzner — The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Deployment evidence and category fit

DocuSeal Self-Hosted

Automates document form filling, signature collection and completion workflows through a self-hosted application, API and webhooks. This does not establish full contract lifecycle management or regulated-record compliance.

Reviewed core 3.3.7 includes security hardening, bug fixes, and performance improvements. The separately reviewed Cloudron package snapshot is 1.21.3 with core 3.3.6; pin a current image and confirm package lag before upgrading. Back up the database and attachments, and preserve SECRET_KEY_BASE. Native deployment examples need production configuration: restrict database access and configure durable storage; Heroku/Render app filesystems are ephemeral, and the free Render database expires. Paid features require appropriate entitlements; Pro uses a license/usage connection to DocuSeal. Qualified electronic signatures are not available in the on-premises edition. Cloudron runs the application and its persistent data on a customer-controlled server. Its platform has separate plans and requires a Cloudron account for installation/updates; account, server and app-installation metadata reaches Cloudron. Remote support requires customer-granted access. The customer chooses DNS, mail and backup destinations. DocuSeal 3.3.8 fixes GHSA-78g6-f52x-q3jx, a High-severity unauthenticated denial of service in Ruby versions used by earlier DocuSeal builds. Versions before 3.3.8 are affected and no workaround is documented. Upgrade, restart every Ruby web and background process, and verify all workers use the updated runtime.

  • Vendor Heroku application specification ↗

    Vendor / upstream documentation · Reviewed 2026-11-13. Vendor support commitment: not assessed; confirm the selected release and contract.

    Creates a container application and PostgreSQL add-on in a customer Heroku account. Dyno filesystems are ephemeral: configure durable object storage for documents, retain encryption keys and back up the database.

Cloud evidence reviewed 2026-11-13. Full listing and qualifications

n8n Self-Hosted

Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.

This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.

  • n8n self-hosted deployment on Heroku ↗

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

    The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.

Cloud evidence reviewed 2026-11-12. Full listing and qualifications

Deployment and procurement checks

Private Spaces
Private Spaces provide isolated networks for dynos and selected add-ons and require an eligible verified team or Enterprise account. Review generation, region and certification scope; a general Heroku template does not establish Private Spaces compatibility. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

Account boundary: Heroku account/team and application; platform-managed infrastructure. Access: App/team access and configuration variables. Network: Application routing; network isolation depends on the selected plan.

Provider documentation ↗ · Guidance reviewed 2026-11-12. Confirm the application edition, region, support access, backup locations and operating responsibilities before choosing.

Compare this category across clouds · Search these listings · Compare 2–4 listings