Hard problems, settled.
A one-person Dutch software company, turning tangled backend, embedded and tooling problems into reliable software.
Click anywhere in the bowl to drop a point. Wherever it starts, it finds the same bottom. That is what convex means.
What I build
Three kinds of work, one aim: take something tangled and leave a system that is clear, tested and documented.
-
Backend & API development
When
Your data lives in systems that disagree, and the integrations between them are held together by scripts nobody wants to touch.
You get
One well-documented API with clear data models, tests and monitoring that your own team can understand and extend.
Typical work
- REST and event-driven APIs
- Database design and migrations
- Third-party integrations
- Performance and reliability fixes
GET /v1/orders/4821 200 OK application/json { "id": 4821, "status": "shipped", "items": 3, "updated": "2026-10-14T09:12:00Z" } -
Embedded & systems software
When
A device, sensor or machine needs software that is fast and predictable, and has to talk reliably to the rest of your stack.
You get
Firmware and system services that are tested on the real hardware, handle failure gracefully and are documented for whoever maintains them next.
Typical work
- Microcontroller firmware
- Device communication and protocols
- Linux system services
- Bridges from hardware to the cloud
[boot] firmware v2.3.1 [bus ] i2c sensor 0x48 ok [link] uplink connected [read] temperature 21.4 °C [read] door closed [ ok ] watchdog armed -
Developer tooling & automation
When
Your team loses hours to manual releases, fragile build steps and repetitive checks that should run by themselves.
You get
Command-line tools, build pipelines and automation that make routine work fast, repeatable and hard to get wrong.
Typical work
- Internal command-line tools
- CI/CD pipelines
- Test and release automation
- Scripts turned into maintained tools
$ release --check tests passed lint clean changelog updated version v1.4.0 ready to tag
The code samples are illustrative examples of each kind of work, not client code.
How I work
Every project follows the same descent: from a tangled problem to one clear, working answer.
-
Agree on the problem first
Before any code, we pin down what is broken, what “done” looks like and what is out of scope. Surprises are cheapest before the work starts.
-
Choose the simplest thing that works
Proven technology over the latest trend. Fewer moving parts means fewer things that can break later.
-
Build it to be handed over
Readable code, tests and documentation, so your own team or the next developer can carry on without me.
-
Keep you in the loop
Short, regular updates in plain language. You always know what is done, what comes next and why.
Tell me what’s stuck
A few sentences is enough: what you are building, where it hurts and when you need it. You will get an honest view on whether, and how, Convexed can help.
hello@convexed.nlWhat happens next
- You send a short description of the problem.
- I reply with questions, or with a first view of how I would approach it.
- If it is a good fit, we agree on the scope in writing before any work starts.