Quran Edge API was born from a simple need: lightweight, accurate, and fast access to the Holy Quran in a developer-friendly format. What started as a personal project by Rio Astamal to create a static Quran reader for his Blackberry Passport has grown into a modern edge-delivered API serving developers worldwide.
Tracing the provenance and accuracy of the Quran Edge API dataset. Original dataset authored by Rio Astamal.
Arabic text, Indonesian translations, and Tafsir are sourced from the official application of Kementerian Agama Republik Indonesia.
quran.kemenag.go.idThe dataset is loaded and indexed inside a Cloudflare D1 SQL database using Drizzle ORM schemas and seeders, optimizing direct querying and search.
Arabic text includes full diacritical marks (harakat) following the Uthmani script standard. Each ayah preserves the original encoding from Kementerian Agama Republik Indonesia.
Indonesian translations and Tafsir Kemenag RI are included for every ayah, providing comprehensive meaning and scholarly interpretation.
How Quran Edge API delivers sub-15ms responses worldwide through edge infrastructure.
Users and applications send HTTP requests to the Quran Edge API domain.
Requests hit the nearest Cloudflare edge node. Edge-cached API responses are served directly from Cloudflare KV caching namespace.
Dynamic pages and API routes are rendered on Cloudflare Workers using the OpenNext adapter for Next.js, running full server-side rendering at the edge.
If cached KV is a miss, requests are dynamically queried against the serverless D1 (SQLite) SQL database at the edge, and results are cached.
The people and organizations behind Quran Edge API.
Rio Astamal
Original Dataset Author
Twinpath
Edge API & Web Application
Want to contribute?
We welcome Pull Requests for translations, bug fixes, and feature improvements.
Open a Pull RequestStart integrating accurate Quran data into your application today. Free forever, no API key required.