Quranic Universal Data

البيانات القرآنية الشاملة

The Quran as one connected data model: text, every riwayah, edition, script, layout, mapping, and metadata—exact to source, checked, versioned, ready for every layer and app.

Website coming
stage
Beta
fields
Computational linguisticsVariation graphsScript and typography engineeringCompressionTextual scholarshipData engineeringAPI design
8
riwayat, from 4 readers
78%
of the text shared by every riwayah
4.5 MB
one asset, all eight riwayat
1.1 MB
Hafs on its own
+0.4 MB
for each riwayah added
100%
of every source rebuilt exactly, hash-verified

Format v1, 2026-08-12. Counts refresh with every release.

What is broken today

  • A copy per riwayah, a copy per appEvery riwayah is its own file, fixed by hand, unversioned. The same edition in the same script differs by source on whether a word is one or two. Nothing reconciles them.
  • Photographs for a mushafPage images by the hundreds of megabytes: one riwayah, one print, nothing to select, search, scale, or read aloud, and no way to touch a verse, a line, or a word.
  • Every layer keyed its own wayTafsir, translations, morphology, timings: each carries its own copy of the text and its own keys, nearly always Hafs. None attaches to another riwayah. Each new file redefines everything, and drifts.
  • Fifteen resources, one appAn app pulls a dozen files for a dozen jobs. They repeat each other, they disagree, and the user downloads the overlap.
  • Differences live in booksWhere the riwayat differ, by word and by letter, sits in printed works and a few hardcoded sites. No one place answers the question for a whole surah.
  • Silent changeA source fixes a letter; nobody hears. Apps ship stale text for years. Nothing is versioned, nothing is hash-checked, nothing notifies.

One model. What it lets you do

Every riwayah, one textEight riwayat from four readers, held as one text that branches only where the readings differ.
  • Exact to the sourceEvery edition comes back from the one asset byte for byte. Verified on every build, hash-checked on every read.
  • Checked before it shipsSources arrive unchecked. Here every edition is compared with every other, down to whether a word is one or two, before it enters the model.
  • One model, everything on itTranslations, tafsir, morphology, timings, notes anchor to the text, not to a copy of it. No schema per file, no text repeated, no drift. Every layer lands on the right verse of the right edition.
  • Words and verses that mapAny word or verse in one riwayah points to its counterpart in another, including verses that split or number differently.
  • Pick your riwayat, get one assetOne file for whatever you choose. Each riwayah adds a sliver, each layer adds only its own data. Not fifteen resources that repeat each other.
  • A native mushaf under 10 MBFonts, prints, pages, juz and hizb, several riwayat, in the asset. Text you select, search, scale, and read in the dark. Touch a verse, a line, a word. No photographs.
  • Differences you can queryWhere any two riwayat differ, by word and by letter, counted, listed, drawn, for a verse or the whole text. What lived in books becomes data every app and every student can ask.
  • Search everything, onceOne index over one model: text without diacritics today; morphology, meaning, and recitation phenomena as they land. Every layer searched together.
  • Recitation in stepUniversal Audio timings anchor to the same letters, so every recitation aligns to every riwayah, and a clip of a word is a lookup.
  • Nothing to decodeAsk for a verse, a page, a word, or a mapping and get it. The schema stays inside; the library and the API answer.
  • A closed loopEvery reference holds across releases. A source fixes a letter: the asset rebuilds, says what changed, and tells the apps that carry it.

Where we are, where we are heading

Where this goes: one model of the text, and everything about the Quran living on it. Pages, meanings, recitation, history. Under one roof, under ten megabytes.

  1. History and manuscriptsHistorical rasm and manuscripts as editions of the same text, with the scholars of the field.
  2. The riwayat not yet digitalWith the authorities and scholars who hold them, the readings no provider has typed enter the model. Sacred whether read by millions or by few.
  3. Recitation linkedUniversal Audio timings anchored to the same letters.
  4. Search across every layerText, morphology, meaning, and recitation phenomena from one index.
  5. Morphology and meaningRoots, forms, and senses anchored to the letters, so a difference in reading explains its difference in meaning.
  6. Differences, typed and certifiedEvery variation site named by what it is: imala, silah, idgham, hamza, a word read otherwise, with the sound and the tajweed that go with it. Reviewed formally and signed off by scholars of the qira'at before it ships.
  7. Access, grown upA full API and SDKs for every platform, online, offline, or both. Fast, reliable, no rate limits.
  8. Fonts, compacted and justifiedEdition fonts share one base, as the text does: one file, every riwayah's shapes, no string rendering differently. Lines justify as the printed page does, in the footsteps of Digital Khatt.Digital Khatt
  9. Pages for every riwayahThe lines and pages of the other riwayat' prints exist only in print. We read them off the page with OCR and computer vision. A field open to contributors.
  10. Prints and pagesMadani and IndoPak layouts, juz and hizb, in the asset: the native mushaf. Hafs first, because its pages exist as data.
  11. Production schemaThe smallest release that holds: one versioned model fixed and published, with a library and an API to read it.
  12. 2026Lab prototypeRiwayat, editions, orthographies, and font layouts projected onto one another.