Principles / Technical thesis

Why we built it this way.

Most of our customers do not need to read this page. They just want their tools to work, their data to stay theirs, and their evenings to come back. But if you are a CTO, a procurement officer, an auditor, or a journalist, this is the technical reasoning behind every architecture decision we make.

The thesis in one paragraph

AI is becoming the operating layer of small business. The tools that handle bookings, contracts, customer messaging and bookkeeping are becoming AI tools. Whoever owns that layer owns the business. Most current vendors are renting it to you, on infrastructure they control, in jurisdictions you do not understand. We build the opposite. EU servers, your data, your code, your call.

Three pressures arriving at the same time

Sovereignty is not a marketing word. It is three concrete legal pressures landing on European businesses simultaneously. None of them are theoretical anymore.

01 / In force October 2024, enforced through 2026

NIS2 Directive

The successor to NIS1 expands scope to most mid-size organizations and introduces personal liability for executives. If your AI vendor cannot tell you where data lives, where it is processed, and who can access it, you cannot answer your regulator. The fines are real and the reporting clock is short.

02 / Already binding since 2020

Schrems II implications

The Court of Justice of the European Union invalidated Privacy Shield in 2020. Standard contractual clauses do not cure the underlying problem: US surveillance law (FISA 702, EO 12333) does not stop applying because you wrote it in a contract. EU customer data on US-controlled infrastructure is a continuous audit risk, not a solved problem.

03 / Always on, growing in scope

CLOUD Act risk

US authorities can compel a US company to hand over EU data even if it is stored in Frankfurt or Stockholm. The provider is often legally prevented from telling you. The only structural answer is infrastructure operated by an EU entity, on EU soil, under EU law. Built-on-EU is the answer, not a checkbox.

We rented our AI stack from US vendors for fifteen years. Now Brussels is asking who owns the data. The honest answer for most small businesses is: nobody knows. We are trying to fix that.

How this shapes what we build

One: We default to one-off project deliveries

The standard subscription model creates a permanent dependency between customer and vendor. We sell projects instead. You pay a fixed price, we deliver a working system, you own the code and the credentials. If you decide we are no longer useful, you continue without us. That is the point.

Two: Our infrastructure runs on EU servers we operate

Hetzner in Helsinki and Falkenstein. PostgreSQL, n8n, our own services, all on machines whose root SSH credentials sit with us, not with a US hyperscaler. When a customer asks where their data is, we name the data centre and the rack.

Three: AI models are picked by what they can guarantee

We use Anthropic Claude, OpenAI GPT, Google Gemini and open source models depending on the task. For sensitive work we prefer EU-deployed Mistral or self-hosted models. We never silently route customer data through a third party we have not named in the contract.

Four: Open architecture, no proprietary lock-in

The technical stack we deliver is mostly open source: PostgreSQL, n8n, FastAPI, modern React, Docker. If we get hit by a bus, your IT person can pick up the project from the README. That is a bus factor of one, not a vendor lock-in of forever.

Where this is not the right fit

If you want a polished SaaS dashboard with twelve stock photos, a chat widget that looks like every other chat widget, and a five year contract that someone in Singapore signed for you: we are not the right fit. We are not faster than the cheap subscription tools at the bottom of the market. We are slower at first because we are building you something you will own.

If that trade is not interesting to you, no hard feelings. But if you have ever had a vendor change their pricing model overnight, or get acquired, or simply disappear, you already know why this matters.