What OneView does
OneView is self-hosted software that brings an organisation's identity-verification workflows into one platform. A client can connect different vendors to licensed KYC Sub-modules such as BVN and NIN, call a stable OneView API, and review the resulting verification history in one interface.
For example, an organisation may use Prembly for BVN and Smile Identity for NIN. Its systems call OneView instead of integrating separately with both providers. OneView selects the configured connection, executes the synchronous request, normalises the outcome, and stores the request history in the client's PostgreSQL database.
Designed for client-controlled infrastructure
The client installation handles vendor configuration, local users, roles, activity history, verification requests, and verification results. OneView does not bundle a client database.
OneView's online licensing and update services do not require client users, vendor credentials, identity subjects, raw verification requests, raw results, or client activity records.
Review Data boundary & responsibilities before production use. It describes the strict licensing/release metadata boundary and the client's legal, privacy, retention, access, backup, and support-data responsibilities.
Current scope
- Docker-based single-server installation.
- Externally managed PostgreSQL supplied by the client.
- Local users and role-based access control.
- Online license activation and refresh.
- White-label branding.
- Approved software releases for AMD64 and ARM64.
- Online update checks, a copyable host command, terminal confirmation, and browser progress.
- Synchronous KYC adapter execution.
SSO, asynchronous verification, offline licensing, and browser-applied host updates are unavailable. A host administrator runs the command displayed by the application.
After sign-in, start with the Dashboard for read-only license capacity and local usage, then use the permission-gated administration and verification pages for supported actions.