Elyra is an AI reservation and guest-operations system for restaurants. Its buyer is a restaurant group that loses bookings when the phone rings during service, emails wait for a reply or the reservation system fails to place the right party at the right table.
What it does
The current Elyra site describes a voice agent that answers calls, an email concierge that replies in the restaurant’s tone and smart table allocation that optimizes placements in real time. The platform also builds a guest profile from menus, preferences, booking history and service style, then supports follow-ups and return visits.
The YC launch says Elyra handles reservations, modifications, menu and dietary questions, policies and large-party requests. It also says the system launched with one restaurant, captured previously missed bookings and now powers top restaurant groups; those are company-reported customer claims. The site does not publish a base price.
Why I’d look closer
The advantage is completion. A phone agent that only answers still leaves staff to place the table; Elyra connects the call, email and allocation problem. Founder context fits the workflow: Felix Odeberg Glasenapp studied engineering physics at KTH and says he built Elyra after seeing restaurants lose bookings; Alan Mando is listed as co-founder.
The tradeoff is hospitality judgment. Menu substitutions, allergies, large groups, deposits, cancellations and special occasions can require a human who understands the restaurant’s actual policy. A table optimizer can also improve utilization while creating a poor guest experience if it ignores pacing or service capacity.
What I’d ask
Which reservation systems and table rules are supported? Can staff review or override a placement and see the reason? How are allergies, accessibility requests, deposits, cancellations and large parties escalated? Does the agent record every promise made to a guest? What does the system do when a menu or policy changes during service?
My editorial take
Shortlist Elyra if missed calls and inbox backlog are measurable revenue leaks and the restaurant has a stable reservation system. Start with overflow and routine bookings, keep dietary and policy exceptions human-reviewed, and compare captured bookings with guest complaints and table-turn quality. The product’s edge is connecting hospitality operations, not merely adding a voice bot.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | AI phone, email and table-allocation system for restaurants |
| Buyer | Restaurants and multi-location restaurant groups |
| Workflows | Reservations, modifications, guest questions, email and table placement |
| Pricing | Not published in the checked pages |
| Main question | Does automation capture bookings without making the guest experience or floor plan worse? |
Sources checked
| Source | Checked |
|---|---|
| YC company profile | 2026-09-19 |
| Elyra homepage | 2026-09-19 |
| Elyra about page | 2026-09-19 |
| Elyra YC launch | 2026-09-19 |
Cohort context
Elyra is listed in Spring 2026. In our 2026-09-18 directory snapshot, 112 of 193 listed companies in that cohort have YC’s primary industry label B2B (58.0%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19 16:16 UTC in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
