Skip to main content
A compliance instrument · Est. Riyadh

The quiet architecture of Saudi regulatory trust.

Every notice from ZATCA, GOSI, HRSD, Balady and MOCI — routed, read, and resolved inside one system your auditors can follow backwards through time.

MK-01 / SERIES-A — MAKYN mark
  • ZATCA
  • GOSI
  • HRSD
  • BALADY
  • MOCI
  • Integrated as one continuous record
The problem · I.

Compliance in Saudi Arabia is not one system. It is seven.

  • ZATCA sends notices by email.
  • GOSI sends them through Absher.
  • HRSD publishes them to Qiwa.
  • Balady issues them city-by-city.
  • MOCI routes them through the CR dashboard.

An accounting firm managing fifty clients receives between 180 and 400 of these notices every month — each in a different inbox, each with a different deadline format, each demanding a different action. Something is always about to be late.

The instrument · II.

MAKYN is a reading machine.

It watches every channel the Kingdom's authorities use to communicate with your organization. When a notice arrives — in any of them — MAKYN reads the Arabic, extracts the deadline, the amount, the referenced entity, and the required action, and places it on one record.

That record is the same whether you manage one company or one hundred. It is the same whether the notice is about a VAT return, a Saudization ratio, a municipal permit, or a commercial registration renewal.

Every action taken against that record is signed and timestamped. Every document is retained. The audit trail is not a feature of the product. It is the product.

Principles · III.

Four principles MAKYN operates by.

  1. 01

    Sovereignty of data

    Every record produced by MAKYN is stored within the Kingdom, on infrastructure licensed by the Communications, Space and Technology Commission. Your data does not cross borders.

  2. 02

    Legibility over automation

    MAKYN does not file on your behalf. It prepares every notice so clearly that a qualified officer can act on it in under two minutes, and so auditably that a regulator can reconstruct the decision three years later.

  3. 03

    One ledger per organization

    A firm managing one hundred client companies sees one hundred ledgers, each independent, each controlled by its own permissions. What happens inside a ledger stays inside that ledger.

  4. 04

    Arabic as the source of truth

    Every notice is processed in the language it was issued in. English is a convenience layer on top. The legal record is Arabic, timestamped, unmodified.

Who this is for · IV.

Built for three kinds of organization.

  1. 01

    Accounting firms managing ten or more clients.

    Where the volume of notices has crossed the threshold at which spreadsheets fail and nothing replaces them except a dedicated compliance associate whose job is checking inboxes.

  2. 02

    In-house compliance and finance teams at mid-sized Saudi groups.

    Where the CFO owns the relationship with ZATCA, the HR director owns Qiwa, the GM owns the municipal files, and no single person has the complete picture.

  3. 03

    Group holdings with subsidiaries across multiple sectors.

    Where each subsidiary has its own CR, its own commercial obligations, and its own set of recurring authorities — and the group needs a consolidated view without dissolving the subsidiary boundaries.

MAKYN does not replace your compliance officer. It gives them their time back.

The difference between an officer who spends eighty percent of their week reading notices and twenty percent acting on them, and an officer who spends twenty percent reading and eighty percent acting, is the difference between a firm that reacts to the regulator and a firm the regulator reacts to.