Buyer guide · Self-hosting
What “free self-hosting” really costs.
A self-hosted automation tool can remove a SaaS subscription and still cost more. The missing line item is operations: infrastructure, backups, upgrades, security and the hours spent fixing the system when it is supposed to be saving time.
The five cost buckets
- Compute: VPS, VM, home server electricity or cloud resources.
- State: database, object storage, backups and retention.
- Observability: logs, uptime checks and alerts.
- Maintenance: upgrades, dependency changes, migrations and incident recovery.
- Risk: expected cost of downtime, lost runs or exposed credentials.
A realistic formula
monthly self-host cost = compute + storage/backups + monitoring + paid add-ons + maintenance hours × hourly value + expected incident cost
You do not need perfect accounting. Even rough numbers prevent the common mistake of comparing a €20 cloud plan with a $5 VPS and declaring a 75% saving.
Example: solo builder
Suppose a technical solo builder spends $8/month on infrastructure and 45 minutes/month on updates/checks. If they value their technical time at $30/hour, maintenance adds $22.50. The effective cost is already $30.50 before incidents. That does not mean self-hosting is wrong: local control, privacy, customization or higher usage may justify it. It means the economic argument needs to include labor.
The example is illustrative, not a recommendation for any specific host or tool.
When self-hosting wins
- You already operate reliable infrastructure.
- Usage-based cloud pricing would be much higher than the incremental server cost.
- Data residency or control is important.
- You need custom integrations or code close to internal systems.
- You can tolerate and recover from downtime.
- The software license actually permits your intended use.
When managed cloud wins
- The workflow directly generates revenue and downtime is expensive.
- You want someone else to own upgrades and availability.
- Your usage is still small.
- You are building the business process, not an infrastructure skill project.
- The product's cloud tier includes collaboration, history, security or support features you would otherwise rebuild.
License cost is separate from infrastructure cost
Self-hostable products use different licenses. Activepieces currently describes its core as MIT licensed, with commercial enterprise components separated. n8n offers a Community Edition under its Sustainable Use License and documents cases where customer-facing hosting or embedding can require commercial licensing. “I can run the Docker image” is not the same question as “my commercial deployment is covered.”
Design for portability
The safest architecture treats the automation platform as an orchestrator rather than the owner of business logic. Keep important scoring rules, prompts, templates, identifiers and attribution data in versioned files or a database you control. Wrap provider-specific calls behind small interfaces.
If a cloud plan becomes expensive, you can move. If self-hosting becomes operationally annoying, you can move back.
Do a 30-day comparison
Before migrating a working workflow, record one month of actual activity:
| Metric | Managed | Self-host estimate |
|---|---|---|
| Executions/month | Actual | Same workload |
| Subscription | Actual | License if applicable |
| Infrastructure | Included or separate | Estimated |
| Maintenance hours | Actual admin time | Estimate conservatively |
| Downtime/retries | Actual | Expected |
| Security/backups | Vendor responsibility mix | Your responsibility mix |
Bottom line
Self-hosting is strongest when it buys something you deliberately value—control, privacy, scale economics or customization. If the only argument is “the software is free,” calculate the labor first.