Google Cloud Workflows vs Workflow Engine
Google Cloud Workflows
cloud.google.comWorkflow Engine
workflowengine.ioSide by side
| Figure | Google Cloud Workflows | Workflow Engine |
|---|---|---|
| Price from | $0.01/mo | $666.67/mo |
| Free plan | Yes | Yes |
| Free trial | Yes | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 6 | 7 |
| Spec score · Workflow Orchestration Software | 8.8 (#7) | 7.8 (#25) |
| Integrations | Connectors integrate workflows with Google Cloud APIs and handle request formatting, retries, and long-running operations; examples include Pub/Sub, Firestore, and Secret Manager. | The maker lists plugins including Approval, Loops, File, Active Directory and Entra ID, Real-Time Tracking, and support for custom plugins. |
| Security | Workflows runs in a sandboxed environment without code or library dependencies that require security patches, and it can use Secret Manager to store and retrieve secrets. | The core engine has no user store and delegates workflow command authorization to an application-provided rule provider; authentication remains the host application's responsibility. |
| Support | Google Cloud customers, including free trial customers, receive Basic Support with documentation, community forums, billing assistance, and Active Assist. | The maker directs existing customers to technical support under their support plan and offers public GitHub Discussions for questions. |
Plans
Google Cloud Workflows
- Always FreeFree
- Always Free external stepsFree
- Always Free internal stepsFree
- Internal steps$0.01 a month
- Pay as you go$0.01 a month
- External steps$0.03 a month
Workflow Engine
- Workflow Engine FreeFree
- Workflow Engine Team$2,000, paid once
- Workflow Engine Complete$5,000, paid once
- Workflow Engine NEO Subscription$8,000 a year
- Workflow Engine NEO Business$10,000, paid once
- Workflow Engine NEO SaaS$15,000, paid once
- Workflow Engine NEO EnterprisePriced on request
In their own words
Google Cloud Workflows
Google Cloud Workflows is a managed orchestration platform for running Google Cloud services, custom services, and HTTP APIs in a chosen sequence. Workflow definitions use YAML or JSON and can combine ordered steps with conditions, loops, parallel work, and reusable subworkflows. Start an execution manually, through client libraries or REST, or on a schedule with Cloud Scheduler. Connectors link workflows to Google Cloud APIs such as Pub/Sub, Firestore, and Secret Manager, while workflow steps can also call custom or private HTTP and HTTPS endpoints. Reliability features include retries, polling, error handling, callbacks, and waits of up to one year. A single execution can run up to 100,000 steps and last no more than one year. IAM controls access; Secret Manager can store and retrieve secrets. Cloud Logging and Cloud Monitoring surface execution logs, volume, errors, and duration. Pricing is based on executed steps, including failed and retried steps, while idle workflows incur no charges. The free plan includes 5,000 internal and 2,000 external steps; paid usage starts at $0.01 per month, with rates that vary by step type and volume.
Workflow Engine
Workflow Engine is an embeddable.NET library for managing business processes while saving their state in your database. It supports timers, audit history, and process versioning, and includes an HTML5 visual designer that can be embedded in an application. Designer packages are available for React, Angular, and vanilla JavaScript, with a documented Blazor integration. The core package supports.NET Framework 4.6.2 through.NET 10 and is deployed on-premises or in a customer's cloud. Supported databases include SQL Server, Azure SQL, PostgreSQL, MongoDB, Azure Cosmos DB, MySQL, Oracle, and SQLite. It imports BPMN 2.0 diagrams as native schemes, but does not export diagrams back to BPMN. Workflow Engine Free is licensed for personal, non-commercial use and costs nothing; it is limited to 10 schemas and 4 execution threads. Paid options include one-time licenses and subscriptions. NEO adds an HTTP API and multitenancy, while Workflow Server is a standalone Docker service called over HTTP. The core engine has no user store; authentication is the host application's responsibility.