Built to be trusted
The engine carries records that employers, financiers, regulators and courts rely on. Governance is how we keep that reliance earned.
How we protect records and licensees
Data protection
Designed around the Data Protection Act, 2024: purpose-bound access, consent records and human decisions on anything with consequences.
Data residency
Hosting is defined as code, so each solution's data can stay in Botswana where a client or regulator requires it.
Verifiable records
Any ledger can be exported with a tool that proves, outside the platform, that no record has been altered.
Continuity for licensees
Perpetual licences, source escrow and step-in rights mean a licensee's business never depends on a single supplier.
Architecture principles
Every solution is reviewed against these before it is published.
One Solution Contract
A third solution can be added without touching Be or BCS.
The core is never forked
A capability one solution needs is added to the core for every solution.
Shared code, never shared data
Separate deployments, keys and ledgers; consent for anything that crosses.
One name, one meaning
Engines, services and packs carry the same names in code, screens and contracts.
Versioned on its own
Each solution pins a core version and moves to the next one deliberately.