AI And Automation
Every tool on my stack page is a noun. The automation layer is the verb, and it is the only part a competitor cannot buy off the shelf.
n8n is an open source workflow automation tool that can run on your own server. Self hosting means the workflows, the credentials and the execution history all sit on infrastructure you control, with no per task pricing. For anyone moving real volume between tools, that converts automation from a metered cost into a fixed one.
Anyone can buy the same forty four tools. Nobody can buy the wiring between them.
That is the whole argument. My stack is public, it is all on the uses page, and there is nothing proprietary about any single item on it. What took years is the connective tissue.
What changes when you self host n8n?
Two things. The pricing model and data custody.
Hosted automation platforms bill per task or per operation. That is fine at low volume and it becomes actively hostile at high volume, because the moment automation starts working you get punished for it. A workflow that fires on every booking, every form fill and every payment is a workflow whose cost scales with your success.
Self hosted n8n runs on a server you pay for monthly regardless of how many executions cross it. The marginal cost of the ten thousandth run is zero. That changes what you are willing to automate at all, and the second order effect matters more than the line item ever did.
Data custody is the other half. Credentials for Stripe, Supabase, the property stack and the mail provider end up concentrated in one place. Self hosting means that place is mine.
What actually runs through it?
n8n is the layer between the other tools. Concretely, it is what moves a record from one system into another without a human retyping it.
A form submission becomes a client record. A Stripe event becomes an internal notification and a status change. A property event out of the channel manager becomes a task with an owner and a date. None of these are clever. All of them used to be somebody’s afternoon.
The test for whether something belongs in n8n is not complexity. It is repetition plus a clear trigger. If it happens on a schedule or in response to an event, and a person is doing it identically every time, it goes in.
Automate the handoff. Keep the judgment.
When is managed hosting the right call?
When nobody will patch the server. That is the entire test.
n8n offers a cloud version and it is a legitimate choice. Self hosting is not free, it is priced differently: you pay in attention rather than per task. Version upgrades, backups, and the queue configuration that stops long running workflows blocking each other all become yours.
If no one on the team will own that, managed hosting is cheaper than the outage. Run the version you will actually maintain.
What breaks?
Upgrades. n8n moves quickly, and a workflow built against an older node version can behave differently after a major release. The mitigation is boring and it works: pin the version, read the release notes before moving, and keep a staging instance for anything that touches money.
The second failure is silent. A workflow that errors without telling anybody is worse than no workflow, because the process now looks handled. Every production workflow needs an error branch that reaches a human. Not a log file. A human.
The third is credential sprawl. Self hosting concentrates every key into one instance, which is the benefit and the risk in the same sentence. That instance gets treated like production, because it is production.
A silent automation is not a system. It is an assumption running on a schedule.
Common questions
Is n8n free if you self host it?
The community edition is source available under a fair-code licence and carries no licence fee to run yourself. You pay for the server it sits on. Commercial restrictions apply if you resell it as a hosted service, so read the current licence before building a product on top of it.
Is self hosted n8n better than Zapier?
At high volume it is cheaper and more flexible, because the pricing is not per task. At low volume with nobody technical to own the server, Zapier is easier and the difference does not matter.
What does it cost to self host n8n?
The server plus your maintenance time. A modest instance runs comfortably on a small VPS. Verify current provider pricing, and budget the maintenance honestly instead of treating it as free.
What are the risks of self hosting n8n?
You own upgrades, backups and security. Every credential the workflows use is concentrated in one instance, so it has to be treated as production infrastructure rather than a side tool.
What should you automate first?
The task with the highest repetition and the clearest trigger, not the most complicated one. If it happens on a schedule or in response to an event and a human does it identically every time, it goes in first.
Buy the tools. Build the wiring. Only one of those is ever yours.
