Core v0.5 implemented · external integration, hardware security and venue validation next

One scan.
Start ordering.

The product target removes the need to find Wi-Fi, type a password and scan a second code. WiFi Order combines venue connectivity, an authenticated table session and the existing ordering page. Once authenticated, guests can use an isolated public-Internet service; onboarding and enforcement still require verified IronWiFi, AP or Gateway and phone evidence.

Keep the existing POS No guest app Prove value before rollout
Target guest journey

Reduce pre-order friction to one step

Core v0.5 automated checks passed
01
Scan the table entry

The guest starts from one clear entry point.

02
Connect to the venue

Select and verify Captive Portal, WPA-Enterprise or Passpoint onboarding during the PoC.

03
Use isolated guest Internet

Authenticated guests can browse public sites while other guests, POS, payment and management networks remain unreachable.

04
Open the correct table

Reach an allowlisted ordering page; closing the table immediately denies entry and starts network revocation.

Existing menuExisting ordersExisting paymentsExisting brand
Verified project status

Core v0.5 passes automated verification; real venue and network evidence remain release gates

What is verified is production-shaped core software and a simulated end-to-end journey—not a completed commercial deployment. External platforms, physical networks, phones and payment journeys still require venue evidence.

Implemented

Core and guest-network policy

Multi-tenant API, TableSession, temporary credentials, NetworkAuthSession, Portal Grant and Resolver, immediate denial on close, authenticated_guest_internet and ordering_path_only modes, IPv4/IPv6 parity, emergency disable, audit and metrics.

Automated checks passed

84 tests, including 58 security tests

The Mock Network Adapter and Gateway Simulator cover create, authenticate, redirect, public-Internet authorization, close, revoke, offline, delay, failure and retry. Core v0.5 CI, Dependency Review and CodeQL pass.

Required before launch

Real network, payment boundary and paid venue

IronWiFi, a Verified AP/Gateway/firewall, iOS/Android, IPv4/IPv6 isolation, VPN and Private DNS, independent penetration testing, the existing ordering platform and hosted payment page, and venue outcomes remain unverified.

Best-fit venues

Not every restaurant needs WiFi Order

We only work with venues where the problem already consumes staff time, causes guest abandonment or creates operating cost—not venues that merely want another novel feature.

Good fit

The problem is frequent and costly

Basements, malls, food courts, hotels, venues or thick-walled buildings where guests often need help because of reception, Wi-Fi or repeated scanning.

Poor fit

A normal QR flow already works

When mobile data is reliable, guests instantly open the ordering page and staff rarely handle table or connection issues, adding equipment and steps is not recommended.

01

Weak-signal venues

Pages fail to load or take too long, forcing staff assistance or manual ordering.

02

Too many entry steps

The table has separate Wi-Fi and ordering codes, requiring guests to switch between camera, settings and browser.

03

Consistent venue management

Multi-site groups, malls, hotels and venues want one managed guest-entry workflow instead of store-by-store manual setup.

Business value

We do not sell networking technology. We prove operating outcomes.

The decision depends on whether the system reduces guest failures, staff intervention and wrong-table entry—not which protocol runs underneath.

Measure

Guest completion rate and time

Record whether each scan reaches the correct table and how long completion takes.

Compare

Staff intervention before and after

Compare assistance with connectivity, rescanning and manual ordering.

Decide

Expand only when the result is proven

Without measurable improvement, we do not recommend continued payment or rollout.

Next validation stage

Move from the implemented sandbox to external and single-venue validation

The next step is not a commercial-completion claim. It is a staged test of the Network Adapter, Verified hardware, network isolation, phones and hosted-payment journey before measuring willingness to pay.

01

Confirm external capabilities

Verify temporary credentials, a unique session reference, webhooks, redirect, revoke and disconnect with IronWiFi or an equivalent platform.

02

Validate hardware, phones and isolation

Select one AP/Gateway/firewall combination and verify IPv4/IPv6, guest and venue-LAN isolation, public browsing, VPN, Private DNS, rollback and physical iOS/Android journeys before marking it Verified.

03

Measure the real PoC and payment boundary

Verify the existing ordering platform redirects only to a trusted hosted payment page, then compare success, time, staff intervention, installation, security and support cost. Stop expansion when thresholds fail.

Venue qualification

Does your venue genuinely need this?

Describe a problem that has actually happened, not an ideal feature request. We will first determine whether a paid pilot is justified and will say directly when the venue is not a fit.

Basement restaurantsMalls and food courtsHotels and resortsVenue diningPOS and system integrators