Robust.AI

Name: Robust.AI
Brand: Robust.AI

Fully autonomous. Truly collaborative.

Est 2019|Valuation $46M|Raised $42.5M|4 Ref Customers

LinkedIn 15K|Web traffic 3K|FTEs 78|HQ San Carlos, California, US

MarketsRobotics Control Software

Published Aug 20, 2026

01Common complaints

- If you require published security and compliance attestations (e.g., SOC 2, ISO 27001) before engaging: Robust.AI does not publicly document these certifications in a readily verifiable way. - If you require extensive peer-review coverage and transparent, published pricing: Robust.AI has a limited footprint on mainstream review platforms and does not publish standard pricing. - If your organization prefers a vendor with a large, proven installed base at massive fleet scale and minimal risk tolerance: more established AMR vendors may present a lower perceived risk for very large deployments. - If your rollout requires immediate deep WMS/OMS integration and complex orchestration from day one: verify connector availability and implementation timelines before committing. - If your facility environment is perception-hostile (extreme dust, variable lighting, reflective floors) and you cannot allocate time for validation testing.

Deal disqualifiers / poor fit

Highly automated facilities where incremental gains are small
Facilities that require immediate, deep WMS/OMS integration before pilot
Environments with extreme dust, highly variable lighting, or reflective surfaces that challenge camera-based perception without validation

Publicly visible limitations

Limited publicly available technical documentation (APIs, integration guides, security whitepapers) compared with mature enterprise software vendors.
Limited independent user-review footprint, making support quality and uptime harder to validate externally.

Roadmap signals (inferred)

Announcements indicate ongoing productization and planned WMS integration work in partnership deployments, suggesting integration capabilities are maturing but may not yet be comprehensive.

Scale limitations

Public sources do not specify fleet size limits, maximum tasks per hour, or uptime SLAs. These should be validated and contractually defined during pilot and procurement processes.

Why customers might leave / churn (likely drivers; limited direct evidence)

Direct evidence of churn was not found. Likely churn drivers for AMR deployments include:

Insufficient ROI after pilots
Reliability or support issues
Integration roadblocks with WMS/OMS
Vendor viability concerns (hardware vendors require long-term support)

02Why they buy

Unique selling points supported by multiple public sources and vendor materials

Collaboration via physical interaction: Carter and Carter Pro emphasize tactile and force-sensing features that allow workers to move the robot and resume autonomous operation.
Operator-focused adoption messaging: public coverage emphasizes reducing initial facility rework and focusing on worker interaction during deployment.

Unique selling points that are primarily vendor-claimed and require validation

Claims of short-term ROI and vendor-provided productivity guarantees should be validated through pilot measurements and contract review.
Claims of minimal or no infrastructure changes required may be accurate for initial pilots but often require additional integration work when scaling.

Areas where competitors may have clear advantages

Larger reference bases and documented deployments
Broader ecosystem partnerships and integration libraries
Potentially more mature fleet analytics and remote operations offerings (varies by vendor)

03Field reports

Important caveat about review platforms

Robust.AI is not a typical self-serve SaaS product with large volumes of public user reviews, and it has limited presence on mainstream review platforms (G2, Capterra, TrustRadius). In this research, no active product pages with extensive customer reviews were found on these platforms. As a result, public customer sentiment is primarily evident from press coverage, press releases, industry publications, and vendor/partner communications.

Example vendor-attributed testimonials and claims

- Business Wire and other press releases describe productivity claims associated with a deployment for a major logistics provider, including a reported substantial productivity gain within the first weeks of deployment. The underlying measurement methodology is not published in detail by the vendor. - A vendor LinkedIn post quoted a warehouse manager saying: "For the first time, I feel like automation is working with us — not at us." This is a vendor-posted testimonial and should be treated as marketing content. - Trade coverage describes Carter as designed to interpret human body language and allow manual takeover by grabbing the handlebar; this characterization appears in descriptive reporting rather than independent validation.

