Digital onboarding for banks,
start to finish, online.
A guided application, KYC and compliance captured at source, and a back-office review workflow — one white-label digital onboarding platform that takes business, personal, group and joint applicants from first form to a live account, without the paper.
Paper account opening loses applicants and hides risk.
A form that emails a PDF to a branch is not a digital account-opening process. The applicant cannot see progress, the bank cannot see the applicant, and compliance happens on a photocopy after the fact.
Three years later, when the auditor asks what the applicant actually saw and declared, the answer has to be reconstructed.
- Half-finished applications nobody follows up
Applicants stop at a hard question or a missing document with no draft to come back to — and no one knows they left.
- Compliance captured after the fact
PEP and FATCA declarations and beneficial owners are collected on paper and typed in later, so screening starts after the account exists.
- Every circular is a release cycle
A new regulation, product or segment changes the form, and changing the form means an engineering ticket.
- The record does not match what the applicant saw
Forms change, but old applications are stored against whatever the current form happens to be.
What changes when the whole journey is one record.
Autosave, resume-anywhere drafts and a private progress link — for business, personal, group and joint applications alike.
PEP and FATCA declarations and the beneficial-owner register are part of the application; every person involved is raised for screening and signed off by a compliance officer.
A visual form builder with maker-checker publishing and version pinning — no code, no redeploy.
An append-only log with before-and-after values, and applications that re-open on the exact form version they were filled on.
Digital onboarding and KYC, captured once and reviewed on a clock.
Digital onboarding is more than an online form. BAOS covers the journey banks are asked to digitise — the application, the KYC and due-diligence capture, the document checklist, the screening queue and the staff review — for business, personal, group and joint applicants alike.
Identification details, employment or business particulars, addresses, next of kin and contact data are captured on your published form, with the fields your KYC policy requires marked mandatory.
Declarations are part of the application itself, made by the applicant before an account exists rather than typed in later from paper.
Business applications record significant stakeholders; group and joint applications repeat a full section for every member or holder. Each person becomes a screening subject.
IDs, photos, registration certificates and resolutions are collected against the checklist for that kind of account, with per-holder slots so “complete” means complete for everyone.
Every person involved is derived into a screening queue with a coverage status. A compliance officer reviews and clears each subject before the application can be approved.
Staff work the application through a six-stage workflow with SLA timers on each stage, record the account number once it is opened in your core system, and leave an append-only log of every action.
Evaluating digital onboarding solutions? Read build, buy or configure, the KYC onboarding process step by step, and the full account-opening guide library.
Business, personal, group, or joint — one platform.
The applicant's first step is choosing the kind of account. Your bank enables only the kinds it offers — each ships as a starter form you publish from the form builder — and every one of them runs the same six-stage review.
The full corporate journey, from entity profile to facilities.
Individual accounts, captured completely the first time.
Chamas and savings groups, with every member on the record.
Every holder captured as a person in their own right.
One review workflow for all of them. The applicant chooses the account kind, BAOS serves the right form, and compliance screening covers every person involved — members, holders, signatories, and stakeholders.
Everything opening a bank account needs — in one flow.
Not a form that emails a PDF to a branch. A complete pipeline: the applicant applies, compliance runs in line, and your team reviews and approves on a clock.
The applicant picks the kind of account — business, personal, group, or joint — and gets the step-by-step form your bank published for it, with autosave and resume-anywhere drafts.
Applicants register and sign in — using your own customer identity service if you have one — keep a list of drafts they can resume or discard, and track progress by a private reference link that cannot be guessed.
Uploads are driven by your checklist, with their own slot for each signatory, beneficial owner, or group member. Staff verify them one at a time or a whole application at once.
PEP and FATCA declarations and the beneficial-owner register are captured inside the application. The applicant and every person involved — directors, beneficial owners, group members, joint holders, signatories — are raised for screening, then cleared by a compliance officer before approval.
Board resolutions for companies, group meeting resolutions for chamas, operating mandates and survivorship for joint accounts — with authorized signatories and signing mandates captured and validated in the same flow.
A six-stage pipeline routes each submission through compliance, document verification, internal review, and approval with role-based queues.
Per-step SLA clocks flag breaches in real time, and every action is written to an append-only audit log.
Every question, section, and helper text can carry English and Swahili, edited in the form builder's translation editor — and applicants get a switcher wherever a translation exists.
Buy it on Azure Marketplace and run it in your own Azure subscription, or install it in your own datacenter. Same product either way.
Two sides, one application.
The customer picks the kind of account — business, personal, group, or joint — and fills in the guided form your bank published for it. The nine steps below are the Kenya corporate standard template, and every one of them is yours to change. Behind the glass, every kind of application runs the same six-stage review pipeline: assigned, screened, verified, and approved.
Change the form without changing the software.
Account-opening forms move — a new regulation, a new product, a new segment. In BAOS that is an afternoon in an admin console, not a release cycle. Build the form visually, publish it under four eyes, and the next application picks it up.
Drag fields from the palette onto the canvas and set their properties on the right. Twenty-two field types, from declarations to repeating people lists — no code, no redeploy, no engineering ticket.
Every published version is immutable, and each application pins the version it was filled on — so an old submission always renders exactly as it was.
A form cannot be published by whoever last edited it. Separation of duties is enforced by the platform, not by policy.
Show or require a field based on earlier answers. The same rules are evaluated identically in the browser and on the server.
Per-field English and Swahili translations, edited in a dedicated translation editor, with a language switcher that appears only where translations have been provided.
Define a pick list once — industries, business types, currencies — and reuse it across every form and step.
Serve a different form by account kind, channel, business type, product, or segment, with a tenant default sitting behind it.
Publishing is blocked on duplicate questions, empty steps, dropdowns with no options, and rules pointing at a field you removed — so a broken form never reaches an applicant.
Walk your draft form through the same screen the applicant will see, before anyone else does.
Configured questions map onto the proper fields of the underlying record — entity name, signatory, shareholding — so reporting and downstream systems keep working, however you rearrange the form.
Export a finished form and import it into another tenant or environment. A form proven at one institution becomes the starting point for the next.
Open drafts by step, measured against submissions — so you can find the question that is costing you applications.
Ten starter forms across all four account kinds ship with the platform, drawn from real account-opening forms in use across the region — including the Kenya corporate standard, the nine-step journey shown above.
Nearly forty prebuilt sections — beneficial owners, member registers, next of kin, signatories, FATCA, board resolutions, and the rest — to drop into any form, grouped across nine areas.
One application, every service it touches.
No re-keying between systems. The customer portal feeds a single application record that flows through compliance, documents, SLA monitoring, and audit — and arrives at account creation complete and validated, ready to hand off to your core banking system.
Self-service sign-up, draft autosave, and reference-token tracking — the only surface the applicant sees — so an applicant can stop, come back and finish without calling the branch.
The single source of truth: the entity or the person, members, holders, signatories, facilities, and mandate — all on one record, so nothing is re-keyed and nothing is lost between teams.
PEP and FATCA declarations and the beneficial-owner register, with the applicant and every person involved raised for screening, and a compliance decision plus overall status attached to the application — so approval cannot run ahead of screening.
Checklist-driven upload, download, and verification — one document at a time or a whole application at once, including signatory photographs — so the reviewer works a complete file, not a trickle of attachments.
Per-step timers start automatically, surface on-track and breached counts, and escalate by role — so a stalled application is somebody's problem before the applicant gives up.
Every workflow action is logged immutably; applicants and staff get an in-app notification inbox and templated emails at each transition — so everyone knows where the application stands, and the record proves it later.
Your brand, your products, your rules.
One codebase serves every institution as an isolated, white-label tenant. Configure it from an admin console — no engineering — and the application, emails, and customer portal all wear your brand.
For applicants who would rather just talk.
An assistant that walks an applicant through the same application in conversation, and gives your reviewers an early read on the documents. It ships with the Enterprise plan, and it is deliberately built so that it can never make the decision.
Applicants who would rather talk than fill in a form are walked through it in chat, with interactive cards for choosing a product, completing a section, making the PEP and FATCA declarations, uploading documents, and confirming a final summary.
Those cards are generated from your own published form for the kind of account being opened — with prompts tuned per kind, so a personal applicant is never asked about board resolutions — and stay in step whenever you change the form.
Recognises seven common Kenyan document types, reads the key details, and deterministically cross-checks them against what the applicant typed. The reviewer sees an advisory flag — never an automatic decision.
There is deliberately no tool for submitting, verifying, or approving — those actions do not exist for the assistant. It is rate-limited, capped in how far it can go on its own, and treats document text as untrusted. A person still decides.
Built to survive an audit.
Onboarding is where a regulator starts asking questions. The platform is built so the answers are already recorded rather than reconstructed.
from applicant and reviewer to compliance officer, branch manager, and auditor — eighteen fine-grained permissions, enforced on every request
an append-only log of who did what, when, from which device and address — with before-and-after values — kept for the life of the application
encrypted sessions, protection against cross-site request forgery, and identity re-checked by every service — not just at the front door
each institution's data lives in its own database schema, and within it staff only ever see the applications for their own branch
automated tests that drive the full applicant and staff journeys in a real browser, plus checks that keep the screens and the services in step
the whole environment is defined as code and packaged for Azure Marketplace, so a rebuild is a rerun rather than a rediscovery
Two ways to deploy. One platform.
Buy it on Azure Marketplace and have it running in your own subscription, or install it in your own datacenter. The same microservices and the same customer portal run in both — the choice is about where your data lives, not what the platform can do.
Plans start at $1,500 per month — see the plans below. The plan price covers BAOS management and support; the Azure infrastructure it runs on is billed separately, on your own subscription.
Sized, installed, and supported with your infrastructure team — including data-residency and network requirements set by your regulator.
The plan fee covers BAOS management and support; Azure infrastructure is billed separately on your subscription.
Prices as listed on Azure Marketplace. Azure infrastructure is billed separately — typically $40–80 per month for entry deployments, and $500–900 per month for a high-availability Enterprise configuration, plus model usage for the AI assistant.
| Capability | Microsoft Azure | On-premises (Kubernetes) |
|---|---|---|
| Relational data | PostgreSQL Flexible Server | PostgreSQL |
| Messaging / events | Azure Service Bus | RabbitMQ |
| Document storage | Azure Blob Storage | MinIO |
| Identity | Microsoft Entra ID (staff) · Azure AD B2C (customers) | Keycloak |
The customer portal runs on App Service, as a static site, or in containers. The Standard and Professional plans install the App Service option; the Enterprise plan runs on Container Apps with autoscaling — the mode that hosts the AI assistant.
Frequently asked questions.
Yes. BAOS is a digital onboarding platform for account opening. Applicants complete your bank's published form online; KYC and due-diligence data, PEP and FATCA/CRS declarations and significant stakeholders are captured at source; documents are collected against a checklist; every person involved is raised for screening and cleared by a compliance officer; and staff review and approve the application against SLA timers, with every action in an append-only audit trail. It covers business, personal, group and joint accounts, is white-labelled per brand, and deploys in your own Azure subscription or on-premises.
Whatever your published form asks for. The starter templates capture identification details, contact and address data, employment or business particulars, next of kin, the directors, shareholders and beneficial owners behind a business, the members of a group and every holder of a joint account, plus PEP and FATCA/CRS declarations — with document slots for IDs, photos, registration certificates and resolutions. Your team adds or removes fields in the no-code form builder without a software release.
Four: business and corporate, personal (individual), group — including chamas and savings groups — and joint accounts. Choosing the account kind is the applicant's first step, and each kind gets the application form your bank published for it. You enable only the kinds you offer — every kind's starter form ships as an unpublished draft — and all four run through the same six-stage review workflow.
Yes. The visual form builder lets product and compliance teams design steps, sections, questions, show-and-hide rules, and document requirements with no code, starting from ten bank starter templates and a library of nearly forty prebuilt sections. Forms carry English and Swahili translations, publishing is maker-checker — the last editor can never approve — and every published version is pinned, so older applications always render exactly as they were submitted.
PEP and FATCA declarations and significant stakeholders are captured inside the application itself. BAOS then derives a screening subject for every person involved — directors, beneficial owners, group members, joint holders, and signatories — tracks each one in a screening queue with coverage status, and a compliance officer reviews and clears them before the application can be approved.
The assistant ships with the Enterprise plan, which deploys the Azure Container Apps hosting it needs. It walks applicants through your bank's own published form in conversation, tuned to the kind of account being opened, and pre-checks common Kenyan documents against what the applicant entered so reviewers get an early advisory flag. It has no ability to submit, verify, or approve anything — those decisions stay with your staff — and it runs on Claude through Azure AI Foundry or on Azure OpenAI, inside your own subscription.
Yes. The same eight .NET microservices and customer portal run on Kubernetes in your own datacenter, with PostgreSQL, RabbitMQ, MinIO, and Keycloak standing in for the Azure services at feature parity. On-premises deployments are sized, installed, and supported by Creodata as an implementation engagement with your infrastructure team.
Three plans are listed publicly on Azure Marketplace: Standard at $1,500 per month for a single brand; Professional at $3,500 per month for up to three brands, with Microsoft Entra ID staff sign-on, Azure AD B2C customer identity, and 24x5 priority support; and Enterprise at $6,000 per month with unlimited brands, the AI assistant, and 24/7 priority-1 support. The plan fee covers BAOS management and support; Azure infrastructure is billed separately on your subscription — typically $40–80 per month for entry deployments. On-premises deployments are priced per engagement.
See any account opened end to end.
We'll walk you through the applicant journey, the form builder, and the review pipeline — across business, personal, group, and joint accounts, branded as your institution. Or deploy it yourself from Azure Marketplace today.
More on account opening
Bank Account Opening Software: What It Is, What It Does, and How to Choose It (2026)
A practical guide to bank account opening software — what a modern account opening system does across business, personal, group and joint accounts, how digital onboarding works end to end, and the checklist banks should use to choose one.
KYC Onboarding in Banks: The Step-by-Step Process (and Where It Breaks Down)
How KYC onboarding actually works in a bank — the data captured at account opening, who must be identified and screened, the review stages that follow, and the failure points that turn a ten-minute application into a two-week wait.
What Is a KYC System? Core Components, Data Captured, and How Banks Use One
A KYC system is the software backbone of customer due diligence — this guide explains its core components, the data it captures at onboarding, how it differs from an AML platform, and what to look for when evaluating one.