Mithaq is board governance software that BHD Group builds in Muscat. It keeps a board's agenda, papers, minutes, decisions, actions and audit history in one Arabic and English workspace. A board can run it in the cloud, on its own domain, or on servers it controls.
Why I wanted it
I have worked inside board processes since 2023. I am Board Secretary at DataOm, ITHCA Group's submarine cable company. I also sit on the board of the Oman Fencing Committee. In both seats, the meeting is the easy part. The hard part is the record that comes after it.
A board makes a decision. Weeks later, someone asks who decided it, on which paper, and with what quorum. The answer often sits across an email thread, a Word file and a chat. An action gets assigned, and then nobody can say who owns it. The Arabic minutes and the English minutes drift apart.
I wanted one place where the evidence for a full board cycle stays connected.
What Mithaq keeps together
Mithaq links each step of a governance cycle. The agenda leads to the meeting papers. The meeting records attendance and quorum. The minutes hold the decisions and the votes. Each decision can create actions with a named owner and a due date. The audit log records every later change.
The interface works in right-to-left Arabic and in English. Arabic content is part of the board record itself. A buyer should test the minutes and the outputs in both languages, and not only the language switch.
Beyond the board portal, Mithaq covers four areas that large suites also sell: contracts, entities, matters and a dataroom. All five areas share one role matrix and one audit log.
One backbone for many kinds of board
A sport federation, a hospital board and a bank board need the same core. Each one holds meetings, makes decisions, keeps documents and needs an audit trail. Their agendas differ a lot. Mithaq loads modules by sector. A federation sees athletes and selections. A bank board sees a risk register and an audit committee. The site lists fifteen sectors today.
Where it runs
Many boards in Oman and the GCC must know where their data lives. Mithaq has three deployment paths. The first is hosted SaaS. The second is a custom domain on the hosted service. The third is a single-tenant on-premise mode, with a Docker Compose setup and local signed-licence checks.
On-premise does not automatically mean air-gapped. Offline operation depends on the network, identity, backup and update design. We write those requirements down with the buyer before we commit to a deployment.
One customer, named in public
The Oman Fencing Committee is the first tenant. It runs its board workspace and its public site at fencing.om on Mithaq. Anyone can open that site and check the relationship.
That is the full customer list today. An early version of the Mithaq site carried two five-star quotes. Both were invented, so we removed them. The site now states only what a reader can check. A board product asks for trust, so its own website must earn that trust first.
What building it taught me
Board software looks simple from outside. The difficult part is the links between records. A decision must point back to its paper and forward to its actions. Without those links, the product is only a nicer folder.
Our ERP has the same design rule: one record for each job, and no copy and paste between systems. Mithaq applies that idea to governance. The evidence for one board cycle stays connected, and not spread across unrelated files. That costs more work at the start. It pays back when the questions come later.
Mithaq is still young. It has one public customer and a clear list of things it must prove next. I want it to grow on records that people can check.
Related: Why we built our own ERP instead of buying one, Board KPIs that a board can actually use