Can be licensed
ERF profiles, .vrm envelope logic, verification rules, class model, review model, and deterministic output behaviour.
Licensable core
Start with proof packs. Expand with a licensed core only when repeated use proves itself.
The public path stays simple: proof packs, templates, and Anchored access. Partner and enterprise licensing exists for multi-client, co-branded, or embedded use around the same core without giving away the full trust authority.
What is licensable
The reusable logic around the proof object — not every operational control.
Stays controlled
Key management, issuance authority, abuse controls, and parts of status or ledger governance remain under Vraimony control.
Best fit
Integrators, partners, and enterprise teams that need multi-client rights, co-branded outputs, or embedded review paths.
License ladder
Move only as deep as the use case requires.
Repeated use by one team with clearer operational rights than the public self-serve path.
Broader repeated use across clients or operating units without opening full partner controls.
Co-branded outputs, multi-client rights, and distribution helpers around the same core.
Custom embedded or policy-heavy use where deployment and control boundaries must be discussed directly.
Boundary
Licensed core, controlled trust.
Licensing never means handing over the entire trust engine. The system stays review-first, facts-only, and narrow. Packs remain the entry path. Licensing only expands how the same core is reused, embedded, or branded.
Start lighter first