Beirut, Lebanon  ·  Two products in production

We build what runs behind the counter.

Stride is a software company making the unglamorous systems a business actually depends on. A point of sale for shops and restaurants. A white-label ordering and delivery platform for restaurant groups. Both are live, and both are taking real orders today.

01 Products

Two products.
Both already in production.

01 In production
For
Shops, minimarkets, cafés
Runs on
Windows desktop, one installer
Needs internet
No

Stride POS

The till, the drawer, and the paperwork nobody wants to do.

A point of sale that installs like any other Windows program and keeps working when the internet doesn't. The database lives on the machine, so a dead router is a nuisance rather than a closed shop. Scan a barcode, take the money, print the receipt.

  • Offline by design. Embedded database, local API, no cloud round-trip between the scan and the total.
  • Inventory that tells the truth. Purchases recalculate weighted-average cost, and every sale line stores the cost it was sold at — so profit is a fact, not an estimate.
  • Customer accounts on credit. A proper ledger of debits and payments, with balances you can actually chase.
  • Cash register discipline. Open a shift, close it against a count, see the variance.
  • Barcode-native. Scanner input goes straight into the sale, no field to click first.
  • Arabic and English throughout, right-to-left included.
02 In production
For
Restaurant groups, 1–50 branches
Ships as
Your brand, your app listing
Surfaces
Five, one backend

Stride Order

A restaurant group's own delivery operation, published under their name.

Customers order from an app with the restaurant's logo on it. The kitchen sees the ticket the second it's accepted. Dispatch watches the fleet move across a live map. None of it says Stride anywhere, which is the point.

  • White-label to the bundle ID. Each brand gets its own build, its own listing, its own isolated database.
  • Zones drawn on a map. Delivery areas are real polygons, so an address routes itself to the branch that covers it, or gets told nobody does.
  • Live driver tracking. A persistent stream from the driver's phone to the customer's map and the dispatcher's fleet view, with route history you can replay.
  • Five surfaces, one system. Customer app, driver app, kitchen board, back office, and our own console above all of it.
  • Per-branch reality. Separate menus, prices, opening hours and sold-out toggles, because branches are never identical.
  • Loyalty and campaigns built from what people actually ordered, not a mailing list.

02 How we work

Four things we're
stubborn about.

  1. i

    We build the whole thing

    Database schema, the API, the staff screens, the app in the customer's hand, and the machine it all runs on. There is no integration partner to blame when something breaks at 9pm on a Friday.

  2. ii

    Assume the connection is bad

    Patchy 3G in a stairwell, a router that reboots mid-shift, a delivery phone at six percent. The software is written for the conditions our clients actually work in, not the ones in a demo.

  3. iii

    One tenant should never see another

    Every client gets an isolated database, their own keys, their own build. Multi-tenancy was in the foundations from the first commit, not retrofitted once a second customer showed up.

  4. iv

    Numbers have to reconcile

    Cash counted against cash expected. Profit from the cost at the moment of sale. Loyalty points that come back when an order is cancelled. If the totals don't survive an argument with an accountant, it isn't finished.

03 Contact

Tell us what
you're running.

One shop or forty branches, an existing mess to replace or nothing at all yet. Send a message and describe the day-to-day. We'll tell you honestly whether we're the right people for it.