R Kiwi

About

About R Kiwi

R Kiwi is Robot.com's autonomous sidewalk delivery robot for meals, groceries and small parcels. It uses a wheeled outdoor body, cameras, three-dimensional lidar, onboard computing and remote fleet oversight to travel through campuses and public pedestrian environments.

Robot.com markets the system as a commercial delivery platform with Level 4 autonomy and charging infrastructure. Service availability, operating domain and human oversight depend on the deployment location and local rules.

Capabilities

Source-backed capabilities

  • Workflows: Task execution, platform development, integration testing and robot operation around a defined workflow.
  • Operating environments: Structured robotics environments where the system can be evaluated against a defined task and operating setting.
  • Target markets: Developers, operators, researchers and partners evaluating the product for robotics workflows.
  • Deployment model: Commercial or available product positioned for customer use, integration or developer adoption.
  • Navigation and obstacle avoidance

    Claimed - Robot.com presents R Kiwi for autonomous food, grocery and parcel delivery with remote oversight.

    Source
  • Remote and shared control

    Claimed - Robot.com presents R Kiwi for autonomous food, grocery and parcel delivery with remote oversight.

    Source
  • Cargo delivery

    Claimed - Robot.com presents R Kiwi for autonomous food, grocery and parcel delivery with remote oversight.

    Source

Supply

Supply / Components

  • R Kiwi

    Nvidia Compute For Robotcom R Kiwi - Compute & Control - NVIDIA - Robot.com R Kiwi uses NVIDIA onboard compute - source: robot.com

    Source

Context

Market context

Autonomous sidewalk delivery robot for meals, packages, and small products.

  • Target environment: Structured robotics environments where the system can be evaluated against a defined task and operating setting.
  • Workflow context: Task execution, platform development, integration testing and robot operation around a defined workflow.
  • Customer context: Developers, operators, researchers and partners evaluating the product for robotics workflows.
  • Deployment model: Commercial or available product positioned for customer use, integration or developer adoption.
  • Commercial maturity: Publicly presented as commercial or available, with maturity depending on deployment scale and support coverage.
  • Adoption constraints: Adoption depends on task proof, reliability, integration, safety, support and fit with the target operating environment.
  • Market position: R Kiwi sits in a robotics product lane defined by its operating workflow, maturity and integration needs.
  • Adjacent products: Adjacent systems depend on the robot form factor, autonomy layer and target workflow.

Comparable Systems

Related Systems