Skip to main content
Client sign inRead API docs
Ghana-first identity infrastructure

Verify people.
Protect evidence.
Explain every decision.

DAJU gives organisations one secure platform to orchestrate consented identity checks, private evidence, human review, and auditable outcomes—starting with Ghana.

Start in the sandboxExplore the API
  • Hosted verification
  • Client operations
  • Versioned API

Live providers remain disabled until their contractual, security, and operational gates pass.

A verification you can follow

Verification session

Customer onboarding

Sandbox
  1. Consent capturedPurpose and version recordedComplete
  2. Evidence protectedPrivate, time-bound accessComplete
  3. 03Identity checksSandbox provider simulationIn progress
  4. 04Explainable outcomeHuman review when requiredWaiting
Session activity recordedDJ-7X42
Tenant-isolatedAccess follows verified membership
Private evidenceTime-bound and access-audited
Human-reviewableFour-eyes controls where required
Auditable by designVersioned outcomes and history

The DAJU platform

Identity infrastructure built as one coherent system.

Move from a verification request to an explainable outcome without losing the consent, evidence, security, and human context around it.

Orchestration

One flow for every verification journey

Compose versioned workflows, collect purpose-specific consent, and issue one-time hosted sessions without coupling your application to a single provider.

Evidence

Keep sensitive evidence out of everyday operations

Documents and selfies stay in private storage. Access is least-privilege, time-bound, and recorded for investigation.

Decisioning

Know why a decision was made

Risk signals, trust assessments, evidence, and final decisions remain separate, versioned, and explainable.

Manual review

Put human judgment where it matters

Route exceptions into least-evidence queues with assignment, escalation, appeal, QA, and four-eyes approval controls.

Developer platform

Integrate once, then grow

Create sessions through a versioned API, use idempotent requests, inspect correlation IDs, and configure signed webhook and retry foundations while outbound delivery remains gated.

Privacy operations

Carry privacy obligations into the workflow

Manage retention policies, legal holds, verified data-rights requests, deletion jobs, and cryptographic completion receipts.

How it works

From workflow to outcome in four clear steps.

DAJU keeps the journey simple for your team while preserving the controls needed for sensitive identity operations.

  1. 01

    Configure

    Create an application and publish a versioned verification workflow.

  2. 02

    Invite

    Create a one-time hosted session for the person being verified.

  3. 03

    Verify

    Collect consented evidence and run only the configured checks.

  4. 04

    Decide

    Return an explainable outcome or route the case to human review.

One operational workspace

See the decision, the controls, and the work still to do.

The client workspace brings verification activity, review attention, workflows, developer controls, privacy operations, and audit history into one tenant-isolated view.

This is an illustrative sandbox view. It demonstrates product structure, not production activity or customer data.

Designed for high-trust journeys

Meet customers where opportunity begins.

DAJU is designed for organisations that need proportionate identity assurance without turning every customer into a compliance case.

Each use case must still be configured against the organisation's legal basis, risk appetite, and approved live providers.

01

Regulated onboarding

Design customer due-diligence journeys with clear consent, evidence boundaries, and reviewable outcomes.

See the integration path
02

Marketplace trust

Give platforms a repeatable way to verify participants without spreading identity evidence across operational tools.

See the integration path
03

Workforce verification

Coordinate identity checks and exceptions for staff, contractors, and distributed teams.

See the integration path
04

Digital-service access

Add proportionate identity assurance to high-trust account and service journeys.

See the integration path

Developer platform

Build the journey. Keep the controls.

Create hosted verification sessions from your server, correlate every request, and prepare outcomes through a versioned API with signed webhook and retry foundations. Outbound delivery remains gated until an approved transport is enabled.

  • Server-side API credentials
  • Idempotent session creation
  • Rate-limit and correlation headers
  • OpenAPI and TypeScript SDK foundations
Open developer docsView integration templates
create-session.shSandbox
curl -X POST \
  https://daju-mocha.vercel.app/api/v1/verification-sessions \
  -H "Authorization: Bearer $DAJU_API_KEY" \
  -H "Idempotency-Key: onboarding-123-v1" \
  -H "Content-Type: application/json" \
  -d '{
    "workflowId": "your_workflow_id",
    "externalReference": "customer-123"
  }'
201 CreatedX-Correlation-Id: cor_••••7f2

Security and privacy

The identity layer should reduce risk—not relocate it.

DAJU treats the browser as untrusted, derives tenant access from verified membership, and keeps privileged operations behind explicit permissions and recent authentication.

Visit the privacy centre
Defence in depthControls applied across the platform
  • Tenant access derived from authenticated membership
  • Forced row-level security on tenant data
  • Private, time-bound evidence access
  • Recent MFA for selected high-risk actions
  • Four-eyes approval for high-risk review
  • Append-only operational audit history

DAJU does not claim external certifications or live-provider readiness until those controls are independently verified.

Ghana first

Built from local realities, designed to extend responsibly.

DAJU begins with Ghana-issued identity documents, Ghanaian contact patterns, and a country-adapter architecture intended to support future markets without flattening their differences.

Implemented adapterGhanaAdditional countriesNot yet claimed

Implementation questions

Clear answers before your first workflow.

DAJU separates what is available in the sandbox from what still requires live-provider and operational approval.

Read the API quick start
Can my team use DAJU today?

Your team can use the sandbox application, hosted verification journey, client workspace, API foundation, and deterministic provider simulations. Live identity and biometric providers remain disabled until their separate contractual, security, privacy, and operational gates pass.

Does evidence appear throughout the client dashboard?

No. DAJU keeps identity documents and selfies in private evidence storage. General workspace views use operational metadata. A permitted reviewer must request short-lived, purpose-bound access, and that access is recorded.

What happens when automation cannot decide?

The workflow can route the case to manual review. Review operations support assignment, priority, SLA tracking, escalation, independent countersign, appeal, and quality assurance without treating an inconclusive result as an approval.

Is DAJU available outside Ghana?

The implemented country adapter begins with Ghana. The platform architecture is designed to add other countries without assuming their identity systems, legal requirements, or document conventions are the same. Additional country coverage is not yet claimed.

How do developers integrate?

Server-side applications create verification sessions through the versioned API and redirect the person to a one-time hosted journey. Idempotency, correlation IDs, request logs, OpenAPI documentation, SDK foundations, and signed-webhook controls support integration and investigation.

Start with the sandbox

Build your first verification flow with clear boundaries.

Explore the API foundation today. Move to live providers only after the required provider-specific and operational gates pass.

Read API docsClient sign in