Robotics · R-03

Ship robot software updates without a site visit.

Signed software updates for robots: packages signed with keys you hold, staged rollouts with rollback when a health check fails, an audit trail of who shipped what to which robot, and dashboards that show where every release stands.

  • Signedwith keys you hold
  • Staged1%, 10%, then every unit
  • Rollbackwhen a health check fails
  • Audit trailwho shipped what, where, when

Talk to an engineer All robotics lines

What we build

An update pipeline you can run on a Friday

Built in your repositories and your cloud. Your team presses the button; the pipeline does the rest and writes it down.

Signed packages

Every package signed with keys you hold, and checked on the robot before it installs. A package that fails the check is refused and reported.

Staged rollouts

A release goes to a small share of units first, then more, then all, by site, customer or model. Each stage waits for its health checks to pass.

Rollback

If a health check fails after install, the robot goes back to the last good version by itself, and the rollout stops until a person decides.

Audit trail

Who built each release, who approved it, which robots got it and when, kept where your auditors and customers can read it.

Update dashboards

Where every release stands: per robot, site and customer, with failures and rollbacks at the top.

Release notes for the authorization

Each release says whether it changes anything reported at certification, so your lab and counsel can decide what kind of change it is before it ships.

FCC and updates

Updates for authorized models

FCC DA 26-789 lets devices the FCC authorized keep receiving software and firmware updates at least until January 1, 2029, under the conditions the order sets. Class II changes still need test results and FCC acknowledgement before the modified device is marketed.

The pipeline can hold a release until that acknowledgement is in, and the release notes record why. Checked November 2026.

General information about software engineering work, not legal advice. Rules change; read the linked source, and ask your own counsel and an accredited test lab before you rely on any of it.

Who does what

  • Digi117: the pipeline, the signing setup, the dashboards and the records
  • Your team or partner: motor and safety firmware builds, which the pipeline signs and delivers as released
  • Your lab and counsel: what kind of change a release is
  • You: the keys and the final say on every release

Questions about robot updates

Do you change motor or safety firmware?

No. Those builds come from your team or a partner. The pipeline signs and delivers what they release, with the same staging, rollback and audit trail.

Who holds the signing keys?

You do. We set up the signing and the key storage with your team, and our access ends when the work ends.

What about robots that are offline most of the day?

The design covers it: packages wait on the robot or a site gateway and install in a window you set, and the dashboard shows which robots have not checked in.

What does an update change for an FCC-authorized model?

That depends on what it touches. The release notes say so per build, and your lab and counsel decide. Start with the checklist.

Tell us how you update robots today.

A USB stick, a script, a vendor tool or a site visit: send what you do now. We reply with what we would build first.

Contact us All robotics lines

Reply within one business day · Not legal advice