Platform · Automation

An n8n agency for workflows and AI agents that survive production.

Anyone can connect two nodes. The workflows worth hiring an n8n agency for run thousands of times a week against real orders and real customers. We build n8n the way software is built: self-hosted, version-controlled, tested, monitored, with a person's approval where the stakes are high.

4.6 from 18 Google reviewsShipping since 2016

  • One workflow, scoped, built and deployed$5,900
  • A production AI agent orchestrated in n8nFrom $7,500
  • Several workflows or a migration from Zapier or Make$2,900–$5,900per engineer, per month
The short answer

What an n8n agency does, and what Gigabit does with n8n.

Gigabit is an n8n agency. We self-host n8n in your own cloud, build workflows across commerce, CRM, ERP and messaging systems, build AI agents on n8n's AI Agent node with human review on risky tool calls, and move Zapier and Make estates to n8n. One workflow is $5,900 fixed and live in three weeks.

n8n has changed under many older builds. Since n8n 2, saving keeps a draft and Publish puts a workflow live; an AI Agent's tool calls can wait for a person to approve them in Slack or Teams; and instance-level MCP lets an outside AI client run, and from n8n 2.13 build and edit, the workflows you enable.

For a $28M multi-channel electronics seller, five automations on self-hosted n8n with custom Python and GPT-4o-mini cut manual operations work from 32 hours a week to 4.5, and process 85% of returns without a person touching them.

What we build

The n8n work we take on.

The difference between a demo and a system is everything that happens when a step fails, drawn here as the n8n screens it happens in.

Self-hosted set-up

n8n in your own cloud account in queue mode, with Postgres, workers, a backed-up encryption key, staged upgrades, access control and telemetry switched off, so workflow data stays on infrastructure you own.

Workflow builds

Order, returns, inventory, reporting and vendor workflows across the systems you run, with retries, idempotency keys, an error output on every risky node and a dead-letter table for what cannot be processed.

AI agent workflows

Agents on n8n's AI Agent node with a deliberately small set of tools, grounded in your data, tested against real past cases, and with human review on any tool that moves money or stock.

Custom nodes and code

Custom nodes for systems that have none, Python or JavaScript in the Code node, and separate tested services for logic too complex to live in a canvas.

Migration from Zapier and Make

Six steps: inventory what runs, rank it by cost and risk, rebuild what is worth keeping in n8n, run old and new side by side, switch the triggers over one workflow at a time, then turn the old ones off.

Monitoring and takeover

Insights, execution logs and failure alerts from an error workflow, and rescue of brittle workflows someone else built. We measure the real failure rate before we change anything.

AI on n8n

n8n makes an agent easy to draw. Making it reliable is the work.

The canvas hides how many ways an agent step can go wrong.

What the platform ships

Built into the platform

n8n treats AI agents as a first-class building block, and has added ways to keep a person in the loop and to let outside AI clients in.

  • An AI Agent node that calls the tools you connect to it, with memory and a choice of model; on n8n Cloud, models can be used without your own API keys.
  • Human review on chosen tools: the workflow pauses and asks a person in Slack, Teams, email or n8n Chat to approve or deny the call.
  • MCP both ways: an MCP Server Trigger exposes one workflow's tools, and instance-level MCP lets clients such as Claude Desktop search and run the workflows you enable, and from n8n 2.13 build and edit them.
  • Evaluations, to test an AI workflow against a dataset before and after a change.
What we add

What turns a workflow into a system

In the $28M electronics seller's build, the order-exception router deliberately keeps a human approval in the loop. Knowing where to do that is most of the skill.

  • An evaluation set of real past cases that every agent step must pass before and after each change, with a release gate.
  • Human review on every tool that moves money or stock, and autonomy only where a mistake is cheap to undo.
  • Structured outputs and validation between steps, so one odd model reply cannot corrupt a record.
  • MCP access enabled only for the workflows an outside AI client needs, never for ones that move money or delete data.
How it is priced

Published prices, mapped to the job.

The same figures as the pricing page. Nothing on this platform is quoted from a separate rate card.

