Contact
Platform overview

One identity record, from enrolment to audit.

Most identity failures happen at the seams — between the system that captured the fingerprint and the system that printed the card, between the card and the reader, between the reader and the report. Biolog removes the seams by holding the whole lifecycle in one platform. The identity captured on enrolment day is the same record that authorises the card, answers the reader at the gate, and appears in the audit log two years later.

Enrolment, photograph and card production on one register — stations free, nobody waiting.
Enrolment, photograph and card production on one register — stations free, nobody waiting.
Five stages

The lifecycle

The identity lifecycle: enrol, issue, verify, account, retire — each stage feeding the next from a single record.01EnrolCapture, quality-check,deduplicate02IssueProduce and encodethe credential03VerifyMatch at the pointof decision04AccountWrite the decisionto the audit log05RetireRevoke centrally,immediatelyOne record. The identity enrolled on day one is the identity in the log two years later.

Stage 1 — Enrol

Biographic data and biometric samples are captured together, quality-checked at the point of capture, and deduplicated against the existing register before the record is committed.

Stage 2 — Issue

The enrolled record generates a credential: a smart card, an RFID card, a printed ID, or a purely digital credential where no card is needed. The credential carries a reference to the biometric record, never a substitute for it.

Stage 3 — Verify

At any verification point, the presented credential or the presented finger is matched against the register. The result is a decision — permitted, refused, flagged — returned in seconds.

Stage 4 — Account

Every decision is written to an immutable log with time, location, device and operator. Reporting turns that log into the answer to whatever question arrives later.

Stage 5 — Retire

Graduation, resignation, expiry, loss. Credentials are revoked centrally and stop working immediately at every reader, without anyone chasing the physical card.

Architecture

Deployed how you need it deployed.

Biolog runs cloud-hosted, on-premise inside your own data centre, or hybrid — central register in the cloud, local verification nodes on site so that a network outage never stops a queue. Where an institution’s policy or a regulator requires data to remain within Nigeria, it remains within Nigeria.

Deployment options: cloud-hosted, hybrid with local verification nodes, and fully on-premise.CloudCentral register hosted by BTS.CLOUD— Register— Console— ReportingON SITEVerification devices onlyNo local registerHybridCentral register, local verification nodes on site.CLOUD— Register— ConsoleON SITE— Local node— Local nodeOn-premiseEverything inside your own data centre.CLOUDnot usedON SITE— Register— Console— Reporting
Let’s build you a solution

See Biolog running against your own process.

A working session with our team, not a slide deck. Bring your enrolment volumes, your verification points and your awkward edge cases. We will show you how Biolog handles them.

Request a demo