Your whole business, one ledger.

Not separate products exchanging files, but capabilities sharing the same party, the same job and the same ledger. An invoice raised out of field service and one raised out of transport go through the same door and land in the same entry.

An inspection house, a cross-border haulier and a contractor run on one model. What differs between them is rate cards, registers and document types — not the invoice, the ledger entry or the job. Which means your business is not queued behind somebody else’s roadmap.

• Configured Petroleum inspection and testingFrom a client nomination to a signed certificate, with a laboratory, inspectors and calibrated instruments.
• Configured Environmental and marine servicesMaterial movements evidenced by a manifest, with approved carriers and tonnage-based pricing.
• Configured Cross-border road freightA cross-border trip costed in several currencies, with vehicle and driver registers and cash settled on return.
• Planned Domestic transport and distributionThe same transport without borders or customs: lanes, drops and per-movement billing.
• Planned Field and maintenance servicesRecurring service agreements, preventive-maintenance schedules and periodic billing.
• Planned RetailPrice lists and promotions, shifts and cash drawers, over stock that reconciles.
• Planned Wholesale and distributionTiered and customer-specific pricing, credit limits and a backorder policy.

You will not find customer logos, quotations or a user count on this page. The platform is at first launch with design partners working under agreement, and there is nothing to display. What follows are claims about the product itself, each of which you can check.

• Arabic first, not Arabic later

  Right-to-left was the assumption the first screen was designed under, not a stylesheet added after the first customer asked. Screens, printing and documents all work in both directions, and Arabic is the default.

• One engine, not seven

  A single modular monolith: twenty-two modules inside one engine, sharing numbering, permissions, the audit trail and the posting path. There is no integration between systems that can quietly stop working mid-month.

• Every company at its own subdomain

  Your company opens at its own address, and a session for one company does not work on another’s — because the session cookie is bound to that host, not because a check in the code remembers to refuse it.

• Configuration over customization

  Anything that can be a row in a table is not code: posting rules, approval thresholds, rate cards and registers are all settings. Raising an approval limit does not need a release.

• Every change has an author

  Each change to a record is written to the activity trail with who made it, when, and which fields moved, in the same transaction. Values are deliberately not copied there: a table holding a copy of every tax identifier would inherit none of the permissions of the table it came from.

• The limits are written down

  Every capability page on this site says where that capability stops — a posting gap in purchasing, no standard costing in inventory, no backorder document in sales. You should know that now rather than discover it in month one.