Robotics · R-01

Launching robots in the US and Canada? Bring the software with you.

For robot makers from Asia, Europe and Canada. A robot that sells at home still needs North American cloud and data handling, apps and documents in English, French and Spanish, an update service, a portal for the integrators who install it, and engineering records for the approval file. Digi117 builds the software. Norvoya, Digi117's front office for North American market entry, handles the market side.

  • EN, FR, ESapps, documents and portal
  • Local cloudUS or Canadian regions you control
  • Evidencelabs certify, counsel advises
  • 16 checkseach linked to its official source

Talk to an engineer Read the checklist

What changed

What the FCC changed for robots in 2026

Each line is from the FCC's own documents. Checked November 2026.

Robots on the Covered List

On July 28, 2026, the FCC added foreign-produced advanced robotic devices to its Covered List (DA 26-786). The FCC fact sheet describes them as mobile robots such as humanoids and quadrupeds.

Authorized models stay on sale

Models the FCC already authorized can still be imported, sold and used, according to the same fact sheet. An authorized model is the asset; software work on it has to stay inside what its authorization covers.

New models need a Conditional Approval

A new model needs a Conditional Approval from the US Department of War before it can be authorized. The software side of that file is a parts list with makers and origins, and records of what the software does.

Updates keep flowing until at least 2029

DA 26-789 lets authorized devices keep receiving software and firmware updates at least until January 1, 2029, under the conditions the order sets. Content rules also apply; your counsel reads them, and we prepare the records they work from.

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.

What we build

The launch kit, built in your repositories

Six pieces, quoted one by one after a review of one model. Most launches need four or five of them.

Local cloud and data handling

We capture the robot's network traffic and list every host it contacts and the country it sits in, then repoint each one to US or Canadian regions you control. You get a data map per field: what is collected, where it goes and how long it stays.

Apps and documents in English, French and Spanish

App screens, voice prompts, setup guides and manuals moved into resource files and translated, with units, dates and number formats per locale. French and Spanish reviewed by people who speak them.

An update service

Signed packages, staged rollouts and rollback, with release notes that say whether a build changes anything reported at certification. Signed software updates has the detail.

An integrator portal

API reference, a sandbox with simulated robots, setup guides and training material, and accounts for the dealers and integrators who install and service your units.

Evidence for content rules and the approval file

A bill of materials down to each board, module and controller with its maker and origin, a software change log per version, and answers to the lab's software questions. We prepare records; we do not certify and we do not give legal opinions.

A console for your first customers

Live status, alerts and uptime reports from day one, so the first sites in a new market are watched from the start. See the fleet console.

How it starts

One model, one review, then a launch plan

  1. NDA first. Then the model list and what each model already holds: FCC ID, ISED certificate, or neither yet
  2. A review of one model: we run the 16-point checklist, capture its network traffic and read its update path
  3. Written findings, ranked by risk, with the parts that belong to a lab, counsel or Norvoya marked as theirs
  4. A written plan and quote per piece, 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

Who does what

  • Digi117: the software and its engineering records
  • Norvoya: market entry, partners and the coordination of labs and counsel
  • Accredited test labs: testing and certification
  • Your counsel: legal opinions and filings
  • You: decisions, keys and the final say on every release

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 labs, counsel and partners, and reports to you in writing. Digi117 builds the software the launch needs.

Visit Norvoya

Free checklist

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

Read the checklist

Questions about a North America launch

Do you file the FCC or ISED application?

No. Accredited labs test and file with the regulator, and your counsel advises. We build the software and the engineering records they ask for: parts lists, change logs, data maps and answers to software questions.

Who handles distribution, partners and the market plan?

Norvoya, Digi117's front office for North American market entry. Digi117 does the engineering, and both report to you in writing.

Which markets does this cover?

The US and Canada. The checklist also covers Mexico, if it is next on your list.

Our robot already runs a cloud at home. Do we need a second one?

Usually not a second product, but often a second region. We list every host the robot contacts, then repoint the ones that need to move and test the change on real units before rollout.

Is this legal advice?

No. We describe engineering work and link the official sources. Ask your own counsel before you rely on any of it.

Bring one robot model. We start there.

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

Contact us Visit Norvoya

Reply within one business day · Not legal advice