IT consultancy · Enschede, Netherlands
We design, build and run AI systems, data platforms and the applications on top of them. On your infrastructure, by the people you actually talk to. Solid means it still works on a Monday morning, and it still works without us.
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
Getting your data into a shape you can ask questions of, AI agents on top that look things up and take action, and a test set that tells you whether the whole thing works. We build for the day the model is wrong, not just for the demo where it is right.
From a small bookkeeping tool that wins back an afternoon a week, to a platform where practices keep patient records, each walled off from the next. One team owns it from the browser tab to the database backup, so nothing gets lost between suppliers.
Hosting in Europe, with the whole setup written down as code. Infrastructure we can rebuild from an empty server in an afternoon, with backups that have actually been restored at least once.
Technology radars, architecture reviews, and an honest answer to where AI pays for itself and where a spreadsheet does the job. We only advise on things we have built ourselves.
Selected work
Open-source technology radar
A technology radar for teams that have outgrown the spreadsheet called 'things to keep an eye on'. Which technologies to invest in, pilot, explore or just watch, with the reasoning behind every call. Log in with your company account, export straight into the management report. Open source and self-hosted, so what you know about the market stays in your own building.
In use at TenneT and Gasunie
Multi-tenant practice management
Practice software for podiatrists and medical pedicurists: patients, insurer authorisations, invoicing, contracts and direct debits, with every practice's data walled off from the next. Encrypted records, and a database we can roll back to any minute of the day. The boring parts, which in healthcare are the whole point.
Multi-tenant · in production
Bookkeeping 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, back
Fast, accessible websites on European servers, designed, built and run end to end.
How we work
Not “where could we use AI”, but which pile of work, which decision, which afternoon that comes back every week. We read your real cases first. If a plain script would do the job, we say so.
Before a system exists: around twenty real cases, each with its right answer. From then on, progress is a number you check, not a demo you watch.
Short cycles, running on your infrastructure from week one. When the system is unsure, it hands the case to a person. That is the design, not a bug. The test set runs on every change.
Code, infrastructure setup, test set and documentation, all in your accounts. That test set is what lets you swap the model later without us. If we keep running it, that is your choice, not a dependency.
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 lock-in, no licence that expires. Untangling this afterwards is a project of its own. At the start it is a checkbox.
How we work, step 4: the keysWhere your data lives decides which law applies to it, and moving it later only gets more expensive. So we pick the region before the first deploy: servers in the EU, on our infrastructure 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. Whoever scopes the work also builds it, and is still the one you call a year later. Knowledge of your situation lives in a head you know, not in a chain of handovers.
Your message lands with an engineerWhatever is not your competitive advantage, we build on open source and give back. That is a decision for the first line of code. Opening up a closed system later means taking apart everything that has grown around it.
Nodus: open source at TenneT and GasunieContact
