AffixIO vs KYC database
KYC stacks establish who someone is in systems of record. AffixIO evaluates whether a specific request meets policy and returns signed allow or deny. The two complement each other. AffixIO does not replace your KYC vault.
At a glance
- AffixIO role
- Signed allow or deny at action boundary
- KYC role
- Identity establishment and retention
- PII at verifier
- Zero by default on AffixIO path
- Audit artefact
- Cryptographic proof + Merkle reference
- Integration
- Thin API layer beside existing KYC
AffixIO vs a KYC database compares a verification boundary that returns signed outcomes with a system of record that stores identity files. AffixIO sits beside KYC, not instead of it.
Side by side
| Dimension | Traditional / incumbent | AffixIO |
|---|---|---|
| Primary purpose | Identity establishment | Allow or deny at action |
| Data retention | Long-lived KYC files | No standing profile at verifier |
| Integration model | Centralise or replace stacks | Thin layer beside stack |
| Audit evidence | Document copies and access logs | Signed proof references |
| Post-quantum | Depends on incumbent | ML-DSA-65 (FIPS 204) |
| Typical buyer | Compliance and onboarding teams | Engineering and programme delivery |
When AffixIO fits
- You need a binary gate before payment, agent action, or programme access.
- Every vendor querying KYC expands breach surface and GDPR scope.
- Auditors need replayable evidence, not another document warehouse.
When KYC fits
- You must establish identity for the first time with regulated onboarding.
- Law requires retention of source documents in your jurisdiction.
- You need ongoing relationship management tied to identity records.
Frequently asked questions
Does AffixIO replace our KYC provider?
No. AffixIO consumes eligibility inputs from systems that already own identity. It returns signed allow or deny at the boundary.
Can AffixIO work without copying KYC files?
Yes. Zero-knowledge circuits can prove policy predicates without exporting underlying records to every integrator.
What do auditors receive?
A signed outcome with Merkle-anchored reference. Not a duplicate identity file.