Skip to content
AXXA

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.

Schematic of a distributed embedded systemThree compute nodes, each built from hardware, platform, middleware and application layers. The nodes share a physical network and exchange data through publish/subscribe middleware; a gateway node bridges the system to edge and cloud services.L4APPLICATIONL3MIDDLEWAREL2PLATFORML1HARDWAREN1node.controlcontrolddslinuxsocN2node.sensingsensingzenohrtosmcuN3node.gatewaygatewaymqttbaremetalfpgaNETETHERNET · UDP MULTICASTtopic/state · reliabletopic/cmd · deadlineEDGE / CLOUDHAL LAYERSHEETSYS-ARCH-01SCOPEILLUSTRATIVE
  • 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.

04Engineering approach

Architecture, implementation, integration and verification as one continuous loop.

How we work
  1. 01

    Understand

    Establish the real problem: system context, constraints, quality attributes and the risks that matter most.

  2. 02

    Architect

    Define structure, interfaces and the decisions that are expensive to reverse, and make them explicit.

  3. 03

    Engineer

    Implement in small, reviewed increments inside your repository, build and process, with tests from the first commit.

  4. 04

    Integrate

    Bring components, hardware and subsystems together early and often, on an explicit plan.

  5. 05

    Verify

    Produce evidence that the system meets its requirements, including under faults and load, and do it automatically.

  6. 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.

Explore expertise
  1. SEC

    Cyber resilience & compliance

    Secure platform · Secure communication · SBOM & vulnerabilities · CRA & standards

  2. QA

    Verification & engineering infrastructure

    Testing · Tooling · CI/CD & quality gates · Traceability

  3. L4

    Architecture & systems design

    Component-based architecture · Interface design · HW/SW architecture · Lifecycle & evolution

  4. L3

    Communication & distribution

    DDS · Eclipse Cyclone DDS · Eclipse Zenoh · Networked embedded systems

  5. L2

    Languages & software construction

    C · Modern C++ · Rust · Python · Design for testability

  6. 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.

  1. 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.

  2. 02

    Architecture and implementation together

    We do not stop at recommendations. Architectural decisions are validated in working code, and implementation is guided by architecture.

  3. 03

    Evidence over assertion

    Decisions are documented, behaviour is tested and quality is measured. You receive artefacts that can be reviewed, not only opinions.

  4. 04

    Independent and vendor-neutral

    We have no licences to resell and no platform to promote. Technology recommendations are based on your constraints alone.

  5. 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.

  6. 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.

Engagement models compared by purpose, fit and output
ModelWhat it isWhen it fitsWhat you receive
E1AssessmentA 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 engineeringSenior 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 deliveryWe 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 leadA 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.

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