Brand & 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 443 and 868 MHz industrial mesh. 2,400 nodes; 99.997% uplink.
A rugged handheld device for when infrastructure fails. Peer-to-peer mesh radio, e-ink display, physical keyboard, local AI. No cell, no cloud — built for extreme conditions, emergencies, and resilient communities.
Small satellite ground station served via REST API and MCP for AI agents. Two nodes — Ericeira and Braga — receiving and forwarding orbital data in real time.
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 passive multi-band signal capture device built for defense and government. Monitors ADS-B aircraft transponders, AIS naval traffic, and automotive TPMS simultaneously — no transmission, no signature. Designed for border surveillance, port monitoring, and critical infrastructure intelligence.
A compact, fanless hub for home automation with a local AI inference layer. Controls lights, locks, cameras, and thermostat from a single device — no cloud required. Built and tested at the Ericeira lab.
We work from offices in Lisbon, Braga, Ericeira, Matosinhos, London, and Oslo — 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.
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.
Established patterns exist because they survived contact with reality. We build on them deliberately — the well-documented option, the one with the long changelog and the quiet mailing list. Mature tooling means known failure modes, known recovery paths, and a community that has already solved the problem you haven't had yet. Novelty is a tax we pay only when it buys something a proven pattern cannot.
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
RF, networks, disks — we design assuming they break, and recover before anyone notices. Graceful degradation is a product feature, not a stretch goal.
We report in numbers that matter: nines, latency, on-call volume, handoff weight. Activity is not progress; shipped reliability is.
Tell us what you're building and what keeps breaking. We'll respond with a written memo, no slides, within five business days.