FATHOM / Industries / Government & Public Sector
Public-sector platforms carry obligations commercial sites can ignore: Arabic as a first language rather than a translation, WCAG accessibility as a requirement rather than a nice-to-have, and data that stays on infrastructure you control. That happens to be exactly how we build everything — self-hosted, RTL-first, accessibility in the definition of done.
01
Designed in Arabic from the first wireframe with English as the parallel track — not an LTR site mirrored as an afterthought.
02
Accessibility review is part of every build before launch — screen readers, keyboard navigation, contrast, and graceful degradation.
03
Self-hosted content systems on infrastructure in your jurisdiction — no third-party SaaS holding public data as a dependency.
Enterprise platform track
from AED 35,000
Multi-entity content federation
+ AED 19,500
Additional language (engineering)
+ AED 2,750 / language
All anchors come from the public Scope Estimator on our homepage — configure your exact scope there and the math stays the same.
Yes — scoped statements of work, security documentation, SLAs in the contract, and AED invoicing are standard for our Enterprise track. Bring the tender requirements to the scoping call.
No — WCAG 2.2 AA review is part of every build we ship, public sector or not. What scales cost is scope and integrations, not whether disabled users can use the site.
Book a strategic architecture call — or run the estimator and send us your pre-filled scope.