Software on Heroku
Software with a documented deployment path in a customer environment on Heroku.
11 listings, including 11 from other publishers. Search and filter Heroku listings →
Read this page as JSON or Markdown.
Each listing needs its own deployment evidence. A cloud badge identifies a documented option, not a certification or an exclusive list of compatible providers. FormKiQ listings carry a Directory Publisher disclosure.
Customer-account guidance
- Account boundary
- Heroku account/team and application; platform-managed infrastructure
- Network
- Application routing; network isolation depends on the selected plan
- Identity & access
- App/team access and configuration variables
- Deployment tooling
- Deploy with Git, containers or app templates; configure paid dynos, database add-ons and durable file storage.
Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account. Provider boundary source ↗ · Checked 2026-11-20
Official provider guidance ↗ · Source reviewed 2026-11-12. Check region, service availability, backup destinations and support access for your deployment.
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.
Browse by category
11 categories on Heroku. Counts show matching listings; a listing can appear in more than one category.
Business operations4 categories
Governance & industries1 category
Content & collaboration1 category
Data & analytics2 categories
Developer platforms & operations2 categories
AI tools & infrastructure1 category
No categories match your search.
Documented software
Deployment evidence and qualifications
Customer-operated content management and website application framework.
- Heroku Cookbook ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Apostrophe application on Heroku with MongoDB and durable asset storage. The current guide initializes an Apostrophe project through its CLI. Old free-tier examples are not current price promises; Atlas and asset storage can be outside the Heroku account.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The current guide initializes an Apostrophe project through its CLI. Old free-tier examples are not current price promises; Atlas and asset storage can be outside the Heroku account.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Heroku Cookbook ↗
Deployment evidence and qualifications
Self-hosted no-code database for organizing, relating and collaborating on business data.
- Baserow Heroku application template ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide documents a beta deployment template for the Baserow application and supporting Heroku services, with configuration and scaling instructions. It requires paid resources; review the current template, image, database and file-storage settings before production use.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application, database and storage, applies updates and configures backups.
Scope: Self-hosting is available independently of Baserow Cloud. The core is largely MIT-licensed, while premium features need a paid license. The official AWS guide documents EC2, ECS/Fargate and EKS paths; it does not establish equivalent deployment support on every hyperscaler.
License: MIT-licensed core with paid premium features and subscription terms
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Baserow Heroku application template ↗
Deployment evidence and qualifications
Open-source civic participation and participatory-budgeting platform.
- Heroku Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Rails application and PostgreSQL on Heroku or the project's DigitalOcean/Ansible deployment. Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Proposal debate, public voting and participatory budgeting are not the same as grant-contract administration. Heroku requires durable external uploads. Match the application and installer releases; database-only suggestions for other clouds do not establish app-hosting paths.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Heroku Guide ↗
Deployment evidence and qualifications
Self-hosted document forms and electronic-signature workflows with API and webhook integration.
- 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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: 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: 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.
License: AGPL-3.0 core; Pro features and the private Pro image use separate commercial terms.
Cloud evidence reviewed 2026-11-13. Read the full listing and sources →
- Vendor Heroku application specification ↗
Deployment evidence and qualifications
Open-source business operations platform for people, projects, time and financial records.
- Heroku Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Ever Gauzy application/API, database and required workers using provider-specific deployment recipes. The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The vendor supplies separate provider recipes. Application, desktop-agent and prerelease versions differ; verify each recipe and optional Enterprise entitlement before enabling it.
License: GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Heroku Guide ↗
Deployment evidence and qualifications
Open-source verifiable election software for organizational and committee voting.
- Heroku Procfile ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Helios web service, PostgreSQL, election state and configured authentication using upstream Fly or Heroku artifacts. The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The upstream Fly migration guide requires an election-free window, preservation of secrets and the existing public URL, and a rollback plan. The deployment artifacts do not certify election suitability or remove the need to validate the organization's election process.
License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Heroku Procfile ↗
Deployment evidence and qualifications
Open-source funding-application, review and grant-management software from Open Technology Fund.
- Heroku Guide ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Hypha web and background services with Heroku PostgreSQL and separately configured durable file storage. Heroku dyno filesystems are ephemeral; production uploads require the documented external storage configuration. Institutional forms, review roles, notifications and grant workflows need their own setup.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: Heroku dyno filesystems are ephemeral; production uploads require the documented external storage configuration. Institutional forms, review roles, notifications and grant workflows need their own setup.
License: BSD-3-Clause for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Heroku Guide ↗
Deployment evidence and qualifications
Automate integrations and business processes with a customer-hosted workflow editor and 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.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Scope: 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.
License: Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- n8n self-hosted deployment on Heroku ↗
Deployment evidence and qualifications
Node.js application backend for data APIs, users, permissions and server-side application logic.
- Parse Server deployment on Heroku ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide documents the Parse Server application on Heroku with MongoDB Atlas, including project configuration and validation. The application and database are in separate customer-controlled services; verify database network access, current runtime versions, secrets and production security.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages Node services, database, class/object permissions, master keys, storage adapters, backups and upgrades.
Scope: Cloud Code is code executed in the server environment, not evidence of a vendor-operated cloud dependency. External storage, push-notification providers and third-party adapters have their own boundaries and licenses. GHSA-43rg-r2xr-q686 affects Parse Server versions before 9.12.0-alpha.3: creating a user with an existing user's auth data can return protected fields and hidden auth-adapter data, including MFA secrets and recovery codes. The advisory concerns the logging-in user's own object and requires that user's auth data or an applicable session token; it is not an arbitrary-user disclosure. Requests using the master or maintenance key are unaffected. There is no known workaround; Parse Server 8 is not patched, and the first published patched version is the 9.12.0-alpha.3 prerelease.
License: Apache License 2.0 for upstream Parse Server.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Parse Server deployment on Heroku ↗
Deployment evidence and qualifications
Self-hosted headless CMS with structured content, APIs and assets.
- Install on Heroku | Squidex ↗
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Squidex application, database and asset storage using provider-specific instructions. The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
Scope: The application provider recipes are distinct from Squidex SaaS. Provider-managed MongoDB and object storage affect permissions, residency and backups. The GCP recipe limits Cloud Run to one instance and explicitly says autoscaling is untested; its Atlas database is a separate service boundary.
License: MIT for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
Cloud evidence reviewed 2026-11-19. Read the full listing and sources →
- Install on Heroku | Squidex ↗
Deployment evidence and qualifications
Self-hosted website and event analytics application with dashboards and PostgreSQL storage.
- Umami self-hosted deployment on Heroku ↗
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide deploys the Umami application and PostgreSQL in the customer platform account or project, with application configuration and administrator login. The customer controls the application and database services while the provider operates its infrastructure. Select compatible images, set the application secret, change default credentials and arrange backups.
Application boundary: Customer platform workspace. Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Operations: Customer manages tracking endpoints, database, admin credentials, retention, TLS, backups and upgrades.
Scope: Change the documented initial administrator password and configure production secrets. Third-party integrations, tracking destinations and external databases require separate configuration; Umami Cloud is a distinct offering.
License: MIT License for upstream Umami.
Cloud evidence reviewed 2026-11-12. Read the full listing and sources →
- Umami self-hosted deployment on Heroku ↗
Compare all cloud providers · Plan a deployment · Browse without publisher listings