AffixIO: privacy-preserving verification infrastructure with ML-DSA-65 attestation

Q: What is AffixIO?

AffixIO is verification infrastructure for privacy-preserving eligibility checks. You prove locally, AffixIO verifies on api.affix-io.com, attests with ML-DSA-65, and can anchor Merkle audit digests. Personal data stays with you.

Q: Why is AffixIO post-quantum technology?

Production attestation uses ML-DSA-65 per NIST FIPS 204. Eligibility receipts are signed so they remain meaningful as classical public-key algorithms are retired.

Q: Where does AffixIO sit in a stack?

Beside age gates, KYC workflows, OAuth/OIDC, agent tool routers and edge kiosks. AffixIO answers binary eligibility; existing systems keep authentication and source records.

Q: Are Claim Desk and PQC Gauge free to try without an API key?

Yes. Both are browser-only AffixIO open labs. Production prove and verify still require keys from hub.affix-io.com.

Q: Which SDK should I install?

Install @affix-io/sdk for local UltraHonk zero-knowledge prove. Install @affix-io/sdk-light for millisecond AffixIO Light proofs on edge devices. Both default to https://api.affix-io.com.

Q: Is AffixIO a PII warehouse?

No. Your host holds source records. AffixIO returns binary outcomes, attestation and Merkle digests without retaining personal data on the default verify path.

AffixIO

Conceptual contour field representing an AffixIO claim becoming signed eligibility evidence. Not a cryptographic implementation.

Verification infrastructure

Prove eligibility. Keep the record.

AffixIO lets your systems prove and verify eligibility while keeping source records with the systems that already hold them.

Explore the system Open Claim Desk Read the documentation

Local prove · Remote verify · ML-DSA-65 attest

A claim resolving into evidence. Conceptual visualisation.

A binary answer, with evidence attached.

Your host proves. api.affix-io.com verifies. Production sync attests with ML-DSA-65 (FIPS 204). Optional Merkle audit anchors digests. AffixIO is not a default PII warehouse.

How a check moves

Four stages. What stays with you, and what AffixIO needs to return a result.

Remains with you

The source record stays on the customer host.

On the path

A claim is named: circuit, predicate, threshold, context.

01. Source record

Your system keeps the underlying record.

02. Local prove

Generate the proof or lightweight result on your host.

03. Remote verify

AffixIO checks the eligibility result.

04. Attest

Production sync adds ML-DSA-65 evidence.

Your host keeps the records.

AffixIO returns the verification result and evidence your downstream systems need. This reduces unnecessary movement of identity attributes. Digests, identifiers and proof material still travel where the protocol requires them.

Source records, documents and identity attributes remain in customer systems.

Customer systems

Source records
Document store
Identity provider
KYC provider
Policy engine

AffixIO

Claim digest
Local prove
Verify
ML-DSA-65 attest
Optional Merkle audit

Outputs

eligible: true / false
subject_ref
Signed evidence
Audit digest

Beside the stack you already run

AffixIO does not replace the IdP or the KYC vendor. It answers eligibility.

Age policy engine keeps thresholds. AffixIO returns the binary gate.

Customer side

AffixIO layer

Output

Instruments, in the browser

No API key. Example values never leave this page unless you copy them. Production prove still needs keys from hub.affix-io.com.

Claim Desk

Canonical claim, SHA-256 digest, opaque subject_ref. Do not paste real personal data.

Canonical claim: (empty)
SHA-256 digest: (empty)
subject_ref: (empty)

Ready to hash locally.

Full Claim Desk

PQC Gauge

ECDSA P-256 is compact. ML-DSA-65 is larger. AffixIO uses ML-DSA-65 for production attestation so eligibility receipts remain checkable as classical public-key schemes are retired.

ECDSA P-25664 B

ML-DSA-653309 B

Open PQC Gauge · NIST alignment

Evidence designed for longer-lived verification.

Designed for post-quantum security. Production attestation uses ML-DSA-65. This is not a claim of guaranteed future-proofing, FIPS 140-3 validation, or a CMVP certificate.

ML-DSA-65 and FIPS 204

AffixIO signs production eligibility outcomes with ML-DSA-65 per NIST FIPS 204. Signatures are larger than ECDSA. The trade is for evidence that can still be checked as classical algorithms are migrated away from.

SDK Enterprise and SDK Light

@affix-io/sdk proves locally with UltraHonk over bundled Noir circuits. @affix-io/sdk-light uses AffixIO Light HMAC on ordinary hosts. Both sync to api.affix-io.com. AffixIO still attests with ML-DSA-65.

Optional Merkle audit

Merkle leaves bind claim digests. The enterprise SDK documents client batches up to 50,000 digests. Leaves do not require the underlying personal fields.

Harvest-now, decrypt-later

Long-lived eligibility receipts signed only with classical algorithms may need to be re-signed later. AffixIO attests with ML-DSA-65 today. No timeline here is a prediction of a cryptanalytic break.

Two packages. One API.

Local UltraHonk zero-knowledge proving with bundled Noir circuits. AffixIO verifies, signs with ML-DSA-65, and can anchor Merkle audit.

npm install @affix-io/sdk

@affix-io/sdk

Documentation npm API reference Examples

What the platform returns

Binary eligibility

eligible true or false for the selected circuit. Applications gate on that result.

How it Works

Local prove

UltraHonk on the enterprise SDK, AffixIO Light HMAC on sdk-light. Proof generation stays on your host.

SDKs

ML-DSA-65 attestation

Production sync signs the outcome per FIPS 204 so evidence can travel with the decision.

Security

Optional Merkle audit

Digests can be anchored without reconstituting personal fields on the default path.

Edge Audit

Build verification into the systems you already run.

Open a lab, read the flow, or sign in to the hub.

Explore the labs Read the documentation Access the hub