Is n8n right for us, or should we write custom software instead?

It depends on the process. n8n works well when you are connecting off-the-shelf systems that have an integration interface and the process can be described as a sequence of steps. When a process is very specific or needs its own interface for people to use, it is more honest to write the software directly. We say which path fits after looking at the process, not before.

The tool itself is open source and you do not pay a license fee to use it. You pay for our work building the flows and for the server n8n runs on, usually a small one, since n8n does not need much power for typical flows.

Who can run the flows after the implementation?

You or your team, if you have someone technical, we hand over full access and show you how to read and adjust a flow. If you would rather we kept an eye on changes, you can take a care plan from 490 zł a month. We settle which route before the start.

Can n8n handle large amounts of data?

For typical office automations, a few hundred to a few thousand events a day, yes, without issue. For genuinely large volumes we look at the architecture separately on a call, because at that point what matters is also how the systems on the other end of the connection behave, not just n8n itself.

What happens to the flows if we stop working together?

They stay with you, because they run on your own server and you have full access from day one. We do not lock or remotely switch off anything once the engagement ends, that is one of the promises we keep regardless of how long a project ran.

Who deploys n8n on a company's own server rather than in the cloud?

Three kinds of vendor offer n8n today: hosting companies, where you get a ready installation but build the workflows yourself; individual automation specialists; and firms that do both, installing the tool and writing the workflows around the client's processes. SEVENEDGE does the latter: installation, workflows, backups and handing day-to-day operation over to the client's team.

What if we don't have our own server?

We advise the simplest option that is enough to start, without overpaying for capacity you don't need. For typical workflows n8n doesn't need a large machine. The server stays yours, along with the access and the data.

Should we do it ourselves or have it done?

Honestly: if someone in the company enjoys tinkering with this and the process is single and simple, you will do it yourselves and there is nothing wrong with that. Having it done makes sense when the flow touches money or customer data, when it has to run without your attention, and when someone has to fix it on the day it breaks. Which way we recommend, we say after looking at the process, not before.

n8n implementation, on your own server

n8n is the engine we build most of our automations on. We install it on your own hardware, not a vendor's cloud, and before we leave the project we teach you how to run it. This page answers WHO SETS IT UP AND HOW. What happens when a finished flow breaks is a separate topic, covered under n8n maintenance.

Book a free call

Free, about 30 minutes, no strings attached. After the call you get a fixed price in writing.

Open-source, hosted with youFirst flow in 1 to 3 weeksNo license fee for n8n itselfAccess and edit rights from day one

In short

Who this is for: For a company that wants its automations on its own server rather than in someone else's cloud: a factory, a hotel, an office or a service business where people re-type the same data between programs every day.
What we actually do: We install n8n on the client's server, build workflows around their processes, set up backups and train their team to run it before we step away. The workflows, the data and the run history stay with the client.
What it takes off your plate: Manual re-typing of orders, invoices, tickets and spreadsheets between programs that do not talk to each other, plus the work that has to happen at a fixed time and that someone regularly forgets.
Where our n8n experience comes from: We publish our own workflows as a creator in the official n8n library, and we document our deployments together with the n8n version, the verification date and a separate section on what a given workflow does not do.

What n8n is

n8n is an open-source tool for building automations: it connects programs into flows, where an event in one system triggers an action in another, without writing an integration from scratch every time. We install it on your server and build flows shaped around your processes, not off-the-shelf templates.

We pick n8n over writing every automation from scratch because a connection to a popular system, email, a spreadsheet, a sales platform, is usually already built and tested, and every flow reads as a diagram of blocks rather than a wall of code. When a process is unusual enough that the ready-made blocks fall short, we add a custom piece or write the software directly, and we decide which after looking at the process, not before.

Because n8n runs on your own server, the flows, the data and the run history stay with you. Nobody outside has access to them beyond you and us during the build, and once it's live you can revoke our access.

How an implementation works

An n8n implementation starts with picking the first process, not installing the tool. Installation is a day's work; the rest of the time goes into a flow that actually takes something real off people's plates.

