Public Procurement Attestation
Verify supplier eligibility for public procurement via ZK attestations of qualifications, track record, and certifications — buyers confirm compliance, suppliers protect proprietary information.
Who this is for.
You evaluate, supply into, or design the policy for public procurement. Today's verification path forces buyers to take custody of submitted documents and forces bidders to disclose more than the evaluator actually checks. The asymmetry pushes risk in both directions.
-
Procurement leads at municipalities and central-government buyers
-
Procurement-policy designers operationalizing eligibility schemas across multiple tenders
-
Defense and critical-infrastructure suppliers protecting financial, technical, or personnel data while bidding
Hand over the source, or just the facts?
the bidder's raw documents and performance internals
meets the tender's eligibility requirements
The bidder collects per-attribute attestations against its own records: ISO certifications from the certifying body, financial-eligibility attestations from its auditor, track-record attestations against its own work history (or aggregated through an industry registry). Each attribute is signed by the issuer the procurement policy already trusts.
The bid carries a composed ZK proof against the tender's eligibility schema. The evaluator verifies the predicate — "the bidder holds an active ISO 14001 certification, meets the financial threshold for this tender class, and has at least N similar references in the last 5 years" — without ever holding the underlying certificates, balance sheets, or reference letters.
For consortia bids, prime contractors compose sub-supplier attestations the same way they compose their own. The evaluator sees one chained proof and verifies the consortium-level eligibility predicate without scanning sub-supplier records.
Choose on three criteria.
Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-proof |
|---|---|---|---|
| Access control only | △ | ✗ | ✗ |
| Masking / anonymization | △ | ✗ | ✗ |
| Encryption only | ✓ | ✗ | ✗ |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ |
What's next
We enter through adoption support and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify the tender categories and bidder-side document types where the disclosure surface concentrates risk.
- Narrow to 1–2 decisions (results) to prove — e.g. "holds an ISO certification," "meets the financial threshold" — the eligibility predicate the evaluator checks. Not the originals.
- Design connection and issuer trust — issuer onboarding for certifying bodies, auditors, and reference organizations, and per-tender-category eligibility schemas.
- Prove one tender category via a (quote-based) PoC — confirm it works for one eligibility schema.
- Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; the setup and pricing are designed together.
Tell us one tender where the disclosure surface concentrates risk, in the first 30 minutes. No tender documentation or bidder data required.
The bigger picture
The bigger picture this use case belongs to.
We map use scenarios across industries and workflows by the four axes.
See use scenarios for Regulatory Attribute in Solutions →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.