VerificationBuilt
Every check, one decision you can replay.
A verification in Aegis is a run: an auditable sequence of steps through a flow the organisation configures, over whichever providers it chooses, settled by an engine that reads no clock and calls nothing. Replay its events and you get the same decision, every time.
Simulation
Runs entirely in your browser.
Send it a person. Watch it decide.
Pick a scenario: a clean run, a provider failing mid-run, an inconclusive match that needs people, or a check the person has not consented to. Beside it, the reasoning says what each step proved.
Scenarios
- Identity documentAuthenticity and data extraction
- LivenessA live person, not a replay
- Face matchThe person is the document’s holder
- ScreeningSanctions and politically exposed persons
- DecisionRecorded with its basis
- CredentialOffered to the person’s wallet
The run’s event stream
- RunOpened · flow version and policy pinned
The reasoning
A person completes every step and every provider answers. What does the run write down, and what does the person leave with?
- Run openedThe run pins the flow version and the policy it started under. A configuration change made from now on cannot alter this decision.
Flows
Configured by the organisation, pinned by the run.
Flows are built from a catalogue of products and versioned. A run keeps the flow version and policy it started under, so changing configuration never changes a decision already in flight.
- Identity and documents
- Document authenticity and data extraction, liveness, face comparison against the document, and one-to-many face search.
- Built
- Screening
- Sanctions, politically exposed persons and anti-money-laundering lists, as steps with their own provider chains.
- Built
- Registries and records
- Bank account, address, phone, company registry and tax checks; credit, SIM-swap recency and knowledge-based questions.
- Built
- Signing and voice
- Digital signing and voice biometrics as steps of a flow.
- Built
- Two layers of configuration
- A platform default and the organisation’s override, each value resolved with a record of where it came from.
- Built
Providers
Many providers. One vocabulary.
Each step can name a chain of providers. Their answers are mapped onto one vocabulary, so an organisation can change provider without changing a single decision rule.
- An answer settles
- The first provider that answers settles the step, favourable or not. Shopping for a better answer is not a feature.
- Failure moves on
- A provider that cannot answer is retried within its budget; when that is spent, the next in the chain gets a fresh budget of its own.
- Exhaustion is policy
- What an exhausted chain means is the organisation’s configured policy, never a hard-coded refusal.
- Isolated workers
- Each provider runs in its own worker with its own credentials. A slow vendor cannot slow the engine or reach another vendor’s secrets.
- Consent before the call
- A provider call is refused unless the person’s consent covers its purpose, and every call that does go out leaves a forensic record.
People
When it needs judgement, two people give it.
The organisation’s console puts every step’s provider evidence beside the step it belongs to, in assigned review queues. A reviewer adjudicates with a reason; a second approver confirms; self-approval is refused.
- Review queues
- Inconclusive results are routed to people by policy, with the evidence laid out step by step.
- Built
- Second approver
- Maker-checker on adjudication, onboarding and sensitive changes; nobody approves their own work.
- Built
- Resubmission
- Ask the person to redo one step, not the whole run.
- Built
- Invitations
- Invite one person or many at once, by email or text, and follow each run as it moves.
- Built
Capture
A journey built for the phone in a person’s hand.
The verification surface is branded per organisation, mobile first, and runs under a strict content security policy. It captures in the browser and keeps the original beside every corrected image.
- Documents
- Edge detection, perspective correction, sharpness and glare checks.
- Built
- Face and liveness
- Guided sessions for a live person and a match to the document.
- Built
- Signatures
- Handwritten signatures on the screen.
- Built
- Barcodes
- The codes printed on identity documents and cards.
- Built
- Voice
- Voice capture for voice biometrics.
- Built
- Credentials
- Present a credential from a wallet through the browser, or by a code on another device.
- Built
- Embeddable
- The same surface as a self-contained package an organisation can place on its own site.
- In progress
Notifications
Told the moment it is decided.
Email, text and signed webhooks. Deliveries retry transient failures, dead-letter what cannot be delivered, and are idempotent per attempt. Organisations register their own endpoints; each signing secret is shown once and stored sealed.
Build on identity that is proven, not assumed.
Aegis is built by Protoworks and offered to partners on request. Tell us what you need to verify, issue or accept, and we will show you the platform running.