Is RoboDrive AI a robot store, a military / weapons robotics firm, a course, or does it guarantee fully autonomous, human-free operation?
No. We are a robotics engineering studio that designs perception, autonomous navigation and motion planning for mobile robots at client sites, with engineers supervising deployment. We do NOT sell robots off a shelf, do NOT work on weapons, defence or covert-surveillance applications, and do NOT sell courses. “Robo” means applied robotics; “Drive” means making robots move and navigate; the .pro TLD is branding only. Robots are safety-critical, can mis-perceive edge cases, and need risk assessment, safety-standard compliance and human oversight — we do not guarantee full autonomy, zero downtime or complete safety.
What happens during a navigation review?
We start with a scoping call and NDA if needed, then review your maps, bag files, fault logs, and operator procedures. A site visit or remote walk-through follows when practical. You receive a route dossier with prioritised findings, suggested instrumentation, and documentation gaps — not a generic maturity scorecard.
Do you work outside Ontario?
Yes. We serve clients across Canada and select international programmes where time zones and export rules allow. Travel is billed at cost unless bundled in a fixed quote. Remote review is often sufficient for initial diagnostics.
Which robot platforms do you support?
We are stack-agnostic: ROS/ROS2, vendor SDKs, and custom planners are all in scope. We do not require you to switch hardware. Our value is in navigation behaviour, map hygiene, and operational documentation — not brand allegiance.
Can you certify our robots as safe?
No. We support safety case documentation and hazard analysis writing, but certification and regulatory approval remain with qualified assessors and your organisation. See our Terms of Service for limitation of liability.
How do you handle site data and PIPEDA?
Contact form data is used only to respond to enquiries. Client engagement data is processed under contract with confidentiality terms aligned with PIPEDA. See our Privacy Policy for details on retention, access requests, and cross-border processors.
What do engagements typically cost?
Indicative CAD ranges appear on our Services page. Final quotes depend on site complexity, fleet size, and deliverable depth. Retainers are available for ongoing map and release review.
Who owns SLAM maps, perception models and navigation stack outputs?
Ownership and licensing are defined in your statement of work. Client-specific maps, tuned parameters and deployment documentation typically transfer to you upon final invoice; our internal libraries and generic tooling remain ours. Bag files, floor scans and operational telemetry are treated as confidential unless you authorize broader use.
Do you join our on-site pilot shifts?
When scope includes supervised expansion, our leads attend pilot windows to observe hand-offs, capture bag files, and debrief operators. We do not assume remote-control of your fleet or replace your on-call engineering roster.
