Servio Restaurant
| Type | Restaurant operations software |
|---|---|
| Part of | Servio |
| Founder | Lior Amsellem |
| Status | Live core modules; pilot / in development for the rest |
| Platform | Web; iPad app submitted to the App Store |
| Positioning | Host stand and menu, beside the existing POS |
| Website | servio.fit/restaurant |
Servio Restaurant is a restaurant operations product within the Servio ecosystem, built by Lior Amsellem. Its working core is the front of house: reservations, a live floor plan, a waitlist and menu management, presented on one board for the host stand. It is positioned to sit beside whatever point-of-sale a restaurant already uses rather than to replace it, and its own website labels the features that are not yet ready as such.[1]
Current capabilities
| Module | What it does | Status |
|---|---|---|
| Reservations | A public reservation page under the restaurant's own link; holds and confirmations; reservations appear on the floor plan | Live |
| Floor plan | Rooms, patio and bar zones drawn with the restaurant; table status; a party moved by drag, with its timer and server | Live |
| Waitlist | Walk-ins quoted from real turn times rather than a guess; seated with one tap | Live |
| Menu management | Sections, modifiers, allergens, 86 controls, import from a photographed menu | Live |
| Restaurant website | A simple public site with the menu and the reservation link | Live |
In development or under evaluation
The following exist in the product in some form but are not offered to restaurants as live capabilities. Each is labelled on the product's own site.
- Kitchen workflows — a kitchen display with station routing. Pilot only
- Order management and checks — fire, split, transfer, refund. Pilot only; never run in a live service.
- Payment integration — card payments through the restaurant's own Stripe account, pay-at-table by QR, and an NFC tap-at-table concept. Built; switches on with payments, which require the restaurant's Stripe onboarding to complete.
- Employee management — schedules, clock-in by PIN, timesheets, tips and payroll reporting. Not deployed pending review.
- Restaurant financial reporting — recipe costing, menu profitability, expenses and debts. Not deployed pending review.
- Delivery-platform integrations — Uber Eats (credentials configured, no merchant has connected) and DoorDash (architecture only). Not connected
Positioning
Servio Restaurant is sold as the host stand and the menu. The comparison it invites is with the notebook and the text thread most independent restaurants use at the door, not with a full point-of-sale system. It does not claim to replace Toast, Square or similar systems, to integrate with them, or to connect to delivery marketplaces.
Pilot programme
The first restaurant customers are being sought through a two-week pilot offered to independent full-service restaurants in Miami: reservations page, floor plan, waitlist and menu, set up in one off-hours session, with nothing changed in the kitchen or the POS, in exchange for weekly feedback. The first pilots with independent Miami restaurants are being arranged; the product is demonstrated on a fully built sample restaurant.[2]
Status
Core front-of-house modules live at servio.fit/restaurant. An iPad app for the host stand and kitchen has been submitted to the App Store. Payments, kitchen, ordering, workforce, reporting and delivery remain pilot-only, undeployed or unconnected, as described above.
References
- servio.fit/restaurant, public product page with per-feature status labels, October 2026.
- Servio Restaurant pilot offer documentation, October 2026.