Who builds this · Bank-grade scope
A core banking system is a promise about arithmetic.
Wynk Systems is built in South Africa, for institutions whose regulator will one day ask where a number came from.
The plain facts
| Fact | Value |
|---|---|
| Registered | South Africa |
| Primary region | af-south-1 (Cape Town) |
| Disaster recovery | eu-west-1 |
| Runtime | TypeScript on Node 24, PostgreSQL 17 |
| Runtime dependencies | None |
How we build
These are not aspirations pinned to a wall. Each one is a rule that has changed what shipped, and each one is written down in the repository where an engineer has to read it before they can merge.
If four review rounds fail, the code gets rewritten
When the same defect class survives three fix rounds, patching stops and the subsystem is re-architected so the invariant becomes structural — an accounting identity the code cannot express a violation of, rather than another guard. Two subsystems have been rewritten under this rule, and both stopped producing findings afterwards.
Review effort is spent by risk, not evenly
Surfaces that move money, mint authority or cross a tenant boundary get adversarial review with independent refuters. Read surfaces get tests and an isolation proof. Spreading review evenly across both is how money paths get the attention a report page deserves.
Merging is not closing
A change lands when it is merged; an epic closes when a full adversarial pass finds nothing new twice in a row. The two are tracked separately because conflating them is how a programme convinces itself it is finished.
A control with no negative test is a rumour
Every invariant carries a test proving it CAN fail — an assertion that holds by construction proves nothing. Where a claim cannot be falsified by a test, the claim does not go on this website.
Deliberately red tests
A test suite here contains failing tests that document known defects with reproductions. Greening one by weakening its assertion is a firing-squad offence; the backlog entry and the test are the same artefact.
What that costs, and what it buys
- It is slower. A subsystem that gets re-architected on its fourth failed review round takes weeks that a patch would have taken hours.
- It produces uncomfortable artefacts. There is a defect backlog with reproductions in this codebase, and some of its tests are deliberately red. We would rather hand you that than a clean board that was cleaned by weakening assertions.
- It means we will tell you when something is in build. Every capability on this site carries a status, and the in-build ones say so in the same typeface as the live ones.
- What it buys is the only thing that matters for a system of record: when the number is wrong, you can find out why.
Talk to a person
Evaluating the platform
Licensed lenders and banks working out whether this fits.
tenants@wynk.systems
Security and assurance
Control evidence, chain attestation, architecture review.
security@wynk.systems
Integration
API questions, migration shape, environment access.
developers@wynk.systems
Wynk Systems is a bank-grade core-banking platform. Registered in South Africa.
This site is informational: nothing on it constitutes an offer, a quotation, or credit advice.