Flowable Enterprise Platform
Commercial workflow and case-management platform with vendor Terraform and Helm deployments.
10 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
Terraform; Kubernetes manifests
Runs in
Documented customer environment
Flowable application services, database, search and persistent storage on EKS or AKS.
- AWS: Customer cloud account
- Azure: Customer cloud account
- AWS
- Azure
Servers / containers
Operated by
Your team
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.
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.
AWS Terraform ↗ · Source checked 2026-11-19
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Azure Terraform ↗ · Source checked 2026-11-19
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 | Terraform; Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers Flowable application services, database, search and persistent storage on EKS or AKS. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
| License | Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
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.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The Enterprise guide configures user SSO for Work/Engage, Design and Hub using OAuth 2.0 with Keycloak, including separate clients, redirect URIs and application security settings. This is application-specific configuration, not automatic SSO from merely installing Spring Security.
Flowable Enterprise applications; validate current product and IdP versions and replace demonstration credentials · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Flowable publishes authenticated Helm charts and separate AWS/Azure Terraform guides. The chart configures licensed product images, database and search connections, secrets and persistent services; repository credentials and compatible chart/application versions are required.
Enterprise Kubernetes chart and deployment guides; not an unrestricted open-source Flowable engine entitlement · Source ↗ · Deployment artifact ↗ (authenticated Helm repository; select a chart matching the licensed product release) · AWS Terraform guide ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The Enterprise requirements give Flowable Work a production minimum of 2 CPU and 8 GB RAM. Application disk guidance differs for files persisted in the database (10 GB) versus the filesystem (100 GB). The separate database minimum without file BLOBs is 4 CPU, 16 GB RAM and 100 GB disk; HA generally needs at least two application instances plus separately sized search, database and storage services.
Product-specific average-scenario guidance; per-application figures are not a total HA footprint · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
Flowable Enterprise Platform; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (8 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.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
Category fit
- Workflow automation
- Commercial workflow and case-management platform with vendor Terraform and Helm deployments.
- Case management
- Commercial workflow and case-management platform with vendor Terraform and Helm deployments.
Compare within Workflow automation
- Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- AWS
- Google Cloud
- Railway
- 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
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
- AWS Terraform ↗documentation.flowable.com
- Azure Terraform ↗documentation.flowable.com
- Helm Guide ↗documentation.flowable.com
- Supplier Onboarding ↗www.flowable.com
- Supplier LEAN Alert ↗www.flowable.com
- Case Management ↗www.flowable.com
- License File Renewal ↗documentation.flowable.com
- Trial Terms ↗www.flowable.com
- Latest Releases (2026.1.5.1) ↗documentation.flowable.com
- 2026.1.x Release Notes ↗documentation.flowable.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.
- AWS Terraform ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
- Azure Terraform ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Flowable application services, database, search and persistent storage on EKS or AKS. The Apache-licensed open-source engine and commercial Work/Platform distribution are different scopes. Supplier-onboarding examples require application modeling and do not establish a packaged supplier-qualification system. The commercial application requires its own licence file.
- AWS Terraform ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked