vesper.dev

How Vesper works

From your spec to a running station, in four steps.

Specify. Prove. Release. Deploy.

  1. 01Specify
    In
    The spec you'd give an integrator
    Out
    A digital twin of your cell
    Your engineers
  2. 02Prove
    In
    The twin and a certified safety envelope
    Out
    A program, tested on thousands of variations
    Vesper
  3. 03Release
    In
    The program and its evidence
    Out
    A versioned release, logged to your MES
    Your QA
  4. 04Deploy
    In
    The release
    Out
    Runs locally in the cell, rollback ready
    Your operations

Line 1 goes down. The robot moves to conveyor 3.

A change on a running line
  1. Production engineer

    Line 1 is down until Thursday. Feed conveyor 3 from the same trolley.

  2. Vesper AI

    Program adapted. 1,200 picks in the twin, all inside the safety envelope.

  3. Conveyor 3 sits 20 cm higher. Moved the place pose and proved it again. Release v4?

  4. Released.

  5. Live at shift start. v3 kept for rollback.

Conveyor 3 · v4 in the twin

Both examples are illustrative.

Physical AI. Boring in production.

At design time: AI
  • Sees parts in any pose
  • Handles variation in parts and packaging
  • Writes the program
  • Tests thousands of variations
At run time: boring
  • Plain, readable code
  • Same result every cycle
  • Inside the certified safety envelope
  • No model guessing on the line

Any robot brand.

Your programs carry over when the hardware changes.

Fixed automation

Classical cell, one task

Vesper runs on

Industrial arm or cobot

Mobile manipulator

Dual-arm robot

Reliable as a robot. Flexible as a person.

Keep it manual
Fixed cell + integrator
Vesper
Variation in parts and poses
Operators adapt
Fixtures and jigs
Sees the scene
A product change
Retrain staff
A new project
A new spec
Who changes the program
Not applicable
The integrator
Your own team
Safety and CE
Workplace rules
Recertify after changes
Designed for CE