Robotics

Software that keeps robots working after the demo.

Digi117 builds the software around the robot: fleet consoles, apps for staff and customers, cloud and data, signed updates and integrations with the systems your customers already run, plus ROS 1 to ROS 2 moves. We do not build safety-rated control, motor firmware or mechanical design; partners who specialize in them do, and we agree the interfaces with them in writing.

  • 10 service linesfrom North America launch to rescue
  • EN, FR, ESapps, documents and portals
  • Free ROS 1 scana written quote after it
  • Labs and counselcertify and advise; we engineer

Talk to an engineer Launching in North America?

DATES ROBOT MAKERS CANNOT MOVEJUL 16 2025JUL 28 2026JUL 30 2026OCT 13 2026JUL 30 2027JAN 1 2029Mexico: new telecom lawFCC: robots on the Covered ListISED: RSS-Gen Issue 6FCC: logic-bearing parts ruleISED: Issue 6 transition endsFCC: update waiver runs at least toCRT issues homologation rulesnew models need a DoW Conditional ApprovalQR code labelling allowedparts from Covered List makers checkedapplications on Issue 6 onlyClass I and II software changesIllustration. Sources: the official links on the checklist page.

Service lines

Ten service lines for the software around the robot

Pick one or several. Each is scoped and quoted in writing after a short review of one model or one site. Five have their own page; the rest are described here.

R-01 · Flagship

North America launch for robot makers

For makers from Asia, Europe and Canada bringing robots to the US and Canada. Local cloud and data handling, apps and documents in English, French and Spanish, an update service, an integrator portal, and the engineering evidence for content rules and the approval file. Norvoya, Digi117's front office for North American market entry, handles the market side.

Details

R-02

Fleet console and remote operations

Live status and maps for every robot, alerts routed to the right person, hooks for remote assist, uptime reports, and role-based views so each customer sees only their own robots.

Details

R-03

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 for every release.

Details

R-04

Robot apps for staff and customers

Operator and companion apps: setup flows that a site team can follow on day one, scheduling, units and formats per locale, and accessibility built in from the first screen.

R-05

ROS 1 to ROS 2 move

A workspace audit, a dependency map, a staged port package by package, and simulation regression tests before code reaches a robot. The workspace scan is free; the written quote comes after it.

Details

R-06

Connect robots to your systems

WMS, WES and ERP in warehouses, PMS and POS in hotels and stores, elevators and doors in buildings, and the VDA 5050 and Open-RMF interfaces between robots and the systems that dispatch them.

Details

R-07

Robot data and AI

Log capture from the fleet, search and replay of any run, labeling pipelines for the data your models learn from, and model deployment to the robot's own computer, with a test set each model passes before it ships.

R-08

Test before the floor

Simulated test scenes for the sites your robots work in, regression suites that run in CI on every change, and hooks for hardware-in-the-loop rigs with the real controller boards on a bench.

R-09

Robot software rescue

For a codebase or a fleet that crashes, drifts or can't be updated. We read the code and the logs first, write down what is wrong, then stabilize it one fix at a time, each quoted before work starts.

R-10

Senior robotics engineers in your team

Cloud, fleet, app, data and ROS 2 engineers who join your stand-ups, work in your repositories and follow your code review. Introduced to you before the quote is signed.

How engineers join a team

Sensors, meters, appliances or industrial devices rather than robots? Device platforms, telemetry, PLC, SCADA and MES links and operator apps are on the Connected hardware page.

Scope

What we build, and what we leave to specialists

A robot that works in a demo still needs a console for the people who run the fleet, updates that reach every unit, apps a site team can set up, and links to the systems a customer already pays for. That software is our work.

Compliance work is engineering evidence and support: parts lists, change logs, data maps and the records a lab or counsel asks for. Accredited labs test and certify, regulators authorize, and counsel advises.

Who does what

  • Digi117: consoles, apps, cloud, data, updates, integrations and ROS 2 moves, with their records
  • Your team or a hardware partner: safety-rated control, motor firmware and mechanical design
  • Accredited test labs: testing and certification
  • Your counsel: legal opinions and filings
  • You: decisions, keys and the final say on every release

What changed

What changed for robot makers entering North America

Each line below is checked against the regulator's own document. Dates are as published. Checked November 2026.

