Manens Become a design partner

Persistent, dynamic memory for robots

A shared memory of the place a robot works in. It tracks how the place changes, carries over to new models and new robots, and enforces the place's rules.

Become a design partner How it works

Robots start over every day

  • Where things are

    Robots don't reliably remember where things are in a specific warehouse, factory, hospital, hotel or home.

  • The site's rules

    “Aisle 4 is closed until 3pm.” “No robots in Zone B during shift change.” Rules told to a model in a prompt get ignored.

  • Any of it after a change

    A model update or a new robot wipes what was learned about the place.

One memory per place

  • Dynamic

    Tracks where each object probably is, how sure we are, and what changed.

  • Persistent

    Belongs to the site, not the model. Survives model updates and new robots.

  • Enforced

    Checks every step against the site's rules before it runs, and blocks violations.

  • Shared

    Every robot, from any maker, plus cameras and sensors, updates the same memory.

  • Spatial

    A shared map, so a new robot is useful on day one and takes faster routes.

Plugs in beside the planner

Manens is an SDK that sits next to a robot's planner. It never touches model weights or motor control.

  1. 1

    Reads

    What robots and sensors see.

  2. 2

    Serves

    Memory to the planner as simple tools.

  3. 3

    Checks

    Each step before it runs, allow or block, with a reason.

Where Manens sits in the robot stack Four stacked layers, top to bottom: Planner, Navigation, Skill policy (VLA) and Motor control. A Manens block sits to the right, connected to the Planner and Navigation layers. Motor control has no connection and is untouched. Planner Navigation Skill policy (VLA) Motor control not touched Manens plugs in here Where Manens sits in the robot stack Four stacked layers, top to bottom: Planner, Navigation, Skill policy (VLA) and Motor control. A Manens block sits to the right, connected to the Planner and Navigation layers. Motor control has no connection and is untouched. Planner Navigation Skill policy (VLA) Motor control Motor control is not touched Manens plugs in here

A warehouse with mixed robots

  1. Monday

    A supervisor closes aisle 4 until 3pm. Every robot gets the rule.

  2. Monday, 1pm

    A robot is routed through aisle 4. Manens blocks the step and it reroutes.

  3. Tuesday

    A forklift moves a pallet. A camera updates memory, and the next robot goes straight there.

  4. Month 2

    A robot from another maker arrives and knows the site on day one.

We're looking for design partners

We're working with a small number of teams building and deploying robots. If memory, site rules or robot handoff matter to you, we'd love to talk.

Get in touch

Or tell us what you'd need for a pilot.