Continuous hardware validation

Your hardware, continuously proven against upstream.

Linaro Hub tests the software on your real boards, whether it’s yours, your suppliers’ or upstream’s. AI agents can work with it, and it builds the evidence for your CRA commitments, all without opening a single inbound firewall port.

Services on the Hub

Live views of the CI and test services Linaro runs.

New

TrustedFirmware, tested on real hardware.

One live view of TrustedFirmware CI, with Jenkins, Gerrit and LAVA results together, from a lab that runs on real Arm boards.

Time to recover a board
~7h → ~1h
Fleet availability
~90% → ~99.8%
Jobs per quarter (Juno)
~30,000
Source: Linaro white paper, “Pitfalls of Production-Grade CI for Secure IoT Hardware”, August 2026.
TrustedFirmware results
Live results will appear here.

Mbed TLS

New portal

Security advisories, the issue backlog, release activity and the projects that depend on Mbed TLS, in one place. It is the crypto library inside Trusted Firmware-A and Trusted Firmware-M.

Linaro commits in Mbed TLS 4.2.0
Second only to Arm
59 of 264
Projects using it
Including TF-A and TF-M
27

What Linaro Hub tests on your hardware

  • YOUR SOFTWARE

    Your own images and firmware

    Prove every build boots and behaves on the boards you ship.
  • YOUR PROVIDERS’ SOFTWARE

    Supplier BSPs, SDKs and drops

    Check what your suppliers deliver before you build on it.
  • UPSTREAM SOFTWARE

    Kernel, firmware and distros

    Linux, TrustedFirmware, Yocto and major distributions, on every release.
  • AI AGENTS

    Real boards for AI workflows

    Let agents submit jobs and read results, and check what they build.
  • CRA COMMITMENTS

    Evidence that keeps building

    Continuous test records to back your Cyber Resilience Act obligations.

How it works: connect your hardware to any service

Connect your board to the Hub once, then run any offering on it. The steps are the same for every service.

Step 1

Create your account

Sign up with your email, a password and your name, then verify your email address. One account covers every service.

Step 2

Plug in your hardware

Power on the Linaro Automation Appliance next to your hardware. It ships pre-registered and shows as Online within seconds.

Step 3

Tell the Hub which board it is

Choose your board from the searchable device list. Swap the hardware later and just change the selection.

Step 4

Run any service on it

Your Linaro contact turns an offering on, results appear in your Hub subscription, and you can add more services later.

Explore all Solutions

Start from the outcome you need, not the tool name.

  1. Show customers and partners that your firmware meets Arm’s standards, and keep proving it as you release.
    Run the Arm Architecture Compliance Suite (BSA, BBR, BBSR)
    Cover both SystemReady and SystemReady DT bands
    Request runs or follow your firmware release streams
  2. ONELab · Distributions
    Prove your board runs the operating systems your customers already use, with nothing custom in between.
    Boot generic kernels from 7+ major distributions
    Includes Debian, Ubuntu, Fedora, Alpine and openSUSE
    No custom BSP required
  3. LAA + LAVA managed services
    Keep boards on your desk while Linaro runs the lab software, so your engineers test instead of maintaining a lab.
    Linaro updates and maintains the lab software
    Manage a global fleet of appliances from one dashboard
    Submit and follow LAVA jobs from the Hub
  4. Pull Labs · KernelCI
    Put your platform in front of the upstream kernel’s test infrastructure, without building a lab to host it.
    Outbound-only connection, with no inbound firewall rules
    Catch regressions before they reach your customers
    Follow every run from the Pull Labs dashboard
  5. Turn continuous testing into the records an auditor will ask for.
    Keep firmware and boot components verified and current
    Build a continuous test record from your ongoing runs
    Hand evidence to auditors without a scramble
  6. Reference images · ONEBoot
    Begin bring-up from images and boot flows that are already tested, instead of from a blank page.
    Tested boot flows for U-Boot, OpenEmbedded and the kernel
    Reference images to bring up a new board faster
    A baseline to compare your own builds against