01 / POS + Schedule → Finance
Sales & workforce → financial close
Sales, tender, cash and payroll packets retain source context as Finance brings them into intake, reconciliation, reporting and close review.
Engineering case / 01 / HospiEdge
Technology inside
HospiEdge.
An operating platform built from the realities of running a restaurant: the handoff from host to server, from ticket to kitchen, from time record to closeout, and from today’s exception to tomorrow’s plan.
Functional depth
The application suite in action.
From reservations and kitchen execution to staffing, hiring, guest marketing, label printing and financial close, HospiEdge covers the connected responsibilities of a restaurant.
Connected workflows
One workflow becomes the next team’s input.
02 / Ops audits → assigned planner work
Observation → corrective work
An audit finding can carry evidence, an owner, a due date and a completion standard into linked corrective work and management follow-up.
03 / POS item data → Label
Catalog → labeling workflow
Catalog imports, source pinning and matching feed item libraries and label templates, followed by print-job records and output confirmation.
04 / Application sources → Master AI → action review
Finding → reviewed action
Cross-app context supports findings and recommendations. Actions move through approval, revision, scheduling and completion states with a reviewable history.
Workflow examples summarize reviewed application contracts and action paths. Inspect the application-level capabilities →
Measured scope
A substantial maintained codebase.
Eight base operating applications, optional Master AI, central platform services, the product hub and shared deployment tooling are measured as distinct source areas.
1,012,537
Nonblank implementation lines
2,430
Unique implementation files
228,568
Separate verification-source lines
Physical source lines excluding blank lines; includes comments, templates and styles. Third-party packages, generated outputs, evidence archives and exact duplicate files are excluded. Verification code is counted separately.
Inspect the component breakdown
| Area | Unique files | Nonblank lines |
|---|---|---|
| Finance | 99 | 50,939 |
| Jobs | 63 | 65,883 |
| Label | 94 | 77,810 |
| Marketing | 176 | 75,306 |
| Master AI | 183 | 87,238 |
| Ops | 61 | 6,320 |
| Platform | 192 | 61,871 |
| POS | 368 | 172,789 |
| Public product hub | 166 | 16,763 |
| Schedule | 189 | 121,411 |
| Shared system & delivery | 458 | 118,538 |
| Table / EYS | 381 | 157,669 |
Inspect the language breakdown
| Language / file type | Unique files | Nonblank lines |
|---|---|---|
| C# | 1 | 60 |
| CSS | 53 | 80,715 |
| HTML | 29 | 515 |
| JavaScript | 50 | 23,550 |
| Kotlin | 22 | 1,760 |
| PHP / templates | 2,016 | 871,838 |
| PowerShell | 138 | 27,967 |
| SQL | 121 | 6,132 |
Architecture
Shared context.
Defined system boundaries.
Conceptual structure of the maintained product. Each application owns its operating responsibilities and exchanges approved records.
ACCESS & CONTEXTShared identity · Tenant · Restaurant · Location · Role
01
People
Schedule and Jobs connect workforce planning, hiring, availability, time records, and onboarding.
02
Service
POS and Table support tickets, kitchen routing, reservations, waitlists, seating, and guest flow.
03
Standards
Label and Ops support food labels, procedures, manager logs, incidents, audits, and follow-through.
04
Control
Finance and Marketing work with approved operating records for reconciliation, reporting, campaigns, and review.
RECORDS & HANDOFFSDefined record owners · Approved transfers · Reconciliation
Hosted platform
Account authority, connected workflows, and central provider integration.
Optional Hybrid
Bounded POS and Table continuity on a Windows computer.
Optional Master AI
Supervised review of permitted context and source-linked findings.
Engineering decisions
What has to work beneath the screens.
Identity & access
Tenant, restaurant, location, role and application entitlement define access. Central authority supplies a signed, scoped identity projection for the supported Hybrid installation.
Operational data contracts
Sales, workforce, guest-flow and management records retain defined ownership. Shared views and reconciliation consume those records through explicit application contracts.
Hybrid continuity
POS and canonical Table/EYS form the local operating scope. Durable record identity, retry handling and synchronization protect the handoff between a Windows installation and hosted services.
Payment integration
Central services own provider secrets and callbacks. POS and Hybrid clients operate through the platform boundary, with restaurant payment processing distinct from software subscription billing.
Supervised AI
Optional assistance uses permitted context, bounded structured responses and deterministic fallbacks. Management review remains connected to source records and the workflow that owns them.
Reproducible delivery
Maintained source is separate from installer and hosting output. Signed artifacts, file hashes, preimages, controlled activation and recovery records make a release inspectable.
Current rebuild assessment / USD
$1.40M–$3.00M
Estimated engineering replacement cost
The work to reproduce equivalent functionality, integration and delivery discipline with a competent team using established frameworks and contemporary development tools.
- Lower scenario
- 12,700 hours × $110
- Central scenario
- $2,125,500
- Upper scenario
- 20,000 hours × $150
September 5, 2026 · AI-assisted rebuild estimate, published by Bennett Edge Group. Measures replacement effort, not historical spending or company market value. Inspect the methodology →
Verification evidence
Confirmations with a traceable basis.
Selected records demonstrate identity controls, recovery, release integrity, installed maintenance and guest-ordering behavior.
Confirmed2026-08-22
Signed identity & deployment transport
16/16 central authentication; 18/18 signed scope; 18/18 local identity; 48/48 deployment transport assertions.
Recorded focused identity and transport acceptance.
HE-IDENTITY-0822Confirmed2026-08-22
Backup, migration & recovery
Restore rehearsal, initial application, repeat application, rollback, unrelated-state preservation, advisory locking and fixture cleanup verified.
Recorded isolated database rehearsal for the Hybrid sync migration.
HE-RECOVERY-0822Confirmed2026-08-22
Hybrid package integrity
2,226 manifested package files; signed identity projection matched; canonical Table scope confirmed; zero forbidden paths or secret-like scan hits.
Recorded acceptance of the August 22 Hybrid release artifact.
HE-RELEASE-0822Confirmed2026-08-22
Installed update lifecycle
Version 1.0.0 → 1.0.1 accepted: signed offer and private download, exact readback, restart, POS/Table response and staging cleanup.
Recorded customer-confirmed maintenance update with retained backup.
HE-UPDATER-0822Confirmed2026-08-28
Ordering & bounded AI assistance
112/112 online-ordering checks; 33 assistant runner checks; 50 zero-network fixture checks; 79 shared-AI credential-contract checks. Desktop and phone interactions confirmed.
Recorded source and browser-fixture acceptance for the scoped ordering change.
HE-ORDERING-0828Selected, dated acceptance records reviewed for this assessment. Each confirmation applies to the named artifact, workflow and test environment. Receipt fingerprints are included in the downloadable assessment.
The operating knowledge
Thirty-six years inform the model.
Shalom Bennett began working in hospitality at sixteen. His experience spans kitchen and service roles, work as a sous chef, and more than fifteen years leading operations as a general manager.
That knowledge helps define the product’s workflows and exceptions. The rebuild model estimates software delivery effort; the founder’s historical experience is not assigned a dollar value.
Read the founder profile →PRODUCT & ENGINEERINGThe operating day
The operating day
is the design context.
People. Service. Standards. Control.
Explore the HospiEdge applications ↗Let’s talk
Review the build in depth.
Discuss the component boundaries, verification records, licensing scope and rebuild assumptions.