[ 01 ]
Software Development
Greenfield product engineering for B2B SaaS — from concept to first paying customer. And modernisation of legacy systems: replatformed, refactored, restored to shipping velocity.
One story a day, in English. No tracking pixels, unsubscribe in one click.
Check your inbox and confirm the address — the first one arrives tomorrow morning.
That did not go through. Try again in a moment.
We build, modernise, and migrate B2B software — from greenfield products through cloud architecture and EU sovereignty migrations to production AI agents.
[ 01 ]
Greenfield product engineering for B2B SaaS — from concept to first paying customer. And modernisation of legacy systems: replatformed, refactored, restored to shipping velocity.
[ 02 ]
Greenfield cloud architecture and first-time migrations into the cloud. Reference designs on AWS and Cloudflare — sized for cost, instrumented for observability, with a clean blast radius from day one.
[ 03 ]
Migration off non-EU hyperscalers onto European providers like Scaleway. The same workloads, replatformed for jurisdictional clarity, European data residency, and a clean regulatory footprint.
[ 04 ]
Production-grade B2B agents engineered for clients. Tool-use, retrieval, evals, and orchestration designed around cost, latency, and provable behaviour — built to ship to real customers.
Four products, each one something we needed and could not buy from a European vendor. Two of them are running on this page while you read it.
The banner you answered
Cookie banner, automatic blocker and daily scanner in one, holding every third-party tag back until the visitor decides. Google Consent Mode v2, and a “Reject” that cannot be configured away.
Watching this page
Uptime checks from Cloudflare’s edge, as often as every minute. Incidents open and close themselves, and the status page says what actually happened rather than showing a permanently green tick.
Sends the snack above
Our own mailing tool. Lists, double opt-in and one-click unsubscribe, sending from our own infrastructure — no third-party mailer holding the addresses, and no key to leak.
Private beta
Customer feedback read against a live picture of your codebase — architecture, conventions, open tickets — then drafted into a ticket engineering can pick up.
A small senior engineering team based in Hamburg. The person who pitches you is the person who builds.
Chief of everything
Chief of Edge Cases
Chief of Cache Invalidation
Chief of Deploy Fridays
And of course — cats and dogs.
Not chatbots bolted onto a product. Each one owns a part of the business, works while nobody is watching, and answers for what it did. This page was picked, written and published by one of them this morning.
Chief Financial Officer
Reads the books every night, drafts the invoices for work that has been done, and files what arrives. He will not invent a figure: asked something he cannot source, he says so.
Chief Operating Officer
Watches delivery — what is finished, what is stuck, what is still up. She works out how long work actually took from the ticket and its comments, because elapsed time is not effort.
Chief Marketing Officer
Reads the AI news every night, picks the one thing worth your two minutes, and writes it up. The snack at the top of this page is hers, comic included.
Chief Data Privacy Officer
Watches consent across every site we run it on: what visitors actually agreed to, which cookies appeared without asking, and which of those is a problem rather than tidying-up.
Art Director
Draws. Mia commissions a picture for the day’s note and Leo makes it — in code, not from an image model, so it is ours and it is the same house style every time.
Daily check-ins
Asks the team what they are doing each morning, nudges the ones who forget, and writes the Friday summary. The only one who talks to everybody every day.
Every one of them refuses more than it answers — no figures in the wrong room, no client detail, nothing it was not explicitly given. That is the part that took the longest. See how they work together →
MCP, EU cloud migration, agentic AI in production, and how modern engineering teams actually ship. Written by the people doing the work.
The Model Context Protocol is the unglamorous plumbing that turns a chat window into a coworker. A short, practical tour of what MCP is, what it’s used for, and where it earns its keep.
Read articleSchrems II didn’t get repealed. The CLOUD Act didn’t get rescinded. And procurement teams in the EU are starting to act on it — quietly, then suddenly.
Read articleMost agentic AI demos break the second they meet a real workflow. The difference between a demo and a production system is mostly retrieval, evals, and the boring loop around the model.
Read articleEngineering velocity isn’t an IDE problem or a language problem. It’s an operating-model problem — how teams structure feedback loops, ship cadence, and the cost of a bad commit.
Read articleWe registered TEKKNA on 1 January 2026. The date was a logistics choice, not a symbol — but the idea behind the company had been waiting much longer.
Read article