Built for the next way restaurants will run.

Innovation First means building useful connections with clear boundaries, not adding AI for its own sake. Everything on this page carries a label: In development, Platform build, Gated roadmap, or Emerging. Nothing here is sold as live.

APPLY FOR BETA ▸WHAT IS INCLUDED TODAY

THE RULE

Who decides what an AI can do in your restaurant?

You do. A restaurant chooses which capabilities are exposed. An AI client may request a permitted action, but a deterministic policy layer decides whether it is allowed, needs confirmation, or is refused.

Owner assistant

IN DEVELOPMENT

Authorised operational insight first, carefully bounded changes later. An assistant reads your reports and prepares routine admin for your sign-off.

· Starts read-only: operations snapshot, sales summary, inventory variance
· Then proposals: a menu or availability change as a diff you approve
· Never a generic 'do anything' assistant: staff roles, exports, refunds stay behind their own approvals

Guest assistant

IN DEVELOPMENT

Restaurant-approved menu and venue discovery for compatible AI clients. Guests ask about dishes, allergens and hours from your published data.

· Narrow first scope: restaurant information, menu search, item detail you choose to expose
· Future guest actions tied to the right table context only
· Reservations, history and payment handoff are separate future domains

Vibe-coding kit

PLATFORM BUILD

The controlled developer path: AGENTS.md law file, plugin SDK with examples, predeploy gate. Your developer or your AI tool builds against it.

· API first, then SDK, CLI, webhooks and extension paths on the same rules
· Extensions are additive and permissioned: no unrestricted database, auth or payment access
· Hosted RestaKit AI editor: coming soon, the recommended path

Plugin catalogue and marketplace

GATED ROADMAP

First-party plugins ship free with updates. Third-party plugins install with a named source and a permission review. A marketplace only once signing, isolation and rollback controls exist.

· Payments arrive as the first plugin; card data never touches your engine
· Every plugin declares routes, tables, events and permissions in a manifest
· Isolation hardening lands before any non-RestaKit plugin is recommended

Permissions, consent and audit

PLATFORM BUILD

Future connected tools must respect the restaurant, the user, the role, the location and the agreed scope. Every action leaves a record.

· Identity, restaurant membership, role, scope and risk checked before any tool acts
· Consent shows the client, the restaurant, the user and the exact access requested
· Narrow permissions, rate limits, idempotency and a human escalation route

Browser-side agents (WebMCP)

EMERGING

An emerging browser-side concept. RestaKit does not implement it today and will not present it as available until it is.

· Not a shortcut around the controls a remote connection needs
· Explained separately from our remote assistant direction
· Belongs in an emerging-technology context, not a product claim

Own the copy that gets these first.

Every item above ships to existing copies as a signed update. Beta partners see them first and shape them.

APPLY FOR BETA ▸

Beta invites · limited places · no payment to apply