The short answer
Choose by workflow model first: n8n or Activepieces for app automation, Windmill for scripts and internal tools, Node-RED for event-driven devices, and Kestra for technical orchestration.
Self-hosting is useful when the workflow must reach a private system, the team needs control over its deployment or a technical owner wants to manage the operating environment. It also makes that team responsible for the database, upgrades, credentials and recovery.
The six products below solve different jobs. n8n and Activepieces are visual cross-app candidates. Windmill connects scripts and internal apps. Node-RED fits event-driven and edge work. Kestra coordinates technical jobs. Automatisch offers another self-hosted app-automation model.
The order reflects documented fit, with different licenses and editions. n8n uses the Sustainable Use License for applicable source; other products combine community and commercial components. Self-hosting also leaves an external data path whenever a flow calls a SaaS app or AI provider.
The shortlist at a glance
Prices use the billing basis shown. Page, task, credit and execution allowances measure different things. On a small screen, scroll the table horizontally.
| Tool | Best fit | Price and billing basis |
|---|---|---|
| 1. n8n | Visual cross-app workflows | Cloud Starter: €20/month billed annually for 2,500 workflow executions. Self-hosted Community has no software subscription fee; hosting and maintenance remain yours. |
| 2. Activepieces | An extensible visual core | Free lists 1,000 credits/month and up to five users. Plus is US$20/month for 10,000 credits; additional credits are US$0.007 each. |
| 3. Windmill | Scripts with operational interfaces | A free self-hosted edition is available. Paid pricing depends on edition, seats and worker configuration; infrastructure remains an additional operating cost. |
| 4. Node-RED | Event-driven and edge integrations | Apache-2.0 software with no core subscription fee. Budget separately for hosting, support, maintenance and any third-party services. |
| 5. Kestra | Data and infrastructure orchestration | Open-source core has unlimited flows and executions; infrastructure costs remain. Enterprise uses a quoted annual per-instance subscription; Cloud requires access and pricing confirmation. |
| 6. Automatisch | Supported trigger-and-action integrations | Community Edition uses AGPL-3.0 and can be self-hosted without a software subscription. Enterprise has separate commercial terms; hosting and support are additional. |
What matters for this decision
- Workflow model
- Match visual app connections, code-first internal tools, edge events or declarative job orchestration to the work being operated.
- Edition and license
- Check the specific source, image and paid features you plan to deploy; self-hosted does not mean unrestricted reuse.
- Operating requirements
- Budget the database, backups, worker capacity, upgrades, logs and the person responsible when a dependency changes.
- Actual data path
- Map where credentials, execution history and payloads reside, including any external SaaS or model-provider calls.
The ranked picks
n8n
Best for visual cross-app workflows
A visual automation platform combining app nodes, AI steps, HTTP requests and code, with cloud and self-hosted deployment.
n8n is the first shortlist here for technical teams wanting app nodes, HTTP requests, code and AI steps in one visual workflow model. Community provides a self-hosted starting point.
The tradeoff: Community excludes several collaboration and governance features. Review Sustainable Use and enterprise boundaries before planning embedded or resale use.
Price and billing: Cloud Starter: €20/month billed annually for 2,500 workflow executions. Self-hosted Community has no software subscription fee; hosting and maintenance remain yours.
Check before choosing: Community omits features including projects, SSO and workflow sharing.
Activepieces
Best for an extensible visual core
A flow and AI automation platform with managed cloud and self-hosted options, plus extensible integration pieces.
Activepieces offers a self-hosted integration core with extensible pieces and a visual builder. It suits teams that want app-style automations while retaining deployment choice and source access.
The tradeoff: The MIT core and enterprise directories have different terms; paid features and operating requirements still need evaluation.
Price and billing: Free lists 1,000 credits/month and up to five users. Plus is US$20/month for 10,000 credits; additional credits are US$0.007 each.
Check before choosing: AI steps can consume more credits; own model keys shift model billing.
Windmill
Best for scripts with operational interfaces
A self-hostable platform for assembling scripts into workflows and giving teams apps to run them.
Windmill is a good candidate when engineers already have scripts and want to assemble them into flows or expose them through internal apps. Its code-first model distinguishes it from a connector-only product.
The tradeoff: Source and prebuilt Community images have different licensing terms. Check worker, seat and enterprise-feature requirements for the intended deployment.
Price and billing: A free self-hosted edition is available. Paid pricing depends on edition, seats and worker configuration; infrastructure remains an additional operating cost.
Check before choosing: Technical ownership is needed for workers, dependencies and upgrades.
Node-RED
Best for event-driven and edge integrations
A flow-based programming runtime for wiring events, APIs and devices together, including on local or edge hardware.
Node-RED’s lightweight Node.js runtime and flow editor suit event-driven integrations, including devices and local services. Its functions and community nodes provide extension points for a technical owner.
The tradeoff: Secure the editor and runtime deliberately; the official documentation says the editor is not secured by default.
Price and billing: Apache-2.0 software with no core subscription fee. Budget separately for hosting, support, maintenance and any third-party services.
Check before choosing: Editor authentication and HTTPS require deliberate configuration.
Kestra
Best for data and infrastructure orchestration
A declarative workflow orchestrator for data, infrastructure and application jobs, with code and guided editors.
Kestra is relevant when the job is coordinating scripts, data tasks, schedules and events across systems. Declarative workflows and plugins support an engineering-led operating model.
The tradeoff: It is a larger conceptual step from a two-app shortcut; approvals and governance capabilities differ between editions.
Price and billing: Open-source core has unlimited flows and executions; infrastructure costs remain. Enterprise uses a quoted annual per-instance subscription; Cloud requires access and pricing confirmation.
Check before choosing: Its orchestration model suits a technical owner more than a first SaaS shortcut.
Automatisch
Best for supported trigger-and-action integrations
A self-hosted visual app-automation project focused on connecting business services without writing each integration from scratch.
Automatisch provides a visual business-app automation project that can run through Docker. It is worth evaluating when its supported integrations cover the specific triggers and actions your team needs.
The tradeoff: Community and Enterprise use different licenses. Verify integration coverage and preserve the credential-encryption configuration during maintenance.
Price and billing: Community Edition uses AGPL-3.0 and can be self-hosted without a software subscription. Enterprise has separate commercial terms; hosting and support are additional.
Check before choosing: Confirm that each exact app trigger and action exists before selection.
Choose by the constraint you have
- You need familiar app nodes plus custom API calls: Start with n8n and ActivepiecesCompare the exact connector and edition requirements on representative flows.
- Engineers already maintain scripts for business users: Shortlist WindmillEvaluate how users run the work and how engineers review and promote changes.
- The inputs are devices, messages or local events: Evaluate Node-REDMatch protocol and node support with the runtime you can operate.
- The work is a chain of technical jobs: Include KestraAssess dependencies, schedules and recovery rather than just the visual editor.
Prove the operating model before moving production work
- Deploy the chosen edition in an isolated test environment and list its database, workers, credential store and external dependencies. Name an operational owner.
- Run a representative flow with authorized sample data. Trace the payload and execution history through each external service; note what self-hosting does and does not control.
- Create a backup and restore the deployment in a separate environment. Verify that credentials and flow definitions remain usable without replacing encryption settings blindly.
- Test a failed dependency, a worker restart and a version change. Record the recovery process, ongoing hosting cost and paid features required before approving a production move.
Keep the trial result and the original input together. A vendor feature list establishes what to investigate; it does not establish your accuracy, savings or operating cost.
Questions before you commit
Are all six tools open source?
Their licensing differs. Node-RED and Kestra cores use Apache-2.0; Automatisch Community uses AGPL-3.0; Activepieces and Windmill contain separately licensed portions. n8n’s applicable source uses the Sustainable Use License. Check the linked license for the exact edition.
Is self-hosting always cheaper than cloud automation?
No. A software subscription can be only one part of the cost. Include infrastructure, maintenance, monitoring, recovery and third-party calls, then compare that total with the managed plan your workflow actually needs.
Does self-hosting make an AI workflow private?
It controls where the workflow engine runs. A step that sends information to an external model or SaaS service still has an external data path. Map those destinations and retention settings for the actual flow.
Can a nontechnical team run these platforms alone?
Visual editors help with authoring, but a production self-hosted deployment needs infrastructure ownership. If nobody can maintain the runtime, a managed edition may be a better operational fit.
Sources and research limits
We checked the official pages linked below on October 27, 2026. Recommendations combine those documented capabilities with the specific workflow in this guide. Features, rates and availability can change. Confirm the current terms and run the evaluation above before choosing.
Published prices are in US dollars unless explicitly stated. An annual-billing monthly equivalent requires the vendor's annual commitment. A quote-based plan is not treated as free. Missing or ambiguous prices are identified instead of estimated.
- n8n. Plans and deployment · Community edition boundaries · License. Checked October 27, 2026.
- Activepieces. Pricing and credit rules · Self-hosting options · License boundaries. Checked October 27, 2026.
- Windmill. Product model · Pricing and edition limits · Source and binary license distinctions. Checked October 27, 2026.
- Node-RED. Project capabilities · Runtime security configuration · Core license. Checked October 27, 2026.
- Kestra. Editions and features · Core license. Checked October 27, 2026.
- Automatisch. Project and edition licenses · Installation and operating requirements. Checked October 27, 2026.