Skip to main content
Qirtaas follows an open-core model: the editor SDK is open source (MIT), and the content backend is available either self-hosted or as a managed service. The frontend code you write is the same in both cases — only the apiUrl and who operates the backend differ.

Comparison

Self-hostManaged Cloud
Editor SDK + Arabic RTL✓ Included✓ Included
Content backendYours, or our imageHosted for you
AuthSelf-managedAPI key + embed token exchange
Quran / hadith content updatesYou pull updatesAlways current
Image storageYour S3-compatible storageStorage included
SupportCommunityEmail & priority
PriceFree (MIT)Paid — sustains the waqf

When to self-host

Choose self-host if you need full control of data residency, want to run the backend inside your own infrastructure, or are building against a custom implementation of the /v1 contract. Start with Self-hosting.

When to use the cloud

Choose managed cloud for zero backend maintenance: hosted content APIs, maintained Quran/hadith datasets, and included image storage. You mint embed tokens from an API key — see Authentication.
Qirtaas is a waqf project by the Alrimaal team. Revenue from managed plans keeps the editor free and open for students of knowledge.