A small team for work that cannot be got wrong

Senior engineers, in your repository

Every engagement starts with the uncomfortable questions: what happens when this fails, who is accountable when it does, and what will it cost to change in three years. We would rather spend two weeks proving an approach than eighteen months discovering it was wrong — and we will tell you when the honest answer is a smaller system, an off-the-shelf product, or no project at all.

The people who scope the work are the people who write it. You get commits in your own repositories from the first week, decisions recorded where the code can be read against them, and a system your team could hand to someone else without us in the room.

Crypti (Pty) Ltd is based in South Africa and works with clients here and abroad, in a timezone that overlaps most of the working day in Europe, the Middle East and the UK.

Built secure. Owned by you.

• POPIA and GDPR by design

  Consent, retention and the right to erasure are designed into the data model rather than bolted on before an audit. South African law is the baseline; European clients get the same handling without a second build.

• Security in the engineering, not the invoice

  Least-privilege access, encrypted storage, signed short-lived links to private files and an audit trail on every privileged action. Standard practice here, not a line item you have to ask for.

• You own everything

  The code, the infrastructure, the accounts and the documentation are yours from the first commit, in your repositories. No proprietary runtime, no hostage clause, and a handover that a different team could actually pick up.

• Built to be maintained

  Typed end to end, tested where a failure would cost something, and written so the reasoning survives in the code. The measure of the work is what it costs to change in two years, not how fast the demo arrived.