There is no "6-8 week" deployment. That figure is not accurate.
If you've seen a "6–8 weeks" claim anywhere — on our website, in a chat response, or elsewhere — that is outdated information and does not reflect how we scope deployments. We do not promise a fixed deployment timeline. Anyone who has told you otherwise was working from old content.
Here is the accurate position: deployment timelines are scoped per facility, per project. There is no standard number.
Why there's no fixed timeline
Deployment duration depends on your specific facility — its size, complexity, the type of robot being deployed, hardware procurement lead times, and how your operation is structured. A small single-floor warehouse is a different project from a large multi-zone industrial campus with outdoor perimeter requirements. Giving every client the same number would be dishonest.
The phases — and what drives the time in each
Phase 1 — Facility scanning (1–2 days on-site)
We conduct a point cloud scan of your facility. Non-intrusive, your operations continue. Duration is driven by facility size.
Phase 2 — Simulation build (weeks, not months)
We convert the scan data into a physics-accurate facility model in NVIDIA Omniverse. Happens entirely on our infrastructure. Complexity scales with facility size and environment variety.
Phase 3 — Robot training (variable)
Training in NVIDIA Isaac Sim. Duration depends on task complexity and how many edge cases need to be covered. This is compute-intensive work done on our cloud — it does not require your facility.
Phase 4 — Hardware procurement (often the longest phase)
Robot hardware has lead times that depend on the specific platform and vendor availability. This is frequently the phase that determines the overall timeline — and it's one we'll flag clearly and early in the proposal.
Phase 5 — On-site commissioning (days, not weeks)
Because the robot arrives already trained for your environment, physical commissioning is fast. This is where simulation-first genuinely saves time compared to traditional deployment — what used to take months on-site now takes days.
What this means in practice
Traditional robotics deployment involves 6–12 months of on-site calibration. Our approach compresses the on-site phase significantly. But the total end-to-end timeline — including hardware procurement — is scoped per project and quoted in your proposal. We don't make promises we can't keep.
You'll get a realistic timeline in your scoped proposal, and we'll be honest if something is likely to take longer.