01
Your machines
Vespira runs in your environment. Sessions, files, and the systems it calls stay on your side of the network.
A NextGenCodeAI product
The procedure runs here.The agent stays with you.
Vespira runs on your infrastructure. It follows a licensed procedure, calls the tools you connect, and leaves a session you can watch, steer, or stop. Order loading at Compes is the first integration.
In integration with Compes
The client
The panel lives on your machine. Skills, systems, and the model.
The first procedure
The document already contains the order.Someone still types it again.
A PDF arrives. A person opens the system of record beside it and copies the fields across. The queue is the job. The mistakes are quiet.
VESPIRASample run
Running
IncomingPDF · DWG
order.pdf
drawing.dwg
T profile · 80 × 40 mm
System of record
Customer
Order
PO
Line
Shape
Size
Quantity
Unit price
Amount
Delivery
A person checks every field and confirms.
The procedure
Vespira runs the path.A person takes the exception.
Scroll the run. The order on screen is a sample of the shape, not a customer’s numbers.
VESPIRASample run
Running
IncomingPDF · DWG
order.pdf
drawing.dwg
T profile · 80 × 40 mm
System of record
Customer
Order
PO
Line
Shape
Size
Quantity
Unit price
Amount
Delivery
A person checks every field and confirms.
Boundaries
Three things that do not move.
02
Sealed procedures
The instructions we license to you stay encrypted until the run that needs them. A skill points at a procedure. It does not carry the text.
03
A person on the exception
Automation takes the repeatable path. A running turn can be watched, steered, and stopped. Judgment stays with someone.
Runtime
What it is built to do. Not a chat window.
01
Sessions
Every run is a session you can open. A turn in progress is marked, including the tool it is inside.
02
Schedules
The same procedure, on a clock. Monday morning does not wait for someone to press start.
03
Documents and drawings
PDF in the run. Drawings convert when the procedure needs the geometry. Files stay on the machine.
04
Your systems
Connect the software you already operate. The agent calls it. You do not replace the system of record.
05
Local skills
Instructions your team owns, beside the procedures we license. Both are available to the run that needs them.
06
One running copy
A license activates one installation. A second copy does not quietly take the work.
Deployment
In integration
Compes is first.Order loading.
We are integrating Vespira at Compes S.p.A. so orders are loaded by the agent instead of retyped. There is no results board on this page. The procedure is being wired into the operation. When it has numbers, they will be measured.
- The procedure is order loading
- The runtime sits in their environment
- Outcomes come after the integration
A document, a set of rules,and a place it should land.
If a procedure has those three, we can put Vespira on it. Tell us which one still waits on a person.