Core Pilot
For one venue validating the live service loop.
Pilot scope
- Operations Command Center
- Floor, tables, sessions, and orders
- Menu, variants, recipes, and stations
- Kitchen queue and ready signals
Pilot access
Hallify
Pricing that starts with operating scope
Hallify is in pilot-access packaging. The goal is to match the rollout to the venue workflow instead of pretending one public price fits every restaurant.
Role-safe operations
Permissions matrix
Live
OwnerOwner
Full venue control, owners, billing-sensitive setup.
ManagerManager
Operations, staff, stock, POS, analytics, limited owner actions.
WaiterService
Floor, reservations, guests, table service, order flow.
ChefKitchen
Kitchen queue, courses, item progress, ready signals.
Audit trail
Corrections, stock movements, payments, and member actions keep a traceable record for managers and owners.
Packages
Choose the rollout shape
No public price anchors until launch. These packages make the pilot conversation concrete.
Operations Pro
For teams ready to connect service, stock, staff, guests, and analytics.
Ops pilot
- Reservations and waitlist workflow
- Guest CRM, notes, tags, preferences
- Inventory, suppliers, purchase orders
- Staff, schedules, time clock, payroll, tips
- Analytics and manager attention queue
Network / Partner
For multi-venue, partner, or investor-led rollout conversations.
Custom rollout
- Multi-venue command center planning
- Owner and manager control model
- Custom onboarding and rollout scope
- Partner and investor operating review
How to read this
Built around honest pilot scope
Each package describes a rollout shape, not a locked contract.
Current product modules
Packages are based on implemented product areas: command center, floor, reservations, guests, POS, kitchen, menu, inventory, staff, analytics, and RBAC.
No fake feature promises
We avoid promising unavailable integrations on the pricing page. Network, partner, and custom rollout work stays conversation-led.
Practical rollout
The best pilot starts with the workflows that are painful today, then expands once the team is comfortable inside the operating loop.
Pricing FAQ
Early access is shaped around implementation reality, not public launch packaging.
No. These are early-access packages. Final pricing will be set after pilots prove the operating scope and rollout model.
A pilot should include the smallest complete workflow that can survive a real shift: service, permissions, kitchen or POS, and manager review.
Pilot setup can include venue structure, menu, recipes, roles, stock categories, suppliers, and staff basics depending on scope.
The product is browser-based. Hardware planning can be part of the pilot if a venue wants tablets, cashier devices, or kitchen screens.