Enter the matrix.

Logistic OS — the second cockpit

On the rosette, it's the only node that doesn't orbit the REST OS hub like the others — it has its own ring, linked by a dotted line. That's not a layout accident: Logistic OS isn't one more feature inside the console, it's a second, sovereign system that simply talks continuously with the first.

An order goes out for delivery. The instant it leaves the kitchen, Logistic OS sees it — not through an end-of-day import, but a live, continuous connection. The fleet of independent drivers — not employees to manage, but partners who drive for whoever they choose, whenever they choose — receives the run through a dispatch that tracks every rider in real time.

You don't do anything more than what you already do: ring it up, send it to the kitchen. Everything else moves on its own.

Why a second hub instead of just another module? Because delivery isn't a sub-problem of the kitchen — it's its own trade, with its own geography, its own urgency. A system connected continuously, never force-merged: each keeps its own coherence, data flows between the two without ever getting lost.

What the Storefront does that the others don't

Every prep console looks alike at first glance — start, check, send. The Storefront is the only one that sees beyond itself: any station can turn on local stock tracking for its own items; the Storefront gathers the stock of every other console in one place — one screen, two tabs (Orders, Stock), to see what's missing anywhere in the establishment.

And when an item drops below the threshold you set, the order automatically routes to whichever prep station you've chosen for that item — Kitchen, Bar, Salad or Grill, adjustable item by item from the Menu. No one loses a sale because a storefront item was briefly out of stock.

Counter and Service — twins, not identical

Same architecture, same capabilities — but each has its own independent settings. You can reserve payment to the Counter only, or the reverse, or turn both on: the decision takes seconds from Admin, and fits the way your establishment actually runs.

The Counter has its own specialty: its home screen opens on four large tiles — Dine In, Takeaway, Delivery, and Active Orders — to start an order by its nature in one tap, no detour through a menu.

And because both consoles run in parallel, nothing forces you onto a single screen. A floor plan can stay open on one console while an order gets managed, paid, or adjusted on the other — two views moving forward together, each at its own pace, instead of one screen you keep bouncing between.

Your vocabulary, not ours

Nothing forces a station to be called what we called it. The "Grill" you just saw can become "Bakery" for you, "Pizza" somewhere else, in your language, with your icon, your color. None of that touches the engine.

The entry tier isn't a stripped-down version

KDS + Stock — the cheapest, payable in installments — could read as "the light version." It isn't: it's a deliberate choice that skips what slows a launch down (tax certification, third-party payment engines). An entry point built to be crossed fast, not a compromise while you wait to upgrade. That's OSK's whole DNA.

Compliance, without you thinking about it

From Pioneer up, every transaction is signed and archived under your country's real tax regime (NF525 in France, e-CF/DGII in the Dominican Republic) — the same checkout gesture you already make, compliant in the background, with no extra step.

The command post

Ten zones inside Admin, each with a real function — Overview, Orders, Menu, Customers, QR, ERP, Settings, Ecosystem, Network, Compliance. Nobody measures a cockpit by counting its buttons — but nobody flies a fighter jet with a stick and nothing else.

• Overview — the whole service at a glance, live.
• Orders — the full history, nothing lost once a table is paid.
• Menu — your items, your prices, your prep destinations.
• Customers — profiles, history, loyalty, whenever you choose to use them.
• QR — generating your table codes, ready to print.
• ERP — the global control, the view that ties every station together.
• Settings — every switch that defines how your establishment runs.
• Ecosystem — the gateway to the rest of the KAYA network.
• Network — the connection to the hub, the fleet, the other systems.
• Compliance — your tax dashboard, live.

Bar — the only station with no front door

Kitchen, Grill, Salad, Storefront: each requires a "START" gesture before you can even check off an item. The Bar has no such door. The moment a round comes in, it's checkable, right away.

And to go even faster: an "ALL" button selects the whole round in one gesture — not one click per drink. That's not a design oversight. A bar serves fast, in bursts, often the same handful of references on repeat.

It's not an isolated ergonomics detail — it's a choice that matters beyond the restaurant. Bar, lounge, rooftop, club, nightlife venue: wherever the rhythm plays out at the counter rather than the kitchen, this console treats the Bar as a trade of its own, not a box ticked by default in a generic till suite.

One thumb, not ten clicks

On Counter, Service, Storefront and Admin, a single swipe — left, right — is enough to move between a table's screens: the menu, the order in progress, active orders. Order tiles collapse or expand with a tap; once open, the same swipe takes you through their tabs, and from the edges, one more swipe brings you back to the overview.

Nothing to memorize, nothing to aim precisely at on a small screen mid-rush: the thumb swipes, the screen follows. Same philosophy you just tried higher up on this page.

Your hardware, not an imposed catalog

OSK runs in a browser — not in a proprietary box. The mini-PC you already have, the tablet sitting in a drawer, the computer running your current till: nothing forces you to buy anything new to get started.

And if you want to go further — a kitchen display panel that survives under a hose-down, transparent film to stick on the pass window to open the kitchen to the room, a dedicated mini-PC for under $50 — OSK doesn't sell hardware off a fixed catalog: OSK knows which one to choose, sources it, negotiates it, delivers it to you. The right choice depends on your establishment, never on an imposed range.

Your name, never someone else's

On a marketplace, the customer orders "Uber Eats" — not from you. Your kitchen, your work, your name: diluted into someone else's brand, among dozens of establishments that all look alike from that screen.

The OSK website stays yours — your name, your colors. A simple storefront, online ordering sent straight to the KDS, or reservations tomorrow: you choose what it does. Nothing stops you from joining forces with other establishments one day if you want — but as a choice, never as a dependency.