AI Quick Win Sprint

$5,900fixed · 3 weeks

One workflow, scoped, built and deployedWith up to three tool integrations and error handling.

Gigabit Agents

From $7,500flat, per agent

A production AI agent orchestrated in n8n

Embedded AI Teams

$2,900–$5,900per engineer, per month

Several workflows or a migration from Zapier or Make

The jobHow we deliver itPrice
One workflow, scoped, built and deployedWith up to three tool integrations and error handling.AI Quick Win Sprint$5,900 fixed · 3 weeks
A production AI agent orchestrated in n8nGigabit AgentsFrom $7,500 · flat, per agent
Several workflows or a migration from Zapier or MakeEmbedded AI Teams$2,900–$5,900 / engineer / mo
Monitoring, upgrades and fixes after launchManaged AI OperationsFrom $1,290/mo
Ranking which workflows to automate firstAI Transformation Sprint$9,900 fixed · 2 weeks

A price marked “from” buys the base scope set out on the pricing page. Anything larger is quoted as a fixed price before work starts. Work with no natural end, such as ongoing development, is priced per engineer per month with no lock-in.

n8n, plainly

Self-hosted, n8n Cloud or something else: the facts that decide it.

Prices and plan features as n8n publishes them, re-checked on 15 November 2026; license terms checked on 23 October and hosting and data-protection facts on 10 November 2026. n8n shows dollars or euros depending on where you view the page. They change, so check the linked pages before you budget.

What n8n itself costs

n8n bills per workflow execution, however many steps the workflow has; n8n's page says annual billing saves 17% against monthly. On a self-hosted install the server, database and model API costs come on top; our build and run fees come on top of either option.

OptionPaid to n8nRuns onWhat decides it
Community editionFreeYour serverAlmost the full feature set, queue mode included. No SSO, Git version control, environments, external secrets, external binary storage, log streaming, multi-main mode or shared projects.
n8n Cloud Starter$20/mo (€20) billed annually, 2,500 executionsn8n's cloud5 concurrent executions and one shared project, with agents, MCP and AI nodes. A first workflow, not a production estate.
n8n Cloud Pro$50/mo (€50) billed annually, 10,000 executionsn8n's cloudUp to 50 concurrent executions, three shared projects, workflow history and admin roles.
Business$800/mo on the US page (€667 on the euro page) billed annually, 40,000 executionsYour server onlyAdds SSO and LDAP, multiple environments and Git version control. Self-hosted only; n8n pitches it at companies under 100 employees.
EnterpriseQuoted by n8nYour server or n8n's cloudExternal secret stores, log streaming, audit logging and support with an SLA.

What the license lets you do

n8n is fair-code, not open source. The self-hosted Community edition is free under n8n's Sustainable Use License, which allows use for your own internal business purposes. n8n's license FAQ spells out the practical line.

Allowed: running it to help run your business, having an agency build and maintain workflows on your instance and charging you for it, and using n8n behind the scenes in your own product, where users trigger automations you built. Not allowed without a commercial license: hosting n8n as a service where your clients build their own workflows, letting outside users configure workflows through your product, white-labeling it, or using the enterprise features that ask for a license key.

That is why we build on your instance, under your license. The workflows are yours, and so is the relationship with n8n.

n8n, Zapier, Make or code

ChooseWhen
ZapierA handful of simple connections, owned by non-technical staff, where the widest catalog of app integrations matters most.
MakeBranching and data transformation at moderate volume, run by a technical operator who is happy with a hosted tool.
n8n CloudYou want n8n's AI and code features without running a server, and volume fits the plan.
Self-hosted n8nData must stay on your infrastructure, volume makes per-task pricing expensive, or you need custom nodes, and someone will own the server.
Custom codeHeavy computation, strict real-time processing, or logic that has outgrown a canvas. Often alongside n8n, not instead of it.

Running self-hosted n8n in production

Scaling is queue mode: one main instance receives triggers and separate worker instances run the executions, and you add workers as volume grows. The free Community edition includes it.

