Available

Eve drafts the work. Your team decides.

Most restaurant AI either chats in a vacuum or takes actions nobody can audit. Eve works inside the operating table, within your venue and permission boundaries, and stops at a review point.

A general manager standing in a quiet dining room before service, holding a tablet
Across the shiftAI & Automation

Operators who want assistance inside the operating model.

Teams that will accept a draft and reject an unsupervised send, publish or payment.

01

What Eve is allowed to see

The services and records your role can already reach, plus the files you attach to a conversation, such as an availability sheet or a photo of a delivery note.

02

Organize the context

Eve reads the venue’s own records and your attachments; it does not invent a guest or a number.

03

Propose, then stop

A schedule draft, a validation or an integration setup is a proposal. Approve, edit or reject remains a person-owned control.

04

Leave a trace

Every approved action runs through a named executor and is recorded with who approved it.

A supervised agent with real, approval-gated executors.

Eve reads attachments and proposes schedule drafts, validations, publications and amendments for Team & Payroll, and connection preparation for Integrations. Automation rules persist for review; condition evaluation and content generation stay switched off by default.

StatusRules persist for review; condition evaluation and generation remain unavailable.

Eve is not an always-on employee.

No uncontrolled outbound actions, no payments, no publishing without approval, and no claim that every specialist is live.

Reads your attachments
Proposals, not actions
Named executors with approval
Off by default where it matters

The other nine services, one click away.

Every service shares the same account, venues and permissions. Open any of them and the context comes along.

Define the actions Eve must never take.

Bring the decisions you will not delegate. That list is the product.