Robots learn now
Learned policies can behave differently after every release.
Approved safety scenarios run on every change: replay first, then simulation, then real robots. Regressions get caught in the pull request, not on the floor.
Learned policies can behave differently after every release.
Manual, physical trials, and weeks to certify one machine.
ISO 10218:2025 and ANSI/A3 R15.08-3 now ask how you control software changes after a robot ships.
A certificate covers one moment. The risk lives in every release.
One incident becomes thousands of tested variations, each tied to the clause it would break.
Checks a certifier recognizes: separation distance, contact force, stopping distance, staying inside the workspace. Real regressions block the merge. Noise doesn't.
foretell / safety — regression found
#1482 nav: tighter cornering in narrow aisles
Every release gets one record, exported for whoever needs it, with a log of every safety decision and sign-off: the change-control trail certifiers, insurers and your customers ask for.
What changed, which scenarios ran and why a change was stopped.
Teams of 10 to 100 engineers. Most start when:

Nothing gets replaced. Your logs and robot software never leave your side; only results do. The dashboard runs in our cloud or yours.
Read-only connections.
No regressions found in the moments we checked, and it says how many that was. Anything we couldn't check, like a gap in the log, an uncertain detection or a moment where the new build drove differently, is marked "not checked", never "passed". Foretell never calls a robot safe; it tells you what was tested.
No. Foretell's own detector finds people, forklifts and obstacles in your lidar, depth and camera data. If you do log your own tracking, we cross-check it, and any disagreement is marked "not checked".
No. An agent drafts scenarios from your incidents and logs, and you start from a library of common hazards mapped to standards. A safety engineer approves each one before it runs.
No. TÜV, UL and exida certify. Foretell produces the release-by-release evidence you bring to them.
No. Replay of your own logs works on day one. Simulation is added for a type of scenario once it has proven accurate for it.
Nothing joins your suite until a safety engineer approves it. Every scenario cites its source log and clause.
We're built around US standards first. Foretell keeps a record and a decision log for every release from day one, so if you sell in the EU once the regulation applies (January 20, 2027), the history is already there. A notified body still does the assessment.
Everything that touches your logs, robot software and simulators runs on your machines. Only results (verdicts and numbers) leave. The dashboard runs in our cloud, or in yours if you need it.
In 30 days they become approved scenarios that replay on every change, with your first release record. No simulator needed.