Verification infrastructure

Get the answer.
Keep the data.

AffixIO tells your systems yes or no. Proof runs on your side. We attest the result and keep an audit trail. Personal data does not come with us.

  • Zero-KnowledgeProve locally when you need full ZK
  • Post-QuantumML-DSA-65 on every production sync
  • StatelessNothing retained from the verify path

What you get

The pieces security and engineering teams actually connect.

01

Binary verify

Send an identifier and a circuit. You get eligible true or false. Optional signed material if you need it. data_retained stays null.

02

Circuit policy

The circuit decides what you are checking: age, KYC, voting, health, finance, education. You pick the rule. Affix runs the check.

03

ML-DSA attestation

Production sync needs Affix ML-DSA-65 (FIPS 204) on the payload. That is the bar for a signed result you can keep.

04

Merkle audit

Digests land in an Affix-compatible Merkle tree. Leaves stay with their attestation so you can reconcile later.

Read the platform overview

Node.js SDKs

Two packages, one API. Pick the proof model that fits the device and the risk.

@affix-io/sdk

Enterprise SDK

Local UltraHonk zero-knowledge prove with bundled Noir circuits. Affix verifies, signs with ML-DSA-65, and anchors Merkle audit.

npm install @affix-io/sdk

@affix-io/sdk-light

SDK Light

Millisecond Affix Light proofs for phones, kiosks, and ordinary hosts. Affix still attests digests with ML-DSA-65 and Merkle audit.

npm install @affix-io/sdk-light

How it works

Your data stays put. Affix returns an attested outcome.

Step 01

Prove on your host

Call @affix-io/sdk or @affix-io/sdk-light. You work with claim hashes, not raw records.

Step 02

Verify and attest

Sync to api.affix-io.com with your API key. Affix returns an ML-DSA-65 attestation.

Step 03

Keep an audit trail

Digests enter the Merkle trail. Offline queues flush when the network returns.

See the full flow