Microcontrollers & firmware
STM32, ESP, RP2040, and friends. Bare-metal or RTOS, bootloaders, OTA, drivers, and the bus glue (I²C, SPI, CAN, UART) that makes a board do its job.
How we build
From a sketch to hardware that ships
We design custom hardware from zero to product, electronics, firmware, power, control, sensors, and comms, and we stay on the bench through bring-up, validation, and the handoff to manufacturing. If it has to work in the real world, we’ll build it to.
What we cover
The whole stack, under one roof
Most hardware projects die in the gaps between disciplines, where the firmware team blames the power team and nobody owns the mechanics. We don’t hand off across those gaps. We design the whole thing as one system.
Power electronics
Switching converters, battery management, motor drives, and protection. Designed for thermal reality and EMC, not just a clean simulation.
Control systems
Closed-loop motion and actuation, state estimation, and autonomy logic. From PID that just works to estimators that hold steady under noise.
Sensors & instrumentation
Analog front-ends, signal conditioning, calibration, and sensor fusion. We chase the millivolt that matters and reject the noise that does not.
Comms systems
RF and wired links, custom protocols, and telemetry that survives a bad channel. Ground station to onboard, robust by design.
Mechanical design
Enclosures, mounts, thermal paths, and the structure that survives a drop test. We design the mechanics around the electronics, not bolted on after.
3D printing & fabrication
In-house 3D printing and rapid prototyping. Brackets, jigs, and enclosures in hand the same week, so we iterate on real parts instead of renders.
The process
Zero to product, in six honest steps
No black boxes. You see where the project is and what it costs at every stage. Here’s how a build actually goes.
- 01
Discovery
We start with your problem, constraints, and the environment the thing has to survive. Requirements, risks, and a realistic budget, written down before anyone touches a schematic.
- 02
Architecture
Block diagrams, part selection, and the trade-offs that decide everything later. Power budget, compute, comms, and mechanics planned together, not bolted on.
- 03
Design
Schematic capture, PCB layout, firmware structure, and mechanical CAD. Design-for-manufacture and design-for-test baked in from the first revision.
- 04
Prototype & bring-up
We build it, power it on, and find out what reality thinks. Board bring-up, firmware, and the unglamorous debugging that turns a render into hardware.
- 05
Validation
Functional, thermal, and field testing against the requirements we agreed on. We document the smoke before it clears so the next revision inherits the fix.
- 06
Production handoff
Manufacturing files, test jigs, documentation, and a build that repeats. You leave with a product, not a one-off that only worked on our bench.
Ways to work with us
Pick the depth you need
A full build, a second pair of expert eyes, or the integration muscle to make a system come together. Start anywhere. Projects often move between these as they grow.
Custom builds, 0 → product
You bring the brief, we own the electronics, firmware, and integration through to a repeatable product. The full stack, one accountable team.
- ▹Schematic + PCB design
- ▹Firmware & control
- ▹Prototype to production
Electronics & mechanical consultancy
Design reviews, architecture calls, EMC, thermal and power sanity checks, and debugging the gremlin nobody else could find, on both the electrical and mechanical side.
- ▹Design & schematic reviews
- ▹Mechanical & thermal review
- ▹Failure analysis & debug
Integration services
Subsystems from different vendors that refuse to cooperate? We make hardware, firmware, and mechanics agree, then prove it on the bench before the field does.
- ▹Subsystem integration
- ▹Bring-up & test
- ▹Bench-validated handoff
What you leave with
A product, not a pile of prototypes
When we’re done, you own a build that repeats and the files to prove it. No vendor lock-in, no “only Kristóf knows how it works.” Everything documented well enough that a stranger could pick it up and keep going.
- ✓Schematics & PCB design files
- ✓Firmware source & build setup
- ✓Mechanical CAD & enclosures
- ✓Bill of materials & sourcing notes
- ✓Test procedures & jigs
- ✓Documentation that a stranger could build from
Got something to build?
Tell us what should exist but doesn’t yet
Send a one-paragraph brief or a messy sketch. Either works. We’ll tell you honestly whether we’re the right team, what it might take, and where we’d start. No buzzwords, no upsell.
Start a conversation →