How we build.

The default

1. Your workflows run on a small computer at your business, a Raspberry Pi or a mini PC depending on the scope, with n8n. The computer sits at your premises and belongs to you; we set up n8n on it and look after it, we do not run an n8n instance of our own for you. Your business data is stored and processed there; by our register that is level 1.

2. If a workflow itself needs an outside service, such as sending email, a cloud storage or an AI, we name provider and level beforehand.

3. We look after the computer remotely over an encrypted connection without a third-party relay. That gives us access to your data; a data processing agreement governs it.For professionals bound by secrecy (tax advisors, lawyers, doctors) a DPA is not enough; a written confidentiality commitment is added (Section 203 StGB, Section 43e BRAO, Section 62a StBerG). More in the frequently asked questions under Data paths →

4. Your backup, as you choose, stays only in-house or goes encrypted to a provider in the EU. Only you hold the key; the provider sees nothing but unreadable data.

All statements according to the providers, as of November 2026, not legal advice. The levels are on the Data paths page. See data paths →

• Default

  Small computer at your business

  For

  Nothing leaves the building. The device belongs to you; access is limited to your business and to us as maintainers under contract. Running cost is electricity. As long as only n8n runs, a Raspberry Pi is enough; with local AI or several services, a mini PC.

  Against

  One device depends on your power and your internet; a small UPS belongs with it. It is reachable from outside only via a forward. Maintenance happens on site or over our remote connection.

  Suits

  Little data going out, high need for protection.

• Alternative

  Your own server at an EU provider

  For

  Fixed address, easily reachable from outside, no device at your premises. The server runs in your name: you are the contract partner, the data processing agreement sits in your account, you pin the location. Running it usually costs around 10 € a month for the server.

  Against

  The provider can technically access the server. Updates and upkeep remain the operator's job; we take that on as a service. No provider is liable for data loss, so a backup of your own, off site, belongs with it.

  Suits

  Workflows with outside contact, such as forms or notifications from other services.

• Alternative

  n8n Cloud

  For

  Quick start, no server of your own, n8n runs and updates it.

  Against

  Your data sits with n8n and its subcontractors; details are in the register under data paths. The n8n AI assistant must stay switched off, otherwise the level goes up.

  Suits

  Low need for protection, quick start.

When automation makes sense

• Your staff enter the same data into two or three different programs.
• A process depends on one person. When they are ill or on holiday, it stalls.
• At month end, someone pulls figures together from emails and spreadsheets, every month over again.

From the first conversation to daily operation

1. 1

   Understand.

   You describe which process costs time. We look at it and write down what the automation has to do. You then receive a quote with a fixed price and a timeline. Up to that point, nothing is charged.

2. 2

   Build.

   We build the automation and test it with your real data before your team works with it.

3. 3

   Launch.

   We train your team. During the first four weeks we answer every question that comes up in daily use.

From then on, the automation does its part day after day. If a step stalls, you receive a notification. Whether we continue to look after it is your decision, and the cost of that is already stated in the quote.

1. 1

   Test server without customer data

   The automated tests run on a test server of our own. It holds no customer data, no real backups and no business credentials.

2. 2

   A gate before every release

   Before every release, a gate checks the exact state that is about to go live. If a test fails or the verdict is missing, the release stops. The tests run on our own servers with our own test pipeline (Woodpecker), not at a third-party service.

3. 3

   Backups in two places

   BilanzKompass backs up encrypted every night off-site, in two locations in Germany with a different provider than the server; the key does not sit with the storage provider. FirmenKompass also backs up off-site in Germany.

4. 4

   Restore rehearsed

   A backup only counts once it has been restored. BilanzKompass automatically restores its backup into a test database every week, FirmenKompass regularly; the rehearsal reports its result to the watchdog.

5. 5

   A watchdog that expects reports

   A watchdog in our control room expects the backup’s report every night and the restore rehearsal’s report regularly. If a report is missing or too old, it raises the alarm. A promise does not count, only the report itself.

6. 6

   AI only with consent

   AI features are off by default: receipt recognition in FirmenKompass and BilanzKompass, dictation in KundenKompass. They only run once the business's administration has consented, and consent can be withdrawn at any time. Without it, nothing goes out: receipts are entered by hand, notes are typed.

Rule since June 2026: before an app goes public, off-site backup and rehearsed restore must be proven by machine. KundenKompass is in the making; this chain applies to it before it enters beta.

Where an app's data goes is explained by each app in its own privacy policy.