The True Cost of Self-Hosting Automation for Client Work

The most expensive line item in self-hosted automation is the one that says $0. Tools like n8n and Activepieces are free to license and genuinely great, which is why so many agencies start there. Then they spend a Saturday on a failed upgrade, another on a database restore, and slowly realize the real self-hosted automation cost was never the software. It was them.

This isn’t an argument against self-hosting, which is the right call for plenty of teams. It’s a way to actually price it, because the license fee tells you almost nothing about what running automation for a book of clients costs. Here’s how to calculate the real total cost of ownership, line by line, so you can compare it honestly against a managed plan.

What the free license doesn’t include

A free license covers the software and nothing else. Everything required to run that software reliably for clients is on you, and each item is real time or real money every month.

• The server. A production instance, the database behind it, and a job queue, sized for real load, not a free tier.
• Upgrades. New versions land regularly, and some ship bugs, so you test and roll forward carefully rather than blindly.
• Backups and restores. Backing up is easy to set up and easy to forget to test until the day you need a restore.
• Security patching. The platform, its dependencies, and the operating system underneath all need timely patches.
• Certificates and reachability. TLS renewal, a public URL that stays reachable for webhooks, and the monitoring to know when it isn’t.
• On-call. When a client’s workflow stops at 2am, someone answers, and that someone is you.

The multiplier nobody prices in: per-client sprawl

The line items above are per instance, and here’s where it compounds. When real client isolation means running a separate instance per client, which is the recommended pattern on n8n, every item on that list multiplies by your client count.

Three clients is three of everything, which is manageable. Thirty clients is a fleet: thirty deployments to upgrade, thirty databases to back up, thirty things that can page you. I walked through why isolation pushes you toward that fleet in the n8n multi-tenancy comparison. The point for costing is that self-hosting rarely scales as one instance. It scales as many.

Put a number on it

Here’s the formula. Monthly TCO is your operations hours times your hourly rate, plus infrastructure, plus the cost of the risk you’re carrying. The infrastructure line is the small one. The hours line is where it lives.

Say a modest portfolio takes five to ten hours a month of upgrades, backups, patching, and the occasional incident. At an agency owner’s rate of $100 an hour, that’s $500 to $1,000 a month in your own time, before a dollar of server cost, and before the client-count multiplier kicks in. The infrastructure might be $50 to a few hundred. The time is the number that should scare you, because it’s the time you’re not spending on client work you could bill.

Where a managed platform moves the cost

A managed platform doesn’t make those costs disappear, it moves them off your plate and onto a fixed line item. You trade upgrades, backups, patching, on-call, and per-client sprawl for a monthly plan, and the vendor absorbs the operations. On TaskJuice that plan is priced by compute time, so you pay for the work your clients’ workflows actually do rather than for the privilege of keeping a fleet alive.

The honest comparison isn’t license fee versus plan price. It’s license-plus-your-hours versus plan price. Once you count the hours, a managed plan often comes out ahead for an agency, and the hours you get back are billable. The Activepieces version of this tradeoff is in the Activepieces comparison, and the n8n cost detail is in the real cost of white-labeling n8n.

The honest case for staying self-hosted

Self-hosting genuinely wins in real situations, and I’m not going to pretend otherwise. If you already have in-house DevOps, the marginal hours are low and the control is worth a lot. If you need data to live on infrastructure you own, self-hosting is the answer. If you value open source and no vendor lock-in, a fair-code or MIT engine gives you the source and the freedom. And for a single team automating its own work rather than a portfolio of clients, the operational load stays small enough that free really is close to free.

The calculation flips specifically when you’re reselling to many clients and your time is the scarce resource. That’s the case where the hours multiply and the managed math wins.

Run your own numbers

Estimate honestly. Count the hours you’d spend per month per instance on upgrades, backups, patching, and incidents. Multiply by your real hourly rate. Multiply again by how many client instances your isolation model requires. Add infrastructure. Then compare that total, not the license fee, against a managed plan. If the managed number is lower, the free software was costing you money.

Frequently asked questions

Is self-hosting n8n or Activepieces really free?

The license is free, and for a single team the total cost can be low. But running it for clients means paying in operations: a server, upgrades, backups, patching, and on-call. The software is free; operating it reliably is not.

How much does it cost to self-host automation for clients?

Mostly your time. A modest portfolio can take five to ten hours a month of maintenance, which at typical agency rates is $500 to $1,000 in labor before infrastructure, and it multiplies if your isolation model needs a separate instance per client.

What are the hidden costs of self-hosting automation?

Upgrades and the occasional bad release, database backups and restores, security patching across the stack, TLS and webhook reachability, monitoring, secret management, and on-call time. Per-client instance sprawl multiplies all of them.

When is a managed automation platform cheaper than self-hosting?

When you’re serving many clients and your time is billable. Once you count operations hours at your real rate and multiply by client instances, a managed compute-time plan often beats license-plus-labor, and it returns the hours to client work.

Free software is a real gift, and self-hosting is a legitimate choice with its eyes open. The mistake is comparing a $0 license to a monthly plan and calling it a decision. The right comparison counts your hours, your on-call, and your client-count multiplier, and for an agency reselling automation, that total is usually where the surprise lives. TaskJuice trades all of it for a compute-time plan and your evenings back. TaskJuice is opening access to founding agencies now. Join the early-access list and run the numbers for your own book.