I'm Tom Segbers. I build payment infrastructure, embedded vision, and product systems whose interfaces explain themselves.
$ whoami
Tom Segbers / Senior developer
$ cat focus.json
{
"focus": ["systems", "interfaces"],
"archive": "2010—2026",
"caseFiles": 28
}Selected case file
Hammer Robotics: Building Mark I for Airport Baggage HandlingI founded Hammer Robotics to automate heavy logistics work with embodied AI. Our Mark humanoid prototype targets airport baggage handling and is preparing pilots with three major German airports.
I / Case files
Four case files that show the range: humanoid robotics, a creator-platform exit, embedded vision, and agent orchestration.
I founded Hammer Robotics to automate heavy logistics work with embodied AI. Our Mark humanoid prototype targets airport baggage handling and is preparing pilots with three major German airports.
I built ClosedLoopOS, an open-source TypeScript platform that turns business processes into YAML SOPs and assigns them to AI agents with an operational dashboard.
I co-founded LAYZR and served as CTO, building a creator loyalty platform that reached 100k+ monthly users and was acquired by Jodel.
For my bachelor thesis, I built ISeeUNet, a modified U-Net trained on hybrid real and synthetic datasets for real-time change detection on Nvidia Jetson NX hardware.
II / Capabilities
I work across the layers that make a product trustworthy: data, interfaces, deployment, and the quiet decisions in between.
Service boundaries, data flows, and the unglamorous glue that keeps a product predictable.
Interfaces that make complex state legible, work by keyboard, and stay fast under real content.
Pragmatic architecture, observability, and release paths that do not depend on heroics.
Working close enough to the problem to know which complexity is necessary and which is theatre.
III / Dispatches
Notes from the workbench: homelabs, automation, and the occasional recipe.
The field-level schema for seven record kinds and twelve defined nouns, the grant algorithm, the time model and the four files a pack may add.
Read dispatchA company OS in one log and four services: records and gates stay domain-free, the eighteen packs add only nouns and gates, and the board decides through the same signed log.
Read dispatchSeven record kinds, eighteen verbs, fifteen axioms: fifty requirements rewritten in a controlled vocabulary and tested by two writers who never compared notes.
Read dispatchIV / Next
If you have a system that needs to be clearer, faster, or more dependable, I would like to hear about it.
Bring the problem.
No pitch deck required.