How it works
One account per person. The vessel’s network does the rest.
The account lives in the InletPass service. The vessel’s Wi-Fi asks that service who may connect, and reports how much data each person used.
- 1Account and purchasesThe phone talks to the InletPass service.
- 2“May this person connect?”The vessel’s Wi-Fi asks; FreeRADIUS answers.
- 3Usage reportsThe Wi-Fi reports data used; the balance updates.
- 4BrowsingGoes out over the vessel’s own link, never through InletPass.
In six steps
From a new account to managed access.
- 01
A person creates an account
The allowance belongs to the account, not the device.
- 02
Crew access starts with eligibility
The desk invites temporary crew with an allowance and an end date.
- 03
FreeRADIUS checks who can connect
The network asks, InletPass answers, the access points apply it.
- 04
The network reports data use
The balance reflects the latest report, not a live meter.
- 05
Premium runs down; free access remains
When premium is used up, the account falls back to free access.
- 06
Staff handle exceptions only
Passengers help themselves. The desk handles invitations and support.
What is working today
Demo, evaluation and pilot, side by side.
| Capability | Public browser demo | Private evaluation | Confirmed in your pilot |
|---|---|---|---|
| Passenger account and balance | Simulated in the page | Working, hosted on Azure | Your data policies |
| Email and text messages | Sample codes shown | Real emails. Texts await provider approval | — |
| Card checkout | Simulated | Stripe test cards; no real payment | Your payment arrangement |
| Crew invitations from the desk | Simulated | Working | Your allowances |
| Work sign-in for crew | Simulated | Not enabled | Your identity provider |
| Network access and usage reports | No network involved | FreeRADIUS tested with simulated equipment | Your access points and timings |
Working Simulated Not available yet
Proposed production hosting
Plan for failures before going live.
Planned, not deployed. Two of each service in separate Azure zones, a database with a standby, and restorable backups. It cannot repair an onboard power failure or a lost satellite link.
Recovery, failover and support details
Network failover settings are tested during integration. Database connections can be interrupted while a standby takes over. A separate-region recovery plan, recovery targets, retention and support coverage are agreed for each deployment.
From this demo to your fleet
Three steps before a wider rollout.
Confirm the equipment
Access points, identity provider, payments.
Test on the real network
Accounting, allowance changes, failover.
Pilot one vessel
Measure real delays before going wider.
Questions evaluators ask
Details, when you want them.
Can someone get a new allowance by changing devices?
Passengers register with an email address or phone number. Changing a device’s randomized MAC address does not create a new data balance. Network session identifiers still connect each device’s usage to the right account.
How will crew sign in with their work account?
The planned Microsoft Entra ID integration checks an approved crew role through the operator’s work sign-in. It is not enabled yet.
How current is the balance a passenger sees?
Compatible access points send session and byte-count reports. Repeat reports are reconciled rather than charged twice. Reporting intervals depend on the access points and their configuration; reports can lag.
What happens at the moment premium data runs out?
Crew and purchased allowances are tracked separately. Applying the change depends on the network and may require reconnecting. Free access still needs a working vessel internet connection.
Who sets prices and allowances, and who runs it?
The operator sets free access, packages and crew allowances. The system can be run by the customer, its provider, or with optional hosting and support from Inlet Solutions.
Does the demo prove an instant cut-off when data runs out?
No. Usage arrives in periodic reports, and applying a change can require the device to reconnect. The hardware pilot establishes the practical delay.
Does passenger traffic pass through InletPass?
No. Only access requests and usage reports travel between the network and the service.
A pilot confirms the supported network settings, reporting interval and recovery behaviour on the equipment you will use.