VNTA Robotics · Pricing
Early accessValidation for robot and fleet integrations.
Start with one integration. See what actually works, with the evidence behind every result.
- Limited
Design partner
From €2,500
Ex VAT
For initial production integrations while Validation is being developed.
Become a design partnerIncludes
- One integration
- Structured validation
- Evidence-backed findings
- Technical access and a direct feedback loop
- Discounted early-partner pricing
In exchange for access to a real robot or fleet environment.
Recommended
LimitedValidation
From €6,500
Ex VAT
Independent validation of a robot or fleet integration, with evidence and readiness findings.
Validate an integrationIncludes
- Defined test scope
- Capability validation: declared against verified
- Failure and reconnect behaviour, where applicable
- Evidence capture: calls, messages, timestamps
- Readiness result
- Technical report, with remediation notes
Final scope and price depend on integration complexity.
- Case by case
Larger deployments
Scoped
Priced by agreement
For multiple systems, sites, vendors or custom adapters.
Discuss an integrationIncludes
- Multi-system validation
- More than one adapter or vendor
- Site-specific test scenarios
- Deployment-level reporting
Scoped and priced by agreement, case by case.
Runtime subscriptions will be introduced once repeated use across real deployments has been validated.
Every price is a starting point, shown ex VAT. There is no online payment: scope is agreed before work begins. VNTA validation evaluates software integration behaviour against a chosen set of checks. It is not a functional-safety certification and does not replace manufacturer commissioning procedures.
How we price
Priced around integrations, not robot count.
The value today is in validating an integration before it goes into operation, not in running a fleet day to day. So it is priced by the integration.
Per integration
One robot or fleet system, validated once.
Per deployment
Several systems or sites, validated as one project.
How an engagement runs
Start with one real integration.
Connect one robot or fleet system, agree what will be tested, run the suite, and go through the result together. Nothing is bought with a button.
- 01
Request
Tell us about the robot or fleet system.
- 02
Qualification
We check it is something we can test today.
- 03
Technical review
Interfaces, documentation, access.
- 04
Scope
What will be tested, and how success is judged.
- 05
Proposal
A price for that scope.
- 06
Validation
The work, the result and the evidence.
Technical status
Early accessWhat runs today, and what does not yet.
Validation has been tested against simulated systems and one external VDA 5050 implementation. It has not yet been run against a real robot. We are now taking on our first production design partners. No dates are given, because none are committed.
- VDA 5050 2.1.0 over MQTT, tested against one external virtual vehicle
- VNTA simulated adapters, for trying the suite without a robot
- Capability records: declared, discovered, verified
- Validation suite, evidence and readiness reports
- Runtime API v0: reads capabilities and starts validation. It will change.
- Sending missions through an adapter: inside validation runs only.
- A first real robot or fleet-manager integration
- Runtime SDK
- ROS 2 adapter
- Open-RMF adapter
- Vendor fleet-manager connectors
- VDA 5050 3.0.0
- Access: mission governance
- Identity: machine trust
Questions
Before you ask.
Has Validation been used on a real robot?
Not yet. It has been run against simulated robots and one external virtual vehicle: open-source VDA 5050 software that VNTA did not write. A first project with a design partner is the first contact with a real system, and part of it is writing the adapter for that system. That is why early places are limited and scoped carefully.
What does a validation include?
One agreed integration, a defined test scope, results backed by evidence, a readiness result, and a technical report with remediation notes.
Is this certification?
No. VNTA validation evaluates software integration behaviour. It is not safety, functional-safety or regulatory certification, and does not replace manufacturer commissioning or safety procedures.
Do you charge per robot?
No. Pricing is based on the integration and the scope of the deployment.
Which standards are supported today?
VDA 5050 version 2.1.0, tested against one external virtual vehicle. VDA 5050 3.0, ROS 2, Open-RMF and vendor fleet managers are planned and have no adapter yet. Support varies by protocol and implementation.
Can you test a simulated system?
Yes, where there is an adapter for its interface. Today that means VDA 5050 2.1.0. Testing against a simulator or a vendor test environment first, before any hardware is involved, is the sensible order.
Can you support a custom robot system?
Possibly. Each system needs an adapter. Custom adapters and validation scopes are looked at case by case.
Is the price fixed?
No. Every price here is a starting point, shown ex VAT. The scope is agreed before work begins and the proposal is priced for that scope.
Can I subscribe to a platform?
Not yet. Runtime subscriptions will be introduced once repeated use across real deployments has been validated.
Request
Validate an integration
Tell us about the integration. This is not a checkout: we read every request and reply about technical fit.
- No payment, no card, no automatic sign-up.
- Scope is agreed before work begins.
- Early places are limited, so not every request can be taken on.
Validate one integration before standardising the rest.
Product scope, supported integrations and pricing may change as Validation is used with early partners.