Archon Mise
Order tickets clipped to a rail on a restaurant pass, a plate steaming beside them under a warm service lamp.

Archon · Dubai, UAE

Operating software.
For the hours that matter.

Some businesses are judged on one window of the day. We build the systems that hold up inside it. The first is Mise — the system a restaurant runs its night on.

207Dishes live
3Languages
4Staff roles
0%Commission taken

S.01 — One night, four moments

One system, from the QR code on the table to the last number of the night.

19:40 — Table 12 seated

The guest scans.

No app, no download, no waiting for a menu. The QR code on the table opens your own menu — in English, Spanish or Arabic, chosen by the guest, not by you.

20:05 — Order placed

The order goes in.

Prices, VAT and the running total are computed in one place, so the number the guest sees is the number the till charges. No arithmetic at the table.

20:06 — Ticket in the kitchen

The kitchen gets the order.

One second later the ticket is in the kitchen, in the form a kitchen already reads. Nobody retypes anything, so nobody mistypes anything.

23:50 — Service closed

The owner closes.

Covers, revenue and what actually sold — the night, in the numbers you already use to run it. Not a report you have to build.

An empty restaurant counter laid with cups and folded linen, lit from one side before service.

S.02 — Before anyone arrives

The work that shows is the work done before the doors open.

S.03 — Products

One system, finished.
Then the next one.

Archon ships a product when a real business is running on it, not when a roadmap says so. Mise is live in Dubai today. What follows is listed honestly, with no date it cannot keep.

Available · Live in Dubai

Archon Mise

The restaurant's own site, menu, ordering and kitchen tickets — one system from the QR code on the table to the numbers at midnight. Everything in its place before the doors open.

  • Your own site and menu, not a listing on someone else's app
  • Table ordering by QR — no download for the guest
  • English, Spanish and Arabic, switched by the guest
  • Kitchen, waiter, cashier and owner, each with their own view
  • UAE VAT computed once, so the till and the table agree

In development

Archon Reach

Outreach a small house can actually run: research, sequence, reply — one conversation at a time. Tested on Archon's own pipeline long before it is sold to anyone.

In development

Archon Voice

A voice that answers the line when the floor is full, takes the booking, and writes it where the floor can see it. In testing on live UAE numbers.

A long laid table under a single warm pendant lamp in a dark, arched dining room at night.
A dining room in Dubai, 19:30

S.04 — Why here

A room in Dubai speaks more than one language.

So does its menu. English, Spanish and Arabic — including a right-to-left layout that is built, not bolted on. The guest picks. The kitchen never sees the difference.

Good evening.

Buenas noches.

مساء الخير

S.05 — Next

Come see it running in a real dining room.

Not a slide deck. A restaurant in Dubai serving guests on it tonight.

A laid table under a single pendant lamp in a dark, arched Dubai dining room before service.

Archon Mise · Available now

Everything in its place.

One system from the QR code scanned at a table to the reporting numbers at midnight. Your site, your menu, your guests, your data — and no commission on a single order.

S.01 — What it replaces

A delivery app rents you
your own customers.

Then it charges a quarter of every order to keep renting them to you, and it keeps the record of who they are. Mise is the other arrangement.

Their marketplace

  • 25–30% taken on every order, forever
  • Their brand above yours, next to your competitors
  • They hold the guest's details, not you
  • Your price has to absorb their cut

Your Mise

  • No commission, just a flat fee, whatever the night does
  • Your own domain, your own room, nobody else's
  • Your guests and your orders sit in your database
  • The price on the menu is the price you keep
A small folded card with a QR code standing on a linen tablecloth, a guest reaching for it with a phone.
The whole onboarding, for the guest

S.02 — How it starts

A QR code on the table. That is the whole install.

No app to download, no account to create. The guest points a camera at a QR code and your menu is open, the same menu the kitchen is cooking from, priced the way the till will charge.

For a table in a hurry, that is the difference between waiting for a busy waiter and knowing your food is being prepared.

A chef's hands sliding a plate across a stainless steel pass toward a waiter, a ticket pinned under the thumb.

S.03 — The order

Different teams. One ticket. No disagreement.

A restaurant is not one screen. The floor, the kitchen, the bar, the till and the office each need a different view of the same night — and they must never disagree about it.

Waiter

Opens a table, takes the order, delivers the dishes, closes the bill.

Kitchen

Tickets arrive in the order they were sent, with requirements spelt out.

Cashier

The bill adds up on its own, because nobody re-entered it.

Owner

Complete oversight: the money, the staff and which dishes actually paid for themselves.

A plate of arepa and ajiaco with a brass spoon on dark linen, lit by a single window.
Your dishes, your prices, your room

S.04 — The site we build you

It should look like your restaurant. Not like software.

We build your landing page too — the real thing, with proper UI/UX, your menu, your logo, your photography and your words if you want, on your own domain. Not a template with your logo dropped into it.

The menu the guest opens is part of that same site, so scanning the QR code never throws them out of your space into someone else's app.

This page you are reading was built by the same hands.

S.05 — The owner's side

Eleven screens to run your business. The guest never sees them.

Behind the menu is the part you run the business from: what is on the menu, what sold, what is left, what to buy tomorrow, who worked, and how much came in. One private address, one PIN — total visibility and control.

Owner · Waiter · Kitchen · Cashier — each PIN opens a different one of these

S.06 — What is included

Everything a night needs.
Set up by us.

Not a login to a product you then have to configure. We build the whole thing around your restaurant and hand it over running — organised below by who actually touches it.

The room

What your guest meets. Built to look like your restaurant, not like software.

  • A landing page built for youThe real thing, with proper UI/UX, your menu, your logo, your photography and your words if you want. Not a template with your logo dropped in.
  • QR menu at every tableOne QR code per table, keyed to the table number, so an order arrives already knowing where it goes.
  • Ordering directly from the guest's own phoneNo app, no download, no account.
  • English, Spanish and ArabicIncluding a real right-to-left layout. The guest picks.
  • LoyaltyRepeat guests recognised, without a plastic card or a second app.
  • ReservationsTables and covers held against the same night the kitchen is cooking.

The teams

What your floor and your kitchen work on, every service coordinated.

  • Four roles, four views, one PIN eachOwner, waiter, kitchen and cashier. Nobody sees a screen that is not their job.
  • Kitchen tickets in the order they were sentWith the requirements spelt out, in the form a kitchen already reads.
  • Printing to your thermal printerBluetooth ESC/POS — the ticket comes out on the same printer roll you use today.
  • Installs like an app on your tabletsA PWA: it sits on the home screen and opens like an app, without an app store.
  • Nothing re-typed between floor and kitchenThe order the guest placed is the order the kitchen works from and the order the till charges. The step where mistakes happen in most venues does not exist here.
  • VAT computed once for the whole systemSo the table, the ticket and the till are always aligned.

The office

What you run the restaurant from, after everyone has gone home.

  • The owner dashboard, eleven sectionsOrders, menu, reports, cash register, inventory, forecast, production, staff, reservations, tools and website.
  • Forecast and shopping listWhat the coming days are likely to sell, and what to buy for them — from your own history, not an industry average.
  • Reports to your phoneThe night's numbers arrive on Telegram when service closes. No dashboard to remember to open.
  • Your menu, edited by youPrices, dishes, photographs and availability live in the dashboard. Anyone on your team with the PIN can change them — no ticket filed with us because something ran out at 21:00.
  • Your own database and your own domainMenu, orders, guests and revenue belong to the venue and are exportable at any time.

S.07 — Specifications

What is actually in it.

Guest orderingA QR code at the table opens the menu in the browser. No app, no download, no account.
LanguagesEnglish, Spanish and Arabic, including right-to-left layout. The guest chooses, not the venue.
MenuCategories, modifiers, photographs and availability. Running live today on a venue with more than two hundred dishes.
RolesOwner, waiter, kitchen, cashier and guest. PIN entry, each with its own view of the same service.
TaxCountry VAT computed in one place for the whole system, so the table, the ticket and the till are always aligned.
ReservationsTables and covers held against the same night the kitchen serves the dishes.
Owner dashboardEleven sections: orders, menu, reports, cash register, inventory, forecast, production, staff, reservations, tools and website — on a private address, behind a PIN.
Ticket printingBluetooth ESC/POS to the thermal printer already in your kitchen. No new hardware to buy for the tickets themselves.
On your devicesInstalls as a PWA — it sits on the home screen of your tablets and phones and opens like an app, with no app store in the way.
Nightly reportsThe day's numbers arrive on Telegram when service closes, so nobody has to remember to open a dashboard.
LoyaltyRepeat guests recognised without a plastic card or a second app.
Your websiteA landing page built for the venue — full UI/UX, not a template, on your own domain.
Your dataMenu, orders, guests and revenue live in a database that belongs to the venue. Exportable, always.
Your addressYour own domain. The site is the restaurant's, not a page inside somebody's marketplace.
CommissionNone. A flat monthly fee — a busy Saturday costs the same as a quiet Tuesday.
Not includedDelivery logistics and payment processing stay with the venue's existing providers. Mise does not replace them and does not take a cut of them.

S.08 — Getting it running

Five steps, and we are there for all of them.

You send the menu

However it exists today — a PDF, a printed card, photographs on a phone. That is the whole ask.

We build the site for you

Your site, your menu in the languages you need, your prices with VAT already set. You see it before anyone else does.

We get everything ready for you

One full service, next to your waiters and your kitchen, helping you deliver quality service even under real pressure.

You open

The QR codes go on the tables and you are running.

We are always there if needed

Because the first weeks are the ones that matter, we stay on the line through them.

S.09 — Already running

Not a prototype. A dining room.

A Colombian restaurant in Dubai has been taking its orders on Mise since July 2026 — the same code, the same database, every night.

207dishes on the live menu
3languages, Arabic right to left
0commission taken, ever

S.10 — Questions

Asked before, answered plainly.

What does it cost?

A flat monthly fee, never a percentage of your orders — a busy Saturday costs exactly what a quiet Tuesday costs. We do not publish the number because it depends on the size of the room and how much menu there is to build. Fill in the set-up and we come back the same day with a figure; a fee quoted blind is one that somebody ends up regretting.

Do we have to replace our POS or our payment provider?

No. Mise covers the room: the menu, the ordering, the kitchen and the night's numbers. Card processing and delivery logistics stay with whoever handles them for you today, and we take no cut of either.

What happens to the data if we leave?

It is yours and it leaves with you. Menu, orders, guests and revenue are exportable at any time, without asking us and without a fee. A system that holds your data hostage is not a system; it is a lock and chain.

Our menu changes every week. Who edits it?

You do, online. Prices, dishes and availability live on the dashboard, so anyone on your team who has access can change the menu — no new software, no ticket filed with us because something ran out at 21:00. The self-service editor is inside the dashboard.

Is the Arabic real, or machine translated?

The layout is real: right-to-left is built into the system, not flipped with a stylesheet. The words are yours — we set up the fields and a native speaker on your side signs off the menu copy. We do not publish Arabic nobody has read.

Who owns the domain and the site?

You do. The site lives on your own domain, registered in the venue's name — not on a subdomain of ours. If we ever part ways, the address your guests already know keeps working and stays yours.

What happens on a Friday night when everything is full?

The guest's menu and ordering run in the browser against a database built for concurrent tables, not on a tablet in the corner that somebody has to keep awake. The part that fails under pressure in most venues is the retyping between the floor and the kitchen, and that step does not exist here.

How long from the menu to opening?

Days, not months, for a single venue with a menu that already exists. The step that takes real time is the service we stand through with your floor, and that one should not be rushed.

S.11 — Get a quote

Tell us about your restaurant.
We come back with a number.

We do not publish a price, because it depends on the size of the room and how much menu there is to build. So we ask first — the same questions we would ask on a call, in an easy-to-use form you can leave and come back to.

What it takes

  • Your address, your opening hours and how many tables
  • Currency and VAT, so the till is right from day one
  • The languages your guests actually speak
  • Your menu — a PDF is best, a photograph works

Ten minutes. It saves as you type, so you can stop halfway and finish from the same device later.

What happens next

  • It reaches us the moment you press send
  • A person reads it — nothing is built automatically off a form
  • We come back the same day on WhatsApp with the price and what is missing
  • If we are not the right fit for your venue, we will say so

Archon Mise — Set-up

Tell us the restaurant. We build it.

Everything below is what it takes to stand your system up — the address on the ticket, the VAT on the bill, the languages on the menu. It saves as you type, so you can leave and come back on the same device.

The venue

The name that goes on the site, on the dashboard and on every printed ticket.

Exactly as guests know it.

The short form you use on the sign or the logo. Leave empty to use the full name.

A short phrase. It becomes the description search engines read.

Where to find you

This lands on the site, in the map, and on the printed receipt. Get it exact — a wrong address on a ticket is a real problem, not a typo.

This sets your currency, your tax rate and your time zone further down. You can change any of them.

Open your restaurant in Google Maps, press Share, and paste the link. It sets the map on your site.

How you operate

The number of tables matters more than it looks: a table numbered above it is silently rejected when a guest scans, so count every table you will ever put a QR code on. Adding a few spare now costs nothing.

Opens, then closes. Past midnight is fine — 01:00 means one in the morning.

Leave as is if you keep the same hours all week.

If you never close, leave it blank.

Count the terrace and any table you might add this year. Too high costs nothing; too low breaks scanning.

Every "today" in your reports is computed from this.

Money

The tax rate is written into two places at once — what the guest sees and what the till charges. If it is wrong here, it is wrong on both, so it is worth checking with whoever does your books.

Set from your country. Write 0% if the venue is not registered.

Printed on the receipt. Legally required once registered.

As on the trade licence, if it differs from the name guests use.

Language and look

Pick every language a guest might want. Arabic is laid out right to left properly, not flipped with a stylesheet — but the words are yours, and we ask a native speaker on your side to sign them off before anything goes live.

Tap to add or remove. English is on by default — switch it off if your guests do not need it.

If you do not know them, leave these and send the logo below — we take the colours from it and show you before building.

The room, the kitchen, three or four dishes. JPG, PNG or HEIC, the largest you have. Up to eight files.

This is what your site will be made of. Send nothing and we will find good photographs of your kind of cooking — the site will look right, but it will not be your room and it will not be your plates. Photographs off a phone, taken near a window, beat anything we can find for you.

A name is enough. If you have licence files, mention it and we will ask separately.

The menu

This is the one that takes us the longest and you the least. Send it however it exists — a PDF is best, and we read it almost perfectly. Photographs of a printed card work too; a person on our side checks those by hand.

If your menu already lives online. A link to a delivery-app listing does not work — we tested it and the data comes back wrong.

Where it lives

Your site needs an address. If you already own one we point it there; if you do not, it goes up on an address we give you the same day and you can move it to your own later without rebuilding anything.

Owning one means you pay for it somewhere: GoDaddy, Namecheap, Cloudflare, or whoever built your last site.

You

Who we talk to while we build it, and where.

Check it over

Everything you have told us, in one place. Anything blank we will simply ask you about — nothing here blocks us starting.

Received

We have it.

It landed with us the moment you pressed send, and we read every one by hand before anything gets built. Expect a WhatsApp from us the same day — usually within a couple of hours during Dubai business hours.