AE-1
A private AI workspace for teams that work in Arabic and English.
The AE-1 Core. One workspace for chat with files, memory and web search, connectors, decks and PDFs, schedules, Messages and the admin console, in six languages.
Explore AE-1Private models trained on your own records, in Arabic and English, running inside your walls.
A private assistant for your people, the model that does the thinking, and the engine that trains models on your data. All of it runs inside your walls.
A private AI workspace for teams that work in Arabic and English.
The AE-1 Core. One workspace for chat with files, memory and web search, connectors, decks and PDFs, schedules, Messages and the admin console, in six languages.
Explore AE-1The intelligence model from Sharq.
From the S1 page. One model, made to understand what you mean and to do the work that follows.
Explore S1Trains and serves models on your data, on your infrastructure.
Illustration. A fine-tuning run pulls a general model toward the way your organisation writes and decides.
Explore Sharq EngineA rented model has never heard your Khaleeji customers, read your credit policy or seen how your best agents close a case. Sharq takes what your organisation already knows and turns it into a model that works inside your world, and belongs to you.
| Hosted frontier API | ||
|---|---|---|
| Arabic adaptation | General‑purpose ArabicUsually steered with prompts and examples. | Fine‑tuned on your conversationsYour own Gulf, Levantine or Egyptian conversations, scored on dialect evals. |
| Data residency | Set by the providerIts hosting regions and its data terms. | Your racks or your cloudYour cloud account in a UAE or KSA region, or Sharq’s in‑region hosting. |
| Pricing model | Usage‑basedUsually per token. | Pilot fee, then a platform planCompute billed at cost. The weights are yours to keep. |
| Policy controls | Applied through promptsSystem prompts and the provider’s safety settings. | Trained into the modelChecked on policy‑adherence evals before each release. |
| Model updates | The provider’s scheduleReleased when the provider decides. | A cadence you approveRetrained on your team’s corrections. |
The console your team works in, from first dataset to a served model.
Open the consoleTry it. Point along the line, pick an eval, pause the run, change the base model and start another, then deploy it.
Illustrative run, computed in your browserWe don’t quote savings in advance. Every pilot is judged on the operating metrics the business owner already tracks, against the stack you use today.
| Baseline Your current stack, measured in weeks 1 to 2 | Pilot model The same cases, side by side, in weeks 9 to 10 | |
|---|---|---|
| Arabic task successHow often the model gets the task right in your customers’ dialects, including code-switched Arabic and English. | % of tasks, not measured yet | % of tasks, not measured yet |
| Cost per taskWhat each completed task costs to run, compute included, compared with what you pay per task today. | per task, not measured yet | per task, not measured yet |
| Case throughputCases resolved per agent, per day, in the workflow the pilot targets. | cases per agent, per day, not measured yet | cases per agent, per day, not measured yet |
| Left blank on purpose. Results are measured on your own workload and reported to you. | ||
One workflow where your current stack is too expensive, too inconsistent or not allowed to leave the country. Twelve weeks later you have a private model and a benchmark to prove it.
Weeks 1 to 2
We sit with your operations team and your records, and learn what the work actually is. One workflow, one owner, one number that has to move.
You bring Call recordings, tickets, documents. The messy real thing.
You get A data audit and a written target for the pilot.
Weeks 3 to 8
Your data is cleaned, stripped of personal details and labelled by dialect. We fine-tune an open model on it, inside your environment, and iterate against Arabic evals every few days.
You bring Two hours a week from a domain expert to review samples.
You get A model that speaks like your best agents, and the dataset behind it.
Weeks 9 to 10
Side by side with what you use today, on live cases, on the outcome you named in week one.
You get A benchmark report: task success, cost per task, throughput.
Week 11 onwards
The model joins the team. Accepted edits and escalations become the next training set, on a cadence you approve.
You get Quarterly refreshes, each one re-checked against the same evals.
Every stage runs where your data lives. Your team can watch, approve and roll back at each one.
Where your data lives
Calls, chats, scans and records become training-ready material, with private details removed before anything is touched.
Choose a base model and a target; the platform picks the method, the hardware fit and the schedule.
Judged on the Arabic your customers actually write and say, and on the rules your regulator cares about.
The finished model runs as an endpoint inside your walls, with an audit trail your governance team can read.
We start where the volume is high, the language is local and the current tooling is either expensive or not allowed.
Retail and corporate banks with Arabic-speaking customers and strict residency rules.
Contact centres handling millions of code-switched conversations a month.
Entities that cannot send a citizen’s record to a foreign cloud, full stop.
Developers and brokerages answering buyers and tenants in Arabic and English, on every channel.
Law firms and in-house teams working across Arabic and English documents, in confidence.
Insurers handling claims and policy questions in dialect, under local regulators.
Hospitals and clinics whose patient records have to stay inside the country.
Operators with decades of technical records and crews who work in two languages.
Retail and corporate banks with Arabic-speaking customers and strict residency rules.
Contact centres handling millions of code-switched conversations a month.
Entities that cannot send a citizen’s record to a foreign cloud, full stop.
Developers and brokerages answering buyers and tenants in Arabic and English, on every channel.
Law firms and in-house teams working across Arabic and English documents, in confidence.
Insurers handling claims and policy questions in dialect, under local regulators.
Hospitals and clinics whose patient records have to stay inside the country.
Operators with decades of technical records and crews who work in two languages.
Anything missing, ask us directly. Conversations are confidential and we reply within one business day.
The model weights, the curated dataset behind them, and the evaluation suites used to judge them. You can export all three at any time and run the model without Sharq.
Wherever you say: your own racks, your cloud account in a UAE or KSA region, or Sharq’s in‑region hosting. Nothing is copied outside the environment you approve.
No. Sharq engineers run the pipeline. Your side contributes what only it can: a domain expert for a couple of hours a week to review samples and outcomes.
Dedicated evaluation suites for Gulf, Levantine, Egyptian and Maghrebi dialects, Arabic–English code-switching, cultural alignment and policy adherence, alongside the business metric the pilot was scoped on.
Open-weight families such as Qwen, Llama, Mistral, Falcon and Jais, sized to the task. Most production pilots land between 7B and 27B parameters, which is what keeps cost per task low.
Corrections, escalations and outcomes from real work are folded back into the training set on a cadence you approve. Each refresh is re-checked against the same evals before it is promoted.
Pick the one where your current stack is too expensive, too inconsistent or not permitted. We will come back with a pilot plan, a data checklist and a number to beat.