Realtime Robotics is turning motion planning software into a robotic workcell design layer

Realtime Robotics launched Resolver at Automate 2025 on May 12, 2025, targeting one of the slowest parts of robotic workcell deployment: path planning and interlock design. The launch record says manual robot path planning can take more than 100,000 hours for a single complex project. Resolver lets users upload workcell information, configure sequencing and conditions, generate collision-free motion paths and interlock signals, and import results back into simulation software.

Realtime grew out of Duke University work by George Konidaris and Dan Sorin on processor architecture for real-time motion planning. The company's core idea is that robot motion planning should not require weeks of manual programming and collision checking when multiple robots, fixtures, and products change inside a cell.

Resolver supports path planning across any number of robots and works directly inside Siemens Process Simulate. Realtime says the software generates results in minutes, cuts engineering effort by half, and compresses project timelines from months to days. Those are company claims, but they fit the main buyer pain: workcell design is often slowed by expert programming time before the first production cycle is ever tested.

RapidPlan is the runtime and control side of the product family. It generates collision-free paths with automatic interlocks in milliseconds, supports multi-robot motion planning, and can operate as RapidPlan Active with real-time sensor data or RapidPlan Passive as a motion advisor to customer control software.

The public examples are useful because they show the type of complexity Realtime is targeting. The RapidPlan page cites an FFT application with more than 120,000 weld points and four robots in one application, plus a Valiant TMS three-robot application processing 12 product SKUs. Those examples keep the product grounded in multi-robot interference and SKU changeover, not generic robotics software.

The competitive field includes robot OEM programming tools, Siemens and Dassault simulation environments, NVIDIA Isaac, Mujin, Wandelbots, conventional integrators, and internal tooling at large automation companies. Realtime's distinction is motion planning as a design and deployment layer for complex workcells. Public material does not show paid Resolver customer count, deployment retention, achieved cycle-time deltas, imported-path failure rates, commissioning rework reduction, or production uptime after generated paths. If Resolver saves verified engineering hours across commissioned cells, Realtime becomes a workcell design layer rather than only a motion-planning engine.

Have a robotics update Korthos should review? Send news, deployments, product releases, funding rounds, research, or media to tips@korthos.xyz or reach out on X at @agkorthos.