IT consultancy · Enschede, Netherlands
We design, build and run AI systems, data platforms and the web applications on top of them — on your infrastructure, by the people you'll actually talk to. The handover isn't a phase at the end. It's how we build.
git push origin main
test backend · frontend
build 3 images → ghcr.io
migrate alembic upgrade head
health containers healthy
postgres · redis · wal-g · EU hosting
VoetLink — practice management for podiatrists, every practice isolated from the next.
What we do
Pipelines that get your data to the point where it can be asked questions, retrieval and tool-using agents on top of it, and the evaluation harness that tells you whether the whole thing works. We build for the day the model is wrong, not only for the demo where it is right.
From a bookkeeping tool that gives back an afternoon a week to a multi-tenant platform holding patient records. One team owns it from the browser tab to the database backup, so nothing falls between suppliers.
European hosting, described in code. Infrastructure you could rebuild from an empty server in an afternoon, with backups that have actually been restored.
Technology radars, architecture reviews, and an honest answer on where AI pays for itself and where it does not. We advise on things we have built ourselves.
Selected work
Open-source technology radar
A self-hosted technology radar for teams that have outgrown a spreadsheet of things we're watching. An interactive radar, a structured catalogue of technologies and assessments, role-based access with Entra ID single sign-on, and reproducible exports for stakeholder reporting. Open source, so the scouting data never leaves the organisation that produced it.
In use at TenneT and Gasunie
Multi-tenant practice management
Practice-management software for podiatrists and pedicures: patients, treatment authorisations, invoicing, contracts and SEPA payments, with every practice's data isolated from the next. Encrypted patient records, background workers and point-in-time database recovery — the unglamorous parts that decide whether healthcare software is allowed to exist at all.
Multi-tenant · in production
Bookkeeping integration for a healthcare practice
A small integration for a healthcare practice: patient invoices from the electronic record system and card payments from the terminal land in e-Boekhouden without anyone re-typing them. What used to be an afternoon of copying every week is now a review of the result. Small on purpose: no new bookkeeping package, just the missing link between three systems the practice already had.
An afternoon a week, returned
Fast, accessible, EU-hosted websites — designed, built and operated end to end.
How we work
Not “where could we use AI”, but which queue, which decision, which afternoon. We read your real cases first, and we say so when a script would do.
Before a system exists: some twenty real cases, each with its right answer. From then on progress is a number you check, not a demo.
Short cycles, running at yours from week one. When the system is unsure, a person decides, by design. The test set runs on every change.
Repositories, infrastructure as code, test set and documentation, in your accounts. That test set lets you swap the model later without us. If we keep running it, that is your choice.
You hold
Settled at the start
Code, data and infrastructure sit in your accounts and your repositories from the first week, not in ours. No proprietary runtime, no licence to expire. Untangling this afterwards is a project of its own; at the start it is a setting.
How we work, step 4: the keysWhere data lives decides which law it falls under, and moving it gets dearer every quarter: more data, more integrations, more people who know the address. So we pick the region before the first deploy. On ours or on yours, and that choice stays reversible.
All of our hosting is inside the EUNobody sits between the problem and the person fixing it. The one who scopes the work writes it, and is still the one you call later. Knowledge of your cases lives in one head you know, not spread along a chain of handovers.
Your message lands with an engineerWhat is not your competitive advantage, we build on open source and contribute back. That is a decision for the first line of code: opening a closed core later means untangling everything that grew around it in the meantime.
Nodus: open source at TenneT and GasunieContact