Negative feedback and criticisms in public discourse

Because Robust.AI lacks broad public review-platform coverage, explicit low-rated reviews are not readily available. Public criticisms tend to be general to the robotics category and to include:

Skepticism about consistent, repeatable ROI across sites
Integration complexity and the challenge of scaling from pilot to fleet
Questions about manufacturing scale and field-service coverage for hardware vendors

Why customers choose Robust.AI (inferred from sources)

Based on vendor messaging and public coverage, customers may select Robust.AI for:

Potentially lower initial facility disruption compared with fixed automation projects
Robots designed for close human-robot interaction and manual repositioning
Solutions positioned for facilities that prefer a subscription or service approach over large upfront capex

Case study 1: Deployment with a major logistics provider (North America site example)

Claimed outcome: Substantial productivity gains within the initial weeks of deployment.

Source type: vendor press release and syndicated announcements.
Critical notes: methodology is not publicly detailed (baseline, measurement window, and definition of "productivity" are absent). Early-phase gains may reflect replacement of high-walking processes and may not represent steady-state improvements.

Case study 2: Strategic alliance with a regional logistics provider

Claimed outcomes: Reported productivity improvements in some deployments; WMS integration planned as part of a phased rollout.

Critical notes: reported improvements vary by site profile and maturity. Planned WMS integration suggests that deeper systems work may be necessary for scaling.

Case study 3: Deployment at a regional fulfillment operator

Vendor communications describe reduced walking time for manual tote delivery and improved throughput following Carter deployments.

Critical notes: benefits are described qualitatively in vendor materials without detailed quantified KPIs (e.g., UPH, picks-per-hour, cost-per-order). Mention of customization (payload capacity changes) indicates potential site-specific engineering work.

04Best fit

Company sizes

Best fit (inferred):

Mid-market to enterprise warehouses and 3PLs that can operationalize robotics
Multi-site operators who can scale a validated pilot

Indicative ranges (practical, not vendor-published):

200–5,000+ warehouse employees across a network
Facilities from approximately 50,000 to 500,000+ sq ft (site suitability depends on pick density and workflow)

Industries / verticals

3PL logistics
E-commerce fulfillment
Retail distribution
Manufacturing material movement

Roles and personas

Decision-makers:

VP/Director of Operations, DC/warehouse leadership
Supply chain transformation leaders
Finance leaders evaluating RaaS vs capex models
IT/WMS owners (if integration planned)

End users:

Warehouse associates (pickers, replenishment)
Supervisors and floor leads

Pain points addressed

High walking time and labor inefficiency in piece-picking
Difficulty staffing and retaining warehouse workers
Need for scalable throughput without major facility rebuilds

05The pitch

What the product does (objective value proposition)

Robust.AI is a warehouse and manufacturing automation vendor that develops collaborative autonomous mobile robots (AMRs) and associated software workflows for pick, put, and transport tasks while maintaining human oversight. Its core product line centers on the Carter (and Carter Pro) robots designed to operate autonomously and to be physically interactive — workers can manually reposition or "steer" the robot via force-sensing hardware and then return it to autonomous operation. Robust.AI describes Carter as intended to operate in close proximity with workers rather than only avoiding them. Key software is branded as Grace, a no-code workflow and fleet coordination suite that supports dynamic coordination between people and robots, workflow configuration, and integrations. Public materials emphasize straightforward deployment and limited initial infrastructure changes, though technical documentation is limited.

Target market & positioning

Robust.AI primarily targets: - Warehousing and fulfillment (especially piece-picking and mixed workflows) - Third-party logistics providers (3PLs) - Manufacturing material handling Positioning themes (as presented by the vendor and public coverage): - Claims of short-term ROI and rapid deployment - Design focused on operator interaction (manual override and tactile interaction) - Flexible, software-configurable workflows intended to allow switching workflows without new hardware

Get a comprehensive analysis of Robust.AI including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →