What is AIR?
AIR is a restaurant operating system: POS, KDS, direct ordering, loyalty, reservations, waitlist, menu SEO, reporting, and AI workflow in one subscription.
AIR is POS, direct ordering, SEO, loyalty, reservations, delivery controls, and AI workflow in one place. This page is the honest version: what works on day one, what needs setup, and what is still coming.
Day-one clarity
What has to work before the first service.
Revenue clarity
How direct ordering, SEO, loyalty, and delivery conversion fit.
Roadmap honesty
What is live, what is beta, and what restaurants should keep.
Buying AIR
AIR is a restaurant operating system: POS, KDS, direct ordering, loyalty, reservations, waitlist, menu SEO, reporting, and AI workflow in one subscription.
Free gets you a full POS and a free website to start. Core ($99) covers the day-one operating system and removes per-order fees. Pro ($199) adds delivery integrations, channel pricing, food cost, inventory, and margin controls. Premium ($299) adds AI-R Host, website enhancement, SEO reporting, and deeper growth workflows.
Yes. AIR includes direct ordering and does not charge commission on your own orders. Guests can order from AIR-hosted ordering pages or from a website AIR enhances for you.
No. AIR does not take commission on direct orders. Payment processing still applies, but AIR does not add a platform tax to guests who already wanted to order from you.
Payment processing, hardware, SMS/voice usage over included pools, and some third-party vendor costs are separate. We try to surface those honestly instead of hiding them in a quote.
Yes. AIR is designed to earn the restaurant every month, not trap it in a long contract.
Cutover
A basic restaurant can evaluate AIR in a week. A real cutover depends on menu complexity, printers, payment terminals, table maps, staff training, delivery integrations, and phone/text approvals.
Yes. The safest path is parallel testing: import the menu, check modifiers and pricing, verify printers, run fake orders, then schedule the real cutover.
Payments, terminals, menu, modifiers, tax, printers, receipts, kitchen routing, floor map, staff PINs, and PWA order entry. Everything else can ramp after the restaurant can safely serve guests.
Plate costing, inventory confidence, smart shopping lists, advanced marketing, social posting, deeper SEO reporting, and AI optimization get stronger after AIR has real operating data.
Yes. Beta operators get hands-on setup help. AIR also includes a cutover plan so owners can see what is done, what needs verification, and what can wait.
POS
Yes. AIR includes POS, KDS, table map, coursing, expo, receipts, modifiers, staff PINs, and order entry on iPad and phone PWA surfaces.
Usually, yes. AIR is designed around standard iPads and browser/PWA surfaces instead of proprietary terminals.
AIR is designed to work with Square or Stripe at cost. We do not mark up processing, and we want restaurants to keep flexibility as rates change.
Yes. Printer setup is one of the most important cutover checks. AIR supports kitchen routing, receipt printing, auth-slip settings, and fallback planning.
That is the goal: dine-in, direct online, phone, DoorDash, Uber Eats, Grubhub, and KitchenHub orders should route to the right kitchen and receipt printers.
The target architecture is web printing first, with local fallback options where the restaurant needs them. We plan cutovers around the actual network and printer layout.
Website
AIR can host or enhance a restaurant website as part of the plan. The goal is to include website plus online ordering without adding another vendor bill.
No. The first step is to audit the current site, keep what is working, and add direct ordering, menu SEO, schema, and conversion paths. A rebrand can come later.
AIR structures menu items, categories, ordering paths, schema, local business data, and internal links so Google can understand the restaurant and menu.
AIR is building a tracking loop: baseline grade, changes made, indexed pages, ranking movement, direct-order starts, reservations, loyalty signups, and 7/30/90-day reporting.
Yes. AIR uses direct-order links, receipt paths, QR inserts, loyalty, and future delivery-channel reporting to move repeat guests back to the restaurant's owned channel.
Yes. AIR can provide reservation and waitlist flows, and restaurants can also keep or embed existing providers when that is the better path.
AI
Maestro is the unified AI surface inside AIR. It can focus on CFO, Ops, or Marketing questions while using the restaurant's own data and workflows.
Examples: What were sales yesterday? What item should we push tonight? Did Robbie clock in? Which DoorDash issues need attention? Are we better off paying for OpenTable or running local ads?
AI-R Host is the phone-facing part of the system. It can answer calls, take pickup orders, book reservations, send links, and hand off to staff when a person should take over.
That is the plan. The menu, modifiers, hours, channel availability, loyalty, and handoff rules need to be correct before live order taking is turned on.
A phone agent sounds simple until it has to quote the right menu, modifiers, hours, prices, reservation rules, handoffs, loyalty, and kitchen flow. It works best when it is connected to AIR.
No. A smart launch path is shadow mode first: let it listen, test menu recognition, run QA, collect corrections, then activate when the restaurant is confident.
Delivery
Pro and Premium are built around third-party marketplace integrations. For Chan Nara, KitchenHub is the API path for marketplace access.
Yes. AIR includes channel pricing so restaurants can protect margins by platform instead of manually editing every marketplace.
AIR is building service pace controls. Some platforms limit what can be changed after an order is accepted, so the best flow may be queueing orders briefly, setting the right time, then accepting.
Chargeback Fighter is a planned workflow for monitoring delivery reports and helping dispute invalid chargebacks. It belongs in the post-cutover value layer, not the day-one critical path.
That is the goal. We are exploring delivery dispatch partners such as Shipday for restaurants that want direct delivery from their own website.
Data
Yes. Loyalty can start on day one. The richer reporting gets better after the restaurant has 30 days of orders, redemptions, and guest behavior.
Food cost becomes useful after recipes, invoices, vendor prices, and sales mix are entered. The first 30 days are about building the habit and improving confidence.
Yes. AIR is designed to use invoices to update vendor costs and eventually connect purchasing, plate costs, waste, and shopping lists.
Not yet. AIR can support timeclock and exports, but restaurants should keep accounting and payroll software until replacement workflows are truly ready.
Day one: sales, orders, payments, printer status, and service flow. Day 30: loyalty, food cost confidence, delivery margin, SEO movement, and staff habits.
Roadmap
Social media content creation and posting, deeper marketing automation, chargeback workflows, stronger inventory intelligence, richer SEO reporting, and more Orion-backed setup guidance.
The goal is to generate menu-item images and short videos, create campaign assets, and schedule social posts using live menu, specials, loyalty, and website content.
AIR is in active beta. The day-one restaurant operating workflows are the priority; advanced growth features are being layered in carefully so we do not overpromise.
Beta operators get closer setup help, influence the roadmap, and can help shape the workflows that make AIR practical during real service.
Still deciding?
The demo shows menu upload, website enhancement, direct ordering, and the owner workflow. That is usually clearer than another sales page.
I can answer questions about AIR, cutover, pricing, and setup.
One Maestro. CFO-minded. Same brain for chat and voice.
Ask about operations, phones, menu, delivery, marketing, cutover, or growth. Maestro answers with the owner's margin and time in mind.