About Sidra
Sidra is a commerce operating system built for Arabic-speaking markets, Arabic first, out of one conviction: most of what is sold to businesses here is either a foreign system localised after the fact, or a handful of small tools wired together whose connection fails at the worst possible moment.
The name
The sidra — the lote tree — is native to this region: deep-rooted, long-lived, giving shade, sending many branches out of a single trunk. The name was chosen because it describes the construction rather than because trees are pleasant: the platform is one modular monolith — one trunk — with twenty-two modules branching off it, each a business capability rather than a separate product. In Latin script the name also carries a backronym, Smart Integrated Data & Resource Automation, which is a convenience for an English-speaking reader and not the origin of the name.
Why one engine
When finance is in one system, jobs in another and transport in a third, the number you actually need — what did this trip earn — lives in three places and is complete in none of them. Sidra keeps numbering, permissions, the audit trail and the posting path in one place, so profitability is something you read rather than something somebody assembles by hand at month end.
The core does not know your industry
There is no "retail invoice" in this system, no "contracting customer", no "tyre product". There is a document, a party, an item and a job — and a business type that is tenant configuration rather than a model in the core. This is not engineering elegance: it is the reason a new kind of business is added by configuring it rather than by shipping a release, and the reason one customer does not wait behind another.
Arabic and English together
Every screen and every document works in both directions, and Arabic is the default rather than the second option. The typefaces ship inside the application: the platform does not fetch a font from a third party on every load, because that makes every screen in a business system depend on a host we do not run and charges the user a round trip they did not need to pay.
What is not built yet
Inventory, purchasing and sales are on the plan and not built, and the Commerce bundle is empty today. Determining a tax code from the place of supply is a product decision nobody has taken. We write that here and on the capability pages themselves, because a customer finds the gap either way and the only variable is when, and from whom.