One catch the documentation states plainly: in queue mode n8n cannot keep binary data on the local filesystem, so workflows that handle files need S3 external storage, which is a feature of the paid self-hosted plans. Decide that before you design file-heavy workflows, not after.

Since n8n 2, Publish has replaced the Active toggle: saving keeps a draft, and production runs the published version until you publish again. Sub-workflows and the error workflow need publishing too, or the parent keeps calling the old version.

The rest is ordinary operations work that a demo skips: Postgres rather than the default SQLite, a backed-up encryption key for stored credentials, pruning of execution data, an error workflow that alerts a person, and upgrades tested on a copy before they reach production.

EU hosting: what you can choose

n8n is made by n8n GmbH, based in Berlin. Where your workflow data sits depends on the option: on n8n Cloud, n8n runs the instance; self-hosted, everything stays in your own cloud account, with the provider and in the region you choose. We set n8n up there and work inside that environment.

According to n8n, n8n Cloud runs on Microsoft Azure in the EU, and its pricing page names servers in Frankfurt. For Cloud, n8n is a processor; its data processing agreement includes the standard contractual clauses, and its sub-processor list is public. For self-hosted n8n, n8n says it is neither controller nor processor, because it does not receive your data.

Two points no demo shows. First, even self-hosted n8n sends usage data (telemetry) to n8n by default, though not the data in your workflows or your credentials. Self-hosted, an environment variable turns it off; on n8n Cloud, according to n8n, it cannot be turned off. Second, the AI assistant in the n8n Cloud editor is on by default and sends context about the open workflow to model providers that n8n lists as US-based sub-processors. Your own AI steps send their input to the provider you choose there.

OptionWhere the data sitsWho you contract with for the data
n8n CloudMicrosoft Azure in the EU; servers in Frankfurt per n8n's pricing page. Backups in a second region in the same country, per n8n.n8n GmbH, Berlin: data processing agreement with standard contractual clauses.
Self-hosted on HetznerFalkenstein or Nuremberg (Germany), Helsinki (Finland). n8n publishes its own Hetzner guide.Your contract with Hetzner. n8n receives no workflow data.
Self-hosted on AWSFor example Frankfurt (eu-central-1), Paris (eu-west-3), Ireland or Stockholm.Your contract with AWS. n8n receives no workflow data.
Self-hosted on OVHcloudFor example Paris, Gravelines, Roubaix or Strasbourg (France), Limburg (Germany).Your contract with OVHcloud. n8n receives no workflow data.

GDPR and where the data sits

No tool is GDPR-compliant on its own; the deployment decides it. Self-hosted n8n keeps workflows, credentials and execution data in your own database. Personal data sent to our US entity or our engineers in Bangladesh would be a third-country transfer under GDPR, so by default we deploy it in your cloud account in an EU region and work inside that environment, so personal data is not transferred to us. You remain the controller and we act as processor under a data processing agreement. Where a transfer cannot be designed out, the standard contractual clauses your counsel chooses are signed before it happens.

Model calls are the part people forget: an AI step sends its input to the model provider you choose, so pick the provider and region with that in mind.

When n8n is the right call, and when it is not.

Choose it when

  • You want automation on your own infrastructure, with data that does not pass through a third party.
  • Volume is high enough that per-task pricing elsewhere has become a real cost.
  • Someone technical, yours or ours, will own the instance.

Look elsewhere when

  • Nobody will look after a server. Use n8n's hosted plan, or stay on Zapier.
  • The job is one simple app-to-app sync. A native integration is less to maintain.
  • The core of the work is heavy computation or strict real-time processing. Write that as a service.
Proof · self-hosted n8n

Manual Ops Cut from 32 to 4.5 Hours a Week: AI Workflow Automation for a Multi-Channel E-Commerce Operation

Five automations across Shopify Plus, Amazon, Walmart and wholesale, orchestrated in self-hosted n8n with custom Python for the complex logic and a human approval kept on order exceptions.

Multi-channel e-commerce brand, $28M annual revenue, 65 employees

Five n8n + GPT-4o-mini automations cut a 4-channel ops team's manual workload from 32 to 4.5 hours/week — ~$87K in year-one impact.

