A small engineering house that behaves like your own team

We are an electronics engineering house in Wallonia, Belgium. We design boards, write the firmware that runs on them, put the logic that is too fast for a processor into an FPGA, put models on the device where that earns its place, and stay involved until the product is being built repeatably by someone else.

Why the seams matter

When the hardware comes from one supplier, the firmware from another and the model from a third, the interesting problems live exactly in between — a timing margin nobody owns, a power rail that sags only during a radio burst, a model that was validated on data the sensor front end cannot actually produce. Doing all of it under one roof is not a sales argument; it removes a whole class of problem from the project.

How we prefer to work

Small teams, direct contact with the engineers doing the work, and written decisions. We would rather spend a day at the start arguing about requirements than three weeks at the end explaining a re-spin. If we think a project is not a good fit for us, we say so early — that is cheaper for everyone than a polite yes.

Senior engineers, not a pyramid

The person in the kickoff call is the person doing the work. There is no account layer translating your requirements into someone else's first embedded project, and no incentive to stretch a project to fill a bench.

What you own

Sources, schematics, layout files, RTL, models, documentation and manufacturing data belong to you. We do not build dependencies into projects to keep clients, and we hand over in a state where another engineer can continue without us.

Independent by design

We are not tied to a silicon vendor, a distributor or an AI platform. Component and toolchain choices are made on technical merit, availability and lifecycle — which is why the vendor list on our home page is long rather than short.