1We pick the first process and the systems to connectOn the free call we look at what you run today and what currently moves between systems by hand. We pick the process with the best ratio of hours recovered to how hard the connection is.
2We install n8n on your serverInstallation, access, backups. If you do not have your own server, we recommend the simplest option that covers the start without paying for capacity you do not need.
3We build the first flow and run it in parallelFor a few days the flow runs alongside the manual work and results get compared. Nobody stops doing it by hand until the flow gets it right zero times wrong in a row over an agreed stretch.
4We teach you to read and adjust flowsWe hand over admin access and walk through what a flow looks like from the inside, so a small change, a new email address, a changed file format, can be made without waiting on us.

Why your own server and not the n8n cloud

n8n can be bought as a cloud service, and at the start that is simpler: an account, a card, done. We do not go that way, and there is one reason for it, but a concrete one.

n8n stores an execution history, and an execution history is not metadata. It holds the content of what went through the flow: order lines, the text of a customer's email, a contractor's tax number, sometimes an attachment. When the flow sits in a vendor's cloud, that content sits there too, and with it the decision of how long it stays.

On your own server it stays with you. You set the retention yourself, you export it yourself, you delete it yourself. Under a data processing agreement that is the difference between naming who you entrust data to and entrusting it to nobody.

What we do not promise, to be straight about it: your own server is neither free nor maintenance-free. Someone has to patch it and watch the backups. If you would rather not do that yourselves, we do it under a care plan — and if you want neither, a vendor's cloud is a more honest choice for you than a server nobody ever looks at.

What this looks like in practice

Example (hypothetical)

A fifteen-person spare-parts wholesaler gets orders by email from a dozen regular customers, each writing them differently. Today one person reads the email, retypes the line items into the sales system and sends back a confirmation, usually the first hour of every working day.

The first n8n flow reads the email content, pulls out the order lines and drops them into the sales system as a draft that a person only approves. The confirmation to the customer goes out automatically once approved. The person who used to retype orders now starts the day checking finished drafts instead of reading every email from scratch.

How long an implementation takes

1 to 3 weeks for the first flow

Shorter when the systems being connected already have an integration interface. Longer when documents with a varying layout need to be read and the flow has to learn from your examples. Later flows usually go faster, since the install and access are already in place.

Questions about an n8n implementation

Is n8n right for us, or should we write custom software instead?: It depends on the process. n8n works well when you are connecting off-the-shelf systems that have an integration interface and the process can be described as a sequence of steps. When a process is very specific or needs its own interface for people to use, it is more honest to write the software directly. We say which path fits after looking at the process, not before.
Is n8n free?: The tool itself is open source and you do not pay a license fee to use it. You pay for our work building the flows and for the server n8n runs on, usually a small one, since n8n does not need much power for typical flows.
Who can run the flows after the implementation?: You or your team, if you have someone technical, we hand over full access and show you how to read and adjust a flow. If you would rather we kept an eye on changes, you can take a care plan from 490 zł a month. We settle which route before the start.
Can n8n handle large amounts of data?: For typical office automations, a few hundred to a few thousand events a day, yes, without issue. For genuinely large volumes we look at the architecture separately on a call, because at that point what matters is also how the systems on the other end of the connection behave, not just n8n itself.
What happens to the flows if we stop working together?: They stay with you, because they run on your own server and you have full access from day one. We do not lock or remotely switch off anything once the engagement ends, that is one of the promises we keep regardless of how long a project ran.
Who deploys n8n on a company's own server rather than in the cloud?: Three kinds of vendor offer n8n today: hosting companies, where you get a ready installation but build the workflows yourself; individual automation specialists; and firms that do both, installing the tool and writing the workflows around the client's processes. SEVENEDGE does the latter: installation, workflows, backups and handing day-to-day operation over to the client's team.
What if we don't have our own server?: We advise the simplest option that is enough to start, without overpaying for capacity you don't need. For typical workflows n8n doesn't need a large machine. The server stays yours, along with the access and the data.
Should we do it ourselves or have it done?: Honestly: if someone in the company enjoys tinkering with this and the process is single and simple, you will do it yourselves and there is nothing wrong with that. Having it done makes sense when the flow touches money or customer data, when it has to run without your attention, and when someone has to fix it on the day it breaks. Which way we recommend, we say after looking at the process, not before.

Tell us what still gets retyped by hand

The call takes about 30 minutes, costs nothing and commits you to nothing. After it you know what makes sense, how long it takes and what fixed price you get in writing.

Work out what the manual work costs you Book a free call

We did the same at the REJMAN precast plant in Sanok and at Dwór Kombornia Hotel & SPA — the signed reference letters are there to download. See client references