Questions we hear on the first call

No. RoboFlux is a civilian robotics engineering and integration studio — perception, motion, systems integration and automation-cell / line-flow design with engineers in the loop. We do NOT build weapons or autonomous weapons and we do NOT provide surveillance of people. AI perception can fail and always needs human validation and safety systems; safety-critical work follows recognized standards (e.g. ISO 10218, ISO/TS 15066, CSA), but no one can guarantee zero incidents or a hands-off operation. We are not a consumer robot store or a SaaS product. "Flux" means automation flow; the .pro TLD is branding only.

Most clients begin with a scoped project: feasibility assessment, engineering design, integration, commissioning, and validation. Fixed-scope statements of work define deliverables, milestones, and acceptance criteria. For ongoing tuning — perception retraining, AMR route adjustments, shift-pattern optimisation — we offer monthly retainer arrangements with defined engineering hours and response-time targets.

We do not operate a self-serve platform or sell hours without context. Every engagement starts with a conversation about your line, your existing control architecture, and the constraint that actually limits throughput. The engineers who scope the project are the engineers who commission it.

Scoped automation-cell and systems-integration projects typically range from C$85,000 to C$450,000 depending on perception complexity, number of integration points, and site constraints. Simpler single-cell cobot integrations may fall toward the lower end; multi-cell line-flow rebalance with AMR fleet integration sits toward the upper end.

Retainer arrangements for ongoing engineering support run C$12,000–C$28,000 per month. All figures are indicative for scoping conversations — not binding quotes, not ROI guarantees, and not promises of specific throughput improvements. We provide formal proposals after feasibility review.

After an initial call, we schedule a feasibility session — on-site or at our Niagara Street lab — to observe your line, review existing PLC and ROS infrastructure, and identify the engineering constraint. You receive a scoped proposal with timeline, deliverables, and CAD budget within five to ten business days.

Kickoff includes a shared project channel, access provisioning agreed with your IT team, and a commissioning schedule that respects your production windows. We do not require exclusive access to your floor; we work alongside your operators and maintenance staff throughout.

Every perception pipeline undergoes structured test campaigns before production release. We build test sets from your actual parts under your actual lighting — including adversarial conditions like glare, dust, orientation drift, and partial occlusion. Edge AI classifiers are evaluated against confidence thresholds with documented false-positive and false-negative rates.

Models are version-controlled with retraining triggers defined upfront. Human operators retain override authority at every decision point. We do not deploy perception systems that operate without a human-in-the-loop recovery path.

RoboFlux complies with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). Contact form data is collected only with explicit consent and used to respond to your enquiry. Client production data — images, telemetry, PLC logs — remains under client control and is handled according to project-specific data processing agreements.

We do not sell personal information, build surveillance systems, or retain client production imagery beyond project needs. Privacy requests go to [email protected]. Full details are in our Privacy Policy.

Our safety engineering aligns with ISO 10218 (industrial robots), ISO/TS 15066 (collaborative robots), and applicable CSA standards for Canadian workplaces. We produce risk assessment support documentation, safety circuit descriptions, and test records for your internal safety review.

We are not a certification body and do not provide regulatory sign-off. Final safety approval remains your responsibility as the employer and equipment operator. We make no guarantee of zero incidents.

At every critical decision point. Operators retain teach-pendant access, E-stop authority, and override controls for perception-driven diverters and AMR routing. We design runbooks for human recovery when AI confidence drops below threshold — not silent failover to unvalidated automation.

Commissioning includes operator training on normal operation, format changeover, and fault recovery. Maintenance staff receive parameter change documentation so they can adjust speeds and offsets within safe bounds without calling us for every tweak.

Yes — systems integration is a core discipline. We build bridges between ROS nodes, PLC logic, WMS order feeds, and MES event streams using OPC-UA, MQTT, REST APIs, or the protocols your existing stack already speaks. AMR fleet routing can consume WMS pick priorities; PLC handshakes can trigger MES production counts.

Integration scope is defined during feasibility — we survey your existing interfaces before proposing architecture. We do not replace functioning WMS or MES platforms; we connect robotics into them.

Weekly status updates cover milestone progress, open risks, and upcoming site activities. Engineering deliverables include integration architecture diagrams, I/O maps, perception test results, motion planning parameter logs, and functional safety evidence packages. At hand-off you receive operator runbooks and maintenance guides written for your team — not generic OEM manuals.

Retainer clients receive monthly activity summaries with hours consumed, tasks completed, and recommended next steps.

Scoped projects run under a statement of work with defined deliverables, acceptance criteria, payment milestones, and change-order procedures. Retainer agreements specify monthly hours, response-time targets, and renewal terms. All contracts are governed by Ontario law — see our Terms of Service for general conditions.

Intellectual property for custom engineering work is assigned per contract terms — typically to the client upon final payment for bespoke integration code, with RoboFlux retaining rights to general-purpose libraries and methods developed prior to the engagement.

We do not build weapons or autonomous weapons. We do not deploy surveillance of individuals. We do not sell robots off a catalogue or act as an OEM distributor. We do not offer certification, regulatory sign-off, or legal compliance advice. We do not guarantee ROI, specific throughput percentages, or zero-incident operations. We do not provide consumer-facing products or self-serve SaaS platforms. We do not accept engagements where the primary purpose is replacing safety personnel with unvalidated automation.