- If you require mature, independently validated reliability metrics
- Bedrock has trade press coverage and partner-reported operational outputs, but limited publicly available audited performance statistics (e.g., interventions per hour, mean time between failures, or detailed safety-case artifacts). Buyers requiring independently validated operational metrics may prefer OEMs or vendors with longer published deployment histories.
- If you require published enterprise security/compliance documentation
- Bedrock does not publicly document SOC 2 or ISO certifications or an enterprise security feature set. Enterprises with strict vendor security requirements should expect extended due diligence.
- If your projects are small, highly variable, or extremely congested
- Autonomy value is generally higher in repetitive, geofenced, heavy-production scenarios. For smaller or chaotic sites, the setup and supervision overhead may outweigh benefits.
- If you expect a self-serve software purchasing motion
- This product combines operational technology and robotics; adoption typically requires on-site enablement and services.
- If your primary requirement is grade control rather than autonomy
- Machine-control ecosystems (Trimble/Topcon and OEM machine control) may deliver faster ROI with less operational change in grade-control-focused use cases.
- Current limitations acknowledged by vendor / leadership
- Public statements imply scope limitations: the product currently starts with excavators and the vendor controls the approved scope of work, expanding task approvals over time via software updates.
- Features on the roadmap (not yet available)
- Expansion to additional vehicle classes has been discussed but no firm public timelines were provided.
- Scale limitations (at what volume/size does it break down?)
- Not publicly documented. Practical constraints likely include site mapping and updating, changing topography, dust and weather impacts on sensors, and complexities introduced by mixed traffic and safety protocols.
- Security or compliance gaps
- No public listing of SOC 2 or ISO certifications. No public documentation for SSO/SAML/SCIM/audit logs/data residency options.
- API limitations or integration constraints
- Not publicly documented.