Alaunus

Release with confidence.

Your robots keep learning after they ship. Every update should make them better, not less safe. Alaunus makes sure of it.

Why Alaunus
Why you need it

The robot you sold is not the robot running today.

New software. New models. New sites. Your safety file was written for the machine that left your building, and every update since has put distance between your robots and their proof.

Your robots keep changing

You ship software, model, and config updates for years after delivery. Every one of them can quietly break the safety case the machine was approved under.

The rules caught up

Your machines fall under the EU Machinery Regulation and the AI Act, and ISO 10218 was rewritten in 2025 for the first time in 14 years. Regulators now expect you to prove a machine is still what its paperwork says it is.

Your proof lives in the wrong places

Risk files, test results, and sign-offs sit in folders, spreadsheets, and inboxes. When a customer, auditor, or incident asks, your team spends weeks assembling the answer.

Re-validation kills your velocity

You cannot say which robots a given update affects, so you either re-check everything and ship slowly, or ship on faith and hope nothing was touched.

Jan 2027 the EU Machinery Regulation applies in full, AI safety functions included
Aug 2026 AI Act obligations for high-risk systems start applying
Since 2011 the core robot safety standard went untouched, until now

So your updates wait, or they ship on faith. Neither should be the price of shipping better robots.

What Alaunus is

The release gate for robots in the field.

Today, the answer to “is this update safe to ship?” lives in folders, spreadsheets, and people’s heads. Alaunus puts it in one place.

Know what a change touches

See which robots, sites, and approvals an update affects before it ships.

Know what to re-check

Get a clear list of what still holds, and what needs a second look.

Ship with evidence

Every release carries a signed, exportable record. Nothing falls through the cracks.

Alaunus organizes the evidence. Your people still make the call.

How it works

Three steps. Works with what you already have.

  1. 01

    Connect

    Link the systems you already use: code, models, and your fleet.

  2. 02

    Review

    When an update is proposed, see what it affects and what to re-check.

  3. 03

    Release

    Named people sign off. The evidence travels with the release.

Early access

We’re working with our first partners now.

If you build or operate robots that keep evolving after they ship, we’d like to talk.

hello@alaunus.ai