Three configurations,
matched to your conditions.
Choose by what you are proving and how far the integration goes.
Standard Standard
Issue proofs against records that already have a fixed format. A verification link and badge can be placed too. If the conditions fit, this is the fastest way to start.
Built around your work Custom
Configured around integration with your existing systems, and on-premises where required.
Built for regulators and auditors Regulated
For work where whoever receives the evidence dictates the format it must take.
The link and badge (verification chip) that point to the verification page are included in Standard.
- The records you are proving have a fixed format (residence certificates, licenses, inspection reports)
- Issuance is triggered from one or two places (a nightly batch, an application form)
- What you present stops at "this is genuine"
If all three apply, Standard is the fastest way to start.
- You are designing your own proofs on your own data
- You disclose selected fields only (selective disclosure)
- Several core systems, or on-premises
- The recipient dictates the format of the evidence
- You embed the verification result in your own screens (iframe)
- Issuance volume is an order of magnitude higher
If even one applies, talk to us about a custom build quote.
The cost does not move however many parties verify, or how often. They do not need an account either.
Lemma receives only a hash; the record itself stays with you. Handing over a proof does not hand over the contents.
Whoever receives it can confirm that you issued it (how your organization name appears is set during onboarding). No one else can issue in your name.
Building or running agents? Start from the Sandbox. The sandbox is free; issuing in production is paid.
Which record, once it carries a proof,
shortens the checking?
In 30 to 60 minutes we design what to prove and how to configure it. You will know on the call whether Standard is enough.