Elyoxe

Quiet on the surface, engineered underneath.Simplicity is the last thing built.

Elyoxe is an engineering studio in Dubai that designs systems, builds them and runs them: bilingual websites, AI pipelines that treat Arabic as a first language, native Android applications, and cloud infrastructure on AWS. Nothing here is described from a distance — every number on the page has a link you can open or a page you can read.

A surface resolving in front of you: contour lines sharpening with motion

Services

Four parallel fields, not stages. Each points to published work that proves it.

  • Web development

    Marketing sites, internal tools and customer-facing applications, bilingual from the first commit rather than translated afterwards.

    One layout, mirrored between LTR and RTL
  • Artificial intelligence

    Document processing, classification and review pipelines, with Arabic as a first language rather than a translation layer. And a system that grades its own exam always passes — so we establish what a false result looks like first, then measure yours against it, whether we built it or you bought it.

    Arabic and Latin documents in one lane
  • Software engineering

    Native Android, backend services and integrations, measured by reliability rather than feature count.

    SIGKILL, then resume with no gap in the data
  • Cloud infrastructure

    AWS architecture, deployment automation and cost engineering for systems that have to stay running.

    From the origin to the edge nearest the visitor, the meter steady

Work

Real projects, each with an interactive diagram built for it alone, and one number that is about you.

InvoiceReadyLive · Compliance platform

A bilingual platform for the United Arab Emirates e-invoicing mandate, designed, built and operated end to end.

24checks your invoice passes before you send it
KhutwaComplete · Mobile

A native Android activity tracker built around sensor accuracy and complete data privacy.

0steps lost when the app is killed
Quantitative methodOngoing · Verifying AI systems

Every system that grades its own exam passes it. This is a method that makes a negative result possible — built on crypto markets, applied to the AI systems we ship.

0results acted on before they passed the checks

Ten coin flips the same way is not rare, and in enough data you will always find a rule that looks true. That alone is why this ledger exists: every line is a way we could have fooled ourselves, and a rule written in advance that closes it.

Try it yourself

0flips
—Heads ratio · converges on 0.5
—Absolute gap · and keeps growing
—Longest streak

Press, and watch the two numbers move in opposite directions.

Standing rules, written into the project's policy before any run — not a tally of results.

Three independent out-of-sample checks, on every line.

  1. Test until something passesThe hypothesis is registered in writing before it runs: population, horizon, feature, predicted direction — and the condition that would falsify it.Closed
  2. Interpret the result after seeing itThe statement stands verbatim as written, and the falsification is reported rather than edited away.Closed
  3. A single arm that looks goodHypotheses are registered as opposed pairs — a single arm that looks good cannot be falsified at all.Closed
  4. Not knowing what chance looks likeA null control runs through the same pipeline: one that finds an edge in shuffled data is broken, and that has to be found before it costs money.Closed
  5. Look again every time the data growsNo look before the registered date or the required count, whichever is later — and any earlier look is written down first.Closed
  6. Test on what you developed onA holdout of instruments never used in development, not analysed and with no look spent on it.Closed
  7. Run whatever looks goodA written gate governs what runs live, with a kill switch, risk caps, and a forward ledger that records every signal from the moment it fires.Closed

There is deliberately no counter here. The number of negative results changes every week; what makes a result worth believing is these rules, and they do not.

AhlamLive · Arabic reference

A sourced dictionary of classical Arabic dream interpretation, where every line can be checked against the page it came from.

2,665symbols, every reading shown on a scan of its printed page
Taʿṭīr al-anāmباب الباء
بحر في المنام يدلّ على ملك قويّ هائل مهاب عادل شفيق يحتاج إليه الخلائق، والبحر للتاجر متاعه وللأجير أستاذه. (ومن رأى) البحر أصاب شيئاً كان يرجوه.

From ʿAbd al-Ghanī al-Nābulusī (d. 1143 AH), Taʿṭīr al-anām fī taʿbīr al-manām, vol. 1, page 30.

The text is reproduced from the printed book as it stands. The site retrieves; it does not interpret.

Reply deskEngine live · Customer-service agent

An agent that answers one business's customers in Emirati Arabic, confined to that business's own file — and this page opens a door to talk to it.

0.07dirhams for a complete conversation with your customer
Salon NoorFictional business

checking…

Same engine, another file

Write to it the way a customer would. Its file holds five services, their prices and the opening hours — and nothing else.

Try

Nothing here is stored. The only writes are two counters: today's cap and yours.

Approach

Four clauses written before any work starts, binding on every engagement.

Written before work startsBinding on every engagement
  1. 01Clause one

    Scope is fixed before code

    Every engagement opens with a written scope and a fixed list of deliverables. Anything added later is priced and agreed before it is built.

  2. 02Clause two

    Every delivery ships with its tests

    The system arrives with the checks that prove it works, and your team can run them without Elyoxe.

  3. 03Clause three

    Deployment and early operation are part of delivery

    Deployment, monitoring and the first operating period sit inside the same contract, not a second one that arrives later.

  4. 04Clause four

    Cost and limits, in writing

    Every delivery says in writing what the system does, what it costs to run, and where its known limits sit.

Engagement model

Fixed scope and fixed price for defined projects. Retained monthly capacity for ongoing work.

Elyoxe

Signed before the work, not after.

Start with the problem,not the specification.

A short description of what is not working today is worth more than a finished specification. The first conversation costs nothing, and a reply follows within one working day.

Send the problem as it is, even in two lines.

A first conversation usually opens a door that was not on the table: a shorter route to the same result, or a result wider than the one asked for. You only find out which once the problem is described as it actually is.