n8n implementation, when n8n is the honest answer
Sometimes the right answer is a workflow engine you own, not a custom build. When that is true we say so, build it there, and charge less. n8n work is scoped and priced inside an automation engagement, from the published prices on the AI automation services page.
When n8n is the right tool
You have technical staff, you want to own the runtime, and you need Canadian hosting cheaply. n8n is a workflow engine you run yourself, which means the data path and the upgrade schedule are yours rather than a vendor's. For a linear chain of API calls with no real judgement in it, a workflow tool will do the job for a subscription fee and you should buy one. We will tell you that if it is true, even though it costs us the engagement.
When it is a liability instead
If nobody in-house will maintain it, do not buy it. An unmaintained workflow engine is a liability: it keeps running long after the person who understood it has left, and it fails quietly. That is the single question we ask before recommending n8n to anyone.
The other limit is judgement. Workflow tools stop at reading a document, deciding what it means and handling the exception. When that is the actual work, you want intelligent document processing or AI agents for business instead, and the comparison is set out in Zapier alternatives.
Your own staff, from our handover
The person who scopes your engagement is the person who writes the workflows, then hands them over with the credentials in your own store and a runbook, so your own technical staff can run them. We do not hold an n8n partner status and do not claim one. What you get is the same handover as any other engagement: the workflows, the credentials in your own store, a runbook, and no runtime licence to buy from us.
What a production n8n deployment needs
A workflow that runs on someone’s laptop is a demo. These are the parts that keep one running after the person who built it has moved on — all of them in your tenancy, all of them in the handover.
The workflows, the credentials in your own store and a runbook are yours. There is no runtime licence to buy from us.
Runs in your tenancy
n8n self-hosted in your own cloud account or on your own hardware, in the region you choose, with its database and its encryption key under your control. The data path is yours, and so is the upgrade schedule.
Credentials in your own store
Each connection gets its own credential with the narrowest access that system allows, held in your environment rather than ours — so revoking one does not break the others.
Workflows kept as files
Every workflow exported and kept under version control, so a change can be reviewed, compared and rolled back instead of edited live in the browser.
Failures that reach a person
An error workflow behind every production flow: a retry where retrying is safe, and a named person alerted where it is not. A workflow engine’s worst failure is the quiet one.
A history you can read
Executions kept long enough to answer “what happened to this one on the 14th”, and pruned on a schedule so the database does not grow without limit.
A runbook for whoever comes next
How to restart it, restore it from a backup and upgrade it, written for the person who maintains it after handover rather than for the person who built it.
n8n, a hosted tool, or custom code
Three honest options for the same job. The cheapest one that does the work is the right one.
| Option | Who runs it | Where your data goes | Good at | Stops at |
|---|---|---|---|---|
| Zapier or Make | The vendor | The vendor’s cloud | Simple triggers between SaaS apps, at low volume | Reasoning over documents; per-task pricing at volume |
| n8n, self-hosted | Your own technical staff | Your tenancy, in the region you choose | Owning the runtime and the data path, with logic your staff can read | Judgement work — and any team with nobody to maintain it |
| Custom code: an agent or a document pipeline | You, from the handed-over source | Where you choose, named in the contract | Reading a document, deciding what it means and handling the exception, measured against an evaluation set | A linear chain a subscription tool already does |
Two things we will not state until they are settled
A separate price. This site publishes a price for everything it sells, and there is no separate n8n price to publish yet. n8n work is scoped and priced as part of an automation engagement, from the published figures on the AI automation services page. Ask on the first call and you will get a number before you commit to anything.
Hosting it for you. We will build and hand over an n8n deployment that runs in your tenancy. We are not offering to host it on your behalf, because that depends on n8n's own licence terms and we have not verified them for that use.
Questions worth asking first
Will you tell me if n8n is wrong for us?
Yes, and we would rather do it on the first call. If a workflow tool does the job for a subscription fee, you should buy one. If nobody in-house will maintain it, do not buy it at all.
Do you host n8n for clients?
Not today. We will build a deployment that runs in your own tenancy and hand it over. Hosting it on your behalf depends on n8n’s licence terms for that use, which we have not verified, so we do not offer it.
Are you an n8n partner?
No. We hold no partner or certification status with n8n and do not claim one.
What does it cost?
n8n work is scoped and priced inside an automation engagement, from the published prices on the AI automation services page. There is no separate n8n price list on this site yet.
What do we own at the end?
The workflows, credentials held in your own store, and a runbook. There is no runtime licence to buy from us.