Skip to content
The Bayanat Labs product families

Arabic datasets for
the AI you’re building.

Bayanat Labs (Riyadh) supplies Arabic AI data in nine product families: 30,000 hours of Arabic speech, 2,700 Arabic books, 400,000 STEM Q&A items and 200,000 MSA NER sentences to license, plus custom collection, annotation and evaluation drawing on a team of 50,000+ expert annotators, the largest in the Middle East, across 25+ Arabic varieties.

اقرأ بالعربية

What you can verify on this site

For each family: what is confirmed now, and what we send on request. We never show a sample that has not been cleared for publication.

FamilyConfirmed on this siteOn request
Bayanat VoiceHours per collection; Transcripts and delivery schemaSpeakers, dialect mix and collection dates; Recording source; Audio format and sample rate
Bayanat KnowledgeCounts per collection; Edited MSA coverage and rightsTitle, publisher and subject lists; Token counts; NER label taxonomy and span rules
Bayanat Voice StudioStudio Prompt Speech counts; Saudi Expressive Speech; Open inspection kit (text only, not a sample)Expressive collection size and speakers; Prompt-to-speaker mapping; Recording setup and audio format
Bayanat AlignLicensable alignment sets; Record types; Ties and reviewer disagreementSample records, rubric and reviewer decisions; Dialect and register mix
Bayanat AgentsLicensable trajectories; Research methodSample trajectory
Bayanat BenchLicensable evaluation sets; Held-out separation; Published researchSample report
Bayanat DocumentsSource handlingExample of the label format
Bayanat SearchRelevance scale; Hard negatives; Unanswerable questionsSample judgments and reviewer reasoning
Bayanat VisionReal and generated images; People in imagesExample of the label format

What to include in a data request

A clear request gets you to the right collection or a scoped pilot faster.

  1. The task: what the model must learn or be tested on, and the modality (speech, text, documents, images or video).
  2. Existing or custom: whether a licensed collection could work, or the data needs to be built around your product.
  3. Language coverage: Arabic varieties, register, mixed Arabic-English, and where your users are.
  4. Volume and format: hours, records or pages, file formats, and the schema your pipeline expects.
  5. The uses to license: training, evaluation, retrieval, display, redistribution or synthetic voice, each named separately.
  6. How you will decide: the sample or pilot result that would let you proceed, and your timeline.
Send a data request