We build for the regulator, not the user.
Every design decision inside MAKYN was made by asking one question first: could a regulator, three years from now, reconstruct what happened here?
Operating principles · I.
- I.
The record precedes the interface.
Most software is designed interface-first. The database is a consequence of the interface. This produces pretty tools whose records are incomprehensible to anyone who wasn't there when they were made.
MAKYN was designed record-first. We wrote the schema for an auditable compliance record before we drew a single screen. The interface is a window onto the record. The record would survive a hundred UI redesigns. Three years from now, when a regulator asks what your officer did on a particular Tuesday, the answer is not a screenshot. It is the record.
- II.
Arabic is not a translation.
Saudi compliance correspondence is issued in Arabic. Every English version is a derivative. Every system that treats English as primary and Arabic as translated creates a legal fiction — because the binding document is always the Arabic one.
MAKYN stores the Arabic notice as the canonical record. The English presentation is a convenience. When your counsel asks for the authoritative source, they get the Arabic PDF as it was issued, with a hash proving it has not been altered since receipt.
- III.
Restraint is a feature.
We do not automate filings. We do not interpret law. We do not give compliance advice. We do not predict audit outcomes. We do not send notices to the authorities on your behalf.
These are not missing features. They are deliberate absences. Each of them is the seam where a product crosses from giving a qualified officer leverage to replacing them. We do not cross that seam, because the moment a compliance product crosses it, the product — not the officer — becomes the entity a regulator holds responsible. That is an insupportable business, and we will not build it.
- IV.
The audit trail is the product.
Every MAKYN record is signed at creation, signed at each modification, and timestamped by an independent source. When you export a record, you export a cryptographically verifiable document.
We provide, to every customer, a monthly attestation: a single signed file listing every record created that month, every action taken against it, and every hash. This file, saved by your finance office, is the record of record. If our service disappeared tomorrow, those attestations would still be legible, verifiable, and admissible.
MAKYN is built by a small team based in Riyadh. Our founders have backgrounds in Saudi financial services, regulatory operations, and engineering. We have deliberately not listed names and photographs on this site. When you request a demonstration, you will meet the person who will be responsible for your account. We would rather that introduction happen in a meeting than on a page.