Design
Brand, UI, and product design for technical companies. Square, measured, specific.
Brand, UI, and product design for technical companies. Square, measured, specific.
Positioning, launch strategy, and growth loops. Copy engineers want to read.
Web, mobile, and back-of-house. Typed languages, small teams, boring technology.
Design for systems that have to keep running at three in the morning on a Sunday.
Build, ship, observe. We run what we build.
Building the boxes on the rack, and the firmware that runs on them.
2.4GHz and sub-GHz. Mesh, point-to-point, long-haul. Spectrum is a resource; we treat it like one.
Domotics, security, and the wiring that disappears into the walls.
Prototype boards, enclosures, and the early hours of a product nobody has seen yet.
A boring, debuggable firmware target for 2.4GHz industrial mesh. 2,400 nodes; 99.997% uplink.
A 14-year monolith sharded into 8 nodes without dropping a single write. 47 min of degraded reads.
From schematic to FCC-certified production unit in 11 months. Designed, fabricated, shipped.
A single-binary simulation harness for 2.4GHz mesh firmware. Runs 512 virtual nodes on one laptop; no hardware required to validate routing logic.
A minimal TLS-terminating reverse proxy that self-configures from environment variables. Under 4 MB binary; deploys to a 1U in under 30 seconds.
The first breadboard iteration of the fanless edge appliance. Four Ethernet ports, one USB-C console, passive cooling. Ran for 11 months before taping out rev 1.
We pick the well-documented option. The one with the long changelog and the quiet mailing list. Novelty is a tax we pay only when it buys something real.
RF, networks, disks — we design assuming they break, and recover before anyone notices. Graceful degradation is a product feature, not a stretch goal.
Design, software, and operations are the same project. We run what we build. Anything else is theater, and theater doesn't answer the phone at 3 a.m.
We report in numbers that matter: nines, latency, on-call volume, handoff weight. Activity is not progress; shipped reliability is.
We work from offices in Lisbon and Braga — and from wherever the work makes sense. Remote-first when concentration demands it, on-site when presence does. We run the same model with partners: sprints in shared spaces, offsite weeks with our partners, and hands-on sessions when the problem is physical.
"Never trust a thought that occurs to you indoors."
— Nietzsche · That's why we spend ~30% of our time outdoors — ideas included.
We run a continuous prototype programme — hardware boards, software experiments, AI integrations, RF test rigs, design probes. Most fail. A few become products. The point is the cadence: if you are not testing something new every week, you are falling behind. We do this internally, and we bring partners into the lab when the problem warrants it.
"Is there anyone so wise as to learn by the experience of others?"
— Voltaire
Tell us what you're building and what keeps breaking. We'll respond with a written memo, no slides, within five business days.