The text this build ships with

About SIYAK

Most Arabic-first products are written in English and translated last — by whoever

answers the email that month. The strings end up inconsistent, never frozen, and wrong

on the day the app ships.

SIYAK is the workbench for that last step. Add the SDK, and your app reports the text it

actually shows. A translation model takes the first pass; a person in your dashboard

approves or rejects each line. Glossary terms you pin go in front of the model every

time, so "checkout" does not become three different words on three different screens.

When the set is ready you export it in the shape your framework reads: flat JSON for a

React app, an .arb file for Flutter, Localizable.strings for iOS, or a CSV for the

translator who works in a spreadsheet.

It began as an internal fix for products written for Egyptian users, where a

professional pass over every string is out of reach and a machine-only translation is

not good enough to publish. The pricing is set for that market: plans are paid in EGP by

wallet transfer, with no card on file and no subscription trap, and the free tier is

meant to be used rather than tasted.

What you see is what the operator runs — one product, one database, with the account and

traffic screens kept behind their own sign-in. Nothing is a demo.

If something here is missing or broken, open a ticket. It reaches a person.