vesper.dev

Frequently asked

Is this offline programming?

No. Offline programming draws fixed paths for fixed parts. Vesper programs see the scene, so parts and poses can vary.

Is an AI model running the robot?

No. AI writes the program at design time. The robot runs plain, readable code, the same every cycle.

What goes in the spec?

What you would give an integrator: the task, the parts (CAD), cycle time and the acceptance bar.

Which robots does Vesper work with?

Industrial arms, cobots and mobile manipulators, from any brand. We confirm your models in the quick talk.

What happens if something goes wrong mid-shift?

Recovery is tested before anything runs, the robot stays inside its safety limits, and the previous version is ready for rollback.

Which industries do you work with?

Any manufacturing with high-mix work: stations where variation, low volume or frequent change kept automation out.

Do we need our own automation team?

No. We integrate the first station and hand your team the controls: run it, re-task it, then write new specs yourselves.

Who carries the CE marking?

Where a mechanical build is needed, a partner builds the cell and carries its CE marking.

What about the integrator we work with today?

They stay involved: they build the cell, Vesper does the programming.

What data leaves our plant?

Programs run locally, inside your network. What leaves your plant is explicit and under your control. Vesper is built and run in Europe.

When can we start?

Now, with a quick talk and a Floor Walk. Test licenses from January 2027, limited deployments through 2027.

What does it cost?

The quick talk and the Floor Walk are free, so we take five Floor Walks per quarter. After feasibility you get a fixed fee for a one-station pilot.