32 → 4.5 (−86%)
Weekly manual hours
85%
Returns processed autonomously
94.2% → 99.1%
Inventory accuracy

Investment: $74,000 (Year 1 total; $44,000 build) · Timeline: 8 weeks (1-week assessment + 7-week build)

Read the case study

How it runs, and what you receive.

  1. 01

    Scope

    One call, then a written plan: the workflow, the data it touches, what a first release covers and a fixed price.

  2. 02

    Build

    Short sprints with a demo on staging. Every AI release passes an evaluation set built from your real cases.

  3. 03

    Launch

    Live with a person on the risky steps and an audit log of every action.

  4. 04

    Run

    We monitor, re-run the evaluations and fix, or hand over to your team with docs and runbooks.

What you receive
  • The code, in your repositories
  • The evaluation set and its latest report
  • Architecture notes and a runbook
  • An audit log of every agent action

Questions n8n teams ask.

Something else? Book a call with an engineer.

How much does n8n automation cost with Gigabit?

One workflow, scoped, built and deployed with up to three tool integrations and error handling, is $5,900 fixed over three weeks. A production AI agent is a flat fee from $7,500. Several workflows or a migration are staffed as an embedded pod at $2,900–$5,900 per engineer per month. Running them afterwards is Managed AI Operations from $1,290 a month.

n8n agency, n8n consultant or freelancer: which do we need?

A freelancer or a single n8n consultant suits one workflow, or advice on an instance you already run. An n8n agency suits work that spans several systems, needs more than one engineer, or has to be looked after once it is live. Gigabit quotes each job at a fixed price or rate agreed in writing, so it can be compared line by line with a freelancer's estimate.

Can your n8n experts take over workflows someone else built?

Yes. We start by adding logging and an error workflow that alerts a person, so the real failure rate is visible, then fix the workflows that fail most or matter most: missing retries, duplicate processing, unpublished sub-workflows and agent steps with no validation.

Should we self-host n8n or use n8n Cloud?

Self-host when data control, volume or custom nodes matter and someone will own the server; n8n's Business plan is self-hosted only. Use n8n Cloud when you want no infrastructure to manage and your volumes fit its plans. The workflows are portable between the two, so it is not a permanent decision.

Is n8n free and open source?

n8n is fair-code, not open source in the OSI sense. The self-hosted Community edition is free under n8n's Sustainable Use License for your own internal business use and includes queue mode; you pay for the server and database it runs on. On 15 November 2026 n8n Cloud started at $20 a month billed annually (€20 on n8n's euro page) for 2,500 executions, and the self-hosted Business plan, which adds SSO, environments and Git version control, was $800 a month billed annually (€667). The full breakdown is in our n8n pricing guide.

Can an agency build n8n workflows for us on the free license?

Yes. n8n's license FAQ allows building automations for a client on the client's own instance and charging for setup, building and maintenance, as long as the client's customers cannot create or edit workflows. It does not allow hosting n8n as a service where clients build their own workflows, or white-labeling it. That is why we build on your instance, under your license.

Is n8n GDPR-compliant?

No tool is compliant on its own; the deployment decides it. Self-hosted n8n keeps workflow and execution data in your own database, so by default we deploy it in your cloud account in an EU region and work inside that environment. You stay the controller and we act as processor under a data processing agreement. AI steps still send their input to the model provider you choose, so choose the provider and region accordingly.

Does self-hosted n8n scale?

Yes, through queue mode: a main instance receives triggers and worker instances run the executions, and you add workers as volume grows. The free Community edition includes queue mode. Two catches: in queue mode, workflows that handle files need S3 external storage, and multi-main mode for a second main instance is not in the Community edition; both come with the paid self-hosted plans.

Name the workflow that eats the most hours.

Thirty minutes to scope it. One workflow is $5,900 fixed, live in three weeks.

  • What you run on n8n today, if anything
  • The job, and the systems it touches
  • What a first release covers
  • A fixed price, in writing

Scope your project

A senior engineer replies within one business day.