Built for regulated finance. Open about what comes next.

Live Operational today

Role-based access control

Six roles (CGS Admin, Maker and Checker; bank Admin, Maker and Checker). Every server route checks who is asking, and automated tests sweep them route by route.

Four eyes

Every claim, disbursement and recovery decision, and every application and report the scheme reviews, needs a second person, and the system checks it is a different person, not only a different role. Work completed automatically is sampled by weekly random checks.

Audit trail

Every decision records who made it, when, and the document behind it. Audit entries cannot be edited by the application, the CGS Admin or the vendor. Boards and auditors can see the history of every decision.

Leverage ceiling enforcement

Can be switched on for any scheme. When it is on, approvals are blocked at the leverage ceiling, at the point of approval rather than after the fact, and no user can override it. A decision that would increase the scheme's exposure, such as continuing cover on a restructured loan, goes to the credit committee.

Three-tier settings hierarchy

Platform, scheme and institution-agreement settings are kept separate, so one institution's configuration never affects another's.

Per-loan reconciliation record

Every reconciliation leaves a permanent record for each loan: the scheme's computed figure, the institution's reported figure and the approved settlement basis.

Roadmap Not yet built

Core banking integration

API endpoints and webhooks so institutions' core banking systems can send data automatically instead of through the portal.

Regional and multi-country schemes

Now being introduced: one deployment for a regional body, with each country's scheme kept separate and a Regional Admin allocating capital from the regional fund.

Detailed security documentation is available to evaluators on request.