Embedded software & systems engineering
Engineering complex systems.Building what comes next.
We help technology-driven organisations architect, develop and validate sophisticated embedded software and engineering systems.
- EMBEmbedded software
- ARCSystems architecture
- INTDistributed integration
- V&VVerification & validation
01Positioning
An independent engineering consultancy for systems that have to work and keep working.
We work where software meets hardware, networks and long product lifecycles. Embedded platforms, distributed communication, and the architecture and verification that hold them together.
Our clients are engineering organisations that already build sophisticated products and need senior capacity, an independent architectural view, or a team that can take responsibility for a difficult part of the system.
We combine architecture, implementation and verification in one engagement, so decisions are tested in code and code is shaped by deliberate decisions.
02Capabilities
Seven capabilities, one engineering discipline.
- 01
Embedded Software Engineering
We shape the software around the product's specific needs, not the other way round.
- 02
Software & Systems Architecture
We make the decisions that are expensive to change early and deliberately, so the system can evolve.
- 03
Systems Integration
We make subsystems from different teams and suppliers work as a single system.
- 04
Verification & Validation
We turn testing into continuous evidence that the system does what it should, not a phase at the end.
- 05
Quality & Automation
Every change is analysed and tested the same way, every time, whoever makes it.
- 06
Technical Advisory
A senior, independent technical view before taking decisions that are hard to undo.
- 07
Cyber Resilience & CRA Compliance
We turn Cyber Resilience Act obligations into concrete engineering decisions, not paperwork.
03Sectors
Where our engineering is applied.
Industries in which we have worked, each with its own constraints, standards and processes.
- IND
Industrial
Embedded and real-time software for machines, production lines and industrial edge devices: deterministic, connected and maintainable for decades.
- AUT
Automotive
Embedded software, connectivity and integration for vehicle electronics, from ECUs and gateways to Linux-based compute platforms and test vehicles.
- SAT
Communications
Software for satellite terminals, modems and ground infrastructure: embedded platforms, RF control, network management and test automation.
- ROB
Robotics
Software architecture, middleware and real-time integration for robots and autonomous systems, from ROS 2 nodes to motion control and fleet communication.
04Engineering approach
Architecture, implementation, integration and verification as one continuous loop.
- 01
Understand
Establish the real problem: system context, constraints, quality attributes and the risks that matter most.
- 02
Architect
Define structure, interfaces and the decisions that are expensive to reverse, and make them explicit.
- 03
Engineer
Implement in small, reviewed increments inside your repository, build and process, with tests from the first commit.
- 04
Integrate
Bring components, hardware and subsystems together early and often, on an explicit plan.
- 05
Verify
Produce evidence that the system meets its requirements, including under faults and load, and do it automatically.
- 06
Evolve
Keep the system changeable: automated quality gates, measured technical debt and a clear roadmap.
Evolve feeds back into Understand: every cycle starts from evidence of the last.
05Technical expertise
Depth across the full system stack.
Organised by the engineering problems each domain solves, from silicon to system-level evidence.
- SEC
Cyber resilience & compliance
Secure platform · Secure communication · SBOM & vulnerabilities · CRA & standards
- QA
Verification & engineering infrastructure
Testing · Tooling · CI/CD & quality gates · Traceability
- L4
Architecture & systems design
Component-based architecture · Interface design · HW/SW architecture · Lifecycle & evolution
- L3
Communication & distribution
DDS · Eclipse Cyclone DDS · Eclipse Zenoh · Networked embedded systems
- L2
Languages & software construction
C · Modern C++ · Rust · Python · Design for testability
- L1
Platform & real-time
Embedded Linux · Yocto Project · RTOS · Hardware abstraction
06How we are different
Commitments about how we work, not claims about who we are.
- 01
Senior engineers, hands on the code
The people who assess your system are the people who design and implement the solution. No hand-off from sales to a delivery team you have not met.
- 02
Architecture and implementation together
We do not stop at recommendations. Architectural decisions are validated in working code, and implementation is guided by architecture.
- 03
Evidence over assertion
Decisions are documented, behaviour is tested and quality is measured. You receive artefacts that can be reviewed, not only opinions.
- 04
Independent and vendor-neutral
We have no licences to resell and no platform to promote. Technology recommendations are based on your constraints alone.
- 05
Built for your team to own
We work in your repositories, tools and processes, and plan the hand-over from the first day. Success means you no longer need us for that system.
- 06
European context
Based in Spain and working across Europe, we know the regulatory, industrial and contractual environment our clients operate in.
07Engagement models
Four ways to work with us.
Every engagement starts with a technical conversation and a written scope. The format follows from the problem, not the other way round.
| Model | What it is | When it fits | What you receive |
|---|---|---|---|
| E1Assessment | A fixed-scope review of an architecture, code base, test strategy or engineering process. | When it fitsBefore a major decision or investment, or when the real condition of a system is unclear. | What you receiveWritten assessment with prioritised, actionable recommendations. |
| E2Embedded engineering | Senior engineers join your team and work in your repositories, tools and process. | When it fitsYou need experienced capacity on a critical or difficult part of the system. | What you receiveProduction code, tests and documentation, plus knowledge transferred to your team. |
| E3Defined delivery | We take responsibility for a well-bounded work package: a subsystem, an integration, a test or build infrastructure. | When it fitsThe scope can be specified and you want a single accountable party for it. | What you receiveA delivered, verified work package with hand-over documentation. |
| E4Fractional architecture lead | A part-time chief-architect role inside your organisation, for as long as it is useful. | When it fitsYou need architecture leadership and governance, but not (yet) a full-time hire. | What you receiveArchitecture decisions, governance practices and a technical roadmap. |
08Insights
Engineering notes on architecture, verification and distributed systems.
- Cyber resilienceThe Cyber Resilience Act for embedded productsWhat the EU Cyber Resilience Act means in engineering terms for manufacturers of embedded and connected products: scope, timeline, essential requirements and where to start.5 min read
- ArchitectureMaintainable architectures for embedded systemsEmbedded products outlive their first hardware, their first team and their first requirements. Five structural decisions that determine whether the software can follow.3 min read
- VerificationVerification strategies for complex softwareCoverage targets do not tell you whether a system works. How to allocate verification effort by risk, across levels, and turn test results into release evidence.3 min read
Contact
Have a system that needs to work and keep working?
Tell us about the system, the constraints and what is at stake. A senior engineer will read it and reply personally.
Start a conversation