Journal

Why we build automation on n8n

People ask what we build on. For most of the automation work we do for other businesses, the honest answer is a piece of software called n8n, running on a server we control. It's worth explaining why, because the choice says something about how we think a business's plumbing should be owned.

What n8n is

n8n is a workflow automation tool, the category Zapier and Make also live in. You wire together triggers and steps: when a payment lands, create the invoice, send the confirmation, update the sheet, reconcile at day's end. The difference is where it runs and who holds it. Zapier and Make are services you rent; your workflows live on their infrastructure, and you pay per task as you grow. n8n is software you can host yourself. We run it on our own server, which changes the economics and the control in ways that matter once a business is doing real volume.

It's "fair-code": source-available, free to self-host, with a commercial cloud option if you'd rather not run it. We mention that only so it's clear this isn't a locked box; it's a tool we can inspect, extend, and stand behind.

Why it wins for the work we do

The data stays where we put it. When a workflow runs on our own server, your invoices, receipts and customer records aren't passing through a third party's platform to get processed. For a business that cares about POPIA, data residency, or just being able to say precisely where its numbers live, that's the whole game. We can point at the server and tell you what's on it.

The cost is predictable. Rented automation platforms bill per task, per operation, per run. That's fine at ten workflows a day and painful at ten thousand, because the bill scales with your success, right when you'd least like a surprise. Self-hosted, the cost is the server, roughly flat whether a workflow fires a hundred times a day or a hundred thousand. A business automating high-volume admin, exactly our sweet spot, comes out ahead, often by a lot.

It bends to the job. The rented tools are great until you hit the thing they don't support, and then you're stuck. n8n has a proper escape hatch: when a workflow needs real logic (a custom step, an odd integration, a South African bank or accounting quirk the mainstream tools ignore) we can write it, right inside the workflow, instead of telling you it can't be done. Most of the value in a real automation lives in those awkward edges, and this is where the well-marketed alternatives quietly give up.

It connects to what you already run. Hundreds of built-in integrations (Google Workspace, the messaging channels, the databases) plus the ability to talk to anything with an API, including Xero and Sage. And an AI step for the parts where reading or writing language is the job, sitting inside the same workflow as everything else.

Where it isn't the answer

We try to be honest about tools, so: n8n is not always right.

  • If you need one or two simple automations and never plan to touch them again, a rented tool you set up yourself in an afternoon may be the sensible call. Running your own server has a floor of effort that isn't worth it for a hobby-sized job.
  • It's a tool, not a product. On its own it does nothing. It needs someone who knows how to design the workflow, handle the failures, and keep it running. Handed to a business with nobody to look after it, it becomes shelfware. (This is part of why we operate what we build, rather than handing over a workflow and disappearing.)
  • The really heavy, high-throughput or hard-real-time jobs sometimes want purpose-built software instead. n8n is superb glue; it isn't every structure.

Why we're telling you what's under the bonnet

Plenty of agencies won't say what they build on, because it keeps you dependent. We'd rather you knew. The workflows we build for you run on an open tool, on infrastructure whose contents we can name, with the awkward, business-specific logic written where you can see it does what it should.

That's the same standard we hold our own products to. If you've got an admin process worth automating and you'd like it built on plumbing you can actually understand and own, that's the conversation to have.