Date and regulatorWhat changedWhat it means for the software
Jul 28, 2026 · FCC (US)Foreign-produced advanced robotic devices were added to the FCC Covered List, except those granted a Conditional Approval by the Department of War. Covered equipment cannot receive new equipment authorizations. The FCC's fact sheet names mobile robots such as humanoids and quadrupeds, and says models it already authorized can still be imported, sold and used. DA 26-786 · fact sheetAn already authorized model is the asset. Firmware work has to stay inside what that authorization covers, and every change needs a record of what it touched.
Jul 28, 2026 · FCC (US)A waiver allows Class I and Class II permissive changes for software and firmware updates that mitigate harm to US consumers, on devices authorized before Jul 28, 2026, at least until Jan 1, 2029. Class II changes still need test results and FCC acknowledgement before the modified device is marketed. DA 26-789The update pipeline needs release notes that say whether a build changes anything reported at certification, and a way to hold a release until a Class II change is acknowledged.
Oct 13, 2026 · FCC (US)Rules in effect: no authorization for devices that contain logic-bearing hardware components made by an entity on the Covered List. Logic-bearing means, in part, parts that generate and use timing signals above 9,000 pulses per second with digital techniques. FCC 26-50, Federal RegisterA bill of materials down to every board, module and controller, with its maker, before an application is filed.
Jul 30, 2026 · ISED (Canada)RSS-Gen Issue 6 published, with QR code labelling allowed and electronic labelling clarified. ISED's notice sets the end of the transition period at Jul 30, 2027; after it, certification applications use Issue 6 only. RSS-Gen · Notice 2026-DRS0001An e-label screen in the app or on the robot's display, built to the issue the lab tests against.
Jul 16, 2025 · CRT (Mexico)The Ley en Materia de Telecomunicaciones y Radiodifusión was published. It sets up the Comisión Reguladora de Telecomunicaciones (CRT), which issues the rules on homologation and conformity assessment. The CRT states that the Instituto Federal de Telecomunicaciones (IFT) was extinguished and that the CRT takes over its rights, obligations and powers. LMTR · CRT agreement, Nov 7, 2025Homologation records that name the right authority, and Spanish manuals, labels and app text.

This page is 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.

How an engagement starts

One model, one review, then a written plan

  1. NDA first. Then tell us about the robot: its software stack, where it runs today and what it already holds, such as an FCC ID or an ISED certificate
  2. A short review of one model or one site: we read the code and the update path and capture what the robot talks to on the network. For a ROS 1 move, the workspace scan is free
  3. Written findings, ranked by risk, with the parts that belong to a hardware partner, a lab or counsel marked as theirs
  4. A written plan and quote per service line, with the people on the job named before you sign
  5. Build in your repositories, weekly demos, then handover with a runbook, or we stay on

Before the NDA

  • A short call on the robot, the market and the deadline
  • A check against the restricted lists below
  • No access to code or data until the NDA is signed

Who we do not work for

Makers on the US Entity List, on US or Canadian sanctions lists, or on the US Section 1260H list. We check before the NDA.

Market entry

Engineering here, market entry at Norvoya

DIGI117 builds the software. Norvoya, our front office, handles North American market entry. Robocho, our robotics database and AI, keeps the facts.

Norvoya is Digi117's front office for North American market entry. It plans the entry with you, coordinates the labs, counsel and partners, and reports to you in writing. Digi117 does the engineering.

Visit Norvoya

Robocho (robocho.com) is our robotics database and AI assistant. Robocho is an AI. Ask it first-line questions with the Robocho button at the bottom right of any page; it hands over to a person when you ask.

Checklist

North America robot software readiness checklist: 16 checks, each linked to the regulator's own document. Checked November 2026.

Read the checklist

Built for hardware importers

A market-access lookup for robots and connected devices: search by brand, model or serial, six dated checks per product, five languages, served from the edge.

Read the build

Questions

Do you write motor firmware or safety controllers?

No. Safety-rated control, motor firmware and mechanical design stay with your team or a partner who specializes in them. We build the software around the robot and agree the interface with them in writing.

Do you certify robots?

No. Accredited test labs test and certify, and regulators grant authorizations. We build the software and the engineering records the lab and your counsel ask for.

Is this legal advice?

No. Our pages and our findings describe engineering work and link the official sources. Ask your own counsel before you rely on them.

Our model is already FCC-authorized. What can we change?

That depends on what the change touches. We write down, per release, whether it changes anything reported at certification. Your lab and counsel decide whether it is a Class I or Class II change. Start with the checklist.

Which languages?

English, French and Spanish, in apps, voice prompts, manuals, portals and integrator material.

How long does it take?

The review comes first; the plan after it gives dates per service line, in writing.

Bring one robot model. We start there.

Send the model, the markets and what it already holds. After the NDA, we review it and reply with what we would do first.

Contact us Read the checklist

Reply within one business day · Not legal advice