VCode is licensed technology. There are eight ways to take it, from proving one use case to embedding the capability inside your own product. Commercial terms are agreed per engagement, so there is no price list here, but you should be able to tell from this page which conversation you are starting.
If you are not sure which applies, start a pilot. It is the cheapest way to find out whether VCode solves your problem, and it is how most enterprise deployments begin.
Enterprise VCode
Who it is for: organisations deploying VCode as an identification layer across a business unit or the whole company.
What you get: licensed use of the symbology and platform at agreed volumes, code issuance and management, the rules engine, scan history, and a commercial agreement that covers your deployment rather than a single project.
How it integrates: through the platform API and, where you are reading codes inside your own application, the SDK.
VPlatform API
Who it is for: teams that want to create, manage and resolve identifiers programmatically.
What you get: API access for code generation, rules, actions, packages, scan resolution and history, documented against the VPlatform Client API.
How it integrates: server to server. See the developer documentation.
VCode SDK
Who it is for: product teams who need scanning and resolution inside an application they already own.
What you get: the ability to read and resolve VCodes in your own app, so your customer stays in your experience rather than being sent to a generic scanner.
How it integrates: SDK access is provided to approved partners.
OEM and embedded
Who it is for: manufacturers and platform vendors building VCode capability into another product.
What you get: the right to embed VCode identification within your hardware or software product, with the commercial and technical terms that go with distribution.
How it integrates: agreed per product, typically SDK plus API.
White label
Who it is for: businesses delivering VCode-based functionality under their own brand.
What you get: the capability presented as part of your customer proposition rather than as a third-party tool.
How it integrates: API and SDK, with branding and customer ownership agreed in the licence.
High-volume serialization
Who it is for: manufacturers issuing individual identities across large product populations.
What you get: code generation at production volumes, with each item individually addressable and each identity carrying its own rules and history.
How it integrates: API-driven minting as part of the production or packaging line.
Technology partnership
Who it is for: companies building a sector-specific platform on top of VCode.
What you get: a commercial relationship rather than a supplier arrangement, with the technical access needed to build a proposition of your own in ticketing, brand protection, documents, logistics or another vertical.
How it integrates: agreed jointly, including integration documentation and technical support.
Pilot
Who it is for: anyone who wants evidence before committing to an enterprise deployment.
What you get: a bounded deployment against one real use case, with the rules that matter to you configured and the scan history to show what actually happened.
How it integrates: the smallest integration that proves the point, usually API only.
Where to start
Procurement and security questions are answered on the Trust Centre, and Company sets out who holds the technology.
Four conversations cover almost everything:
- Start a pilot if you have a use case and want proof.
- Discuss an enterprise deployment if you know the scale and need terms.
- Request developer access if you want to read the API and build against it.
- Discuss licensing or partnership if you are embedding, white labelling or building a sector platform.
Not sure which one you need?
Describe the problem rather than the product. We will tell you which route fits, or that VCode is not the right answer.