Soho Connect Research Desk
What the mining-camp WiFi model actually is
A mining-camp WiFi system combines an upstream internet connection, managed access points, a captive portal and an access policy. The operator can provide free access, sell time or data vouchers, sponsor selected services, or use a hybrid model.
The business case should not begin with an assumed profit figure. It should begin with five measured conditions:
- the number of people regularly on site;
- the quality and cost of the available upstream connection;
- realistic demand for paid or sponsored access;
- the power and coverage design required for the site;
- the operating cost of support, monitoring and replacement equipment.
A safer revenue model
Use the WiFi Token Revenue Calculator to test scenarios rather than treating a forecast as guaranteed income.
Illustrative monthly revenue can be modelled as:
active paid users × average paid sessions per month × average session price
Then subtract upstream data, power, support, payment collection, maintenance and equipment-replacement allowances. A conservative model should test low, expected and high adoption rather than one optimistic number.
Open the WiFi Token Revenue Calculator.
The system architecture
Upstream connectivity
The site may use fibre, fixed wireless, LTE or satellite depending on availability. The chosen connection must be assessed for capacity, latency, fair-use restrictions, weather exposure and recovery when the primary link fails.
Gateway and captive portal
The gateway controls authentication, vouchers, session limits, bandwidth rules and usage records. The login experience should clearly explain the access terms and what customer information is being requested.
Coverage layer
Access points should be placed from a site survey, not from an indoor-office assumption. Worker accommodation, common areas, offices, workshops and outdoor gathering points may need different equipment and mounting methods.
Power layer
Remote sites need a load schedule covering the gateway, access points, upstream equipment, monitoring hardware and expected operating hours. Solar and battery capacity should be sized from measured consumption and local conditions, with an allowance for poor-weather days and battery ageing.
Operations layer
A working deployment needs remote monitoring, a fault-escalation path, voucher controls, staff training, spare-equipment planning and a clear policy for acceptable use.
Deployment sequence
- Survey the site: map buildings, user concentrations, power, obstructions and existing connectivity.
- Define the access model: free, paid, sponsored or hybrid.
- Model capacity and economics: test conservative demand and operating-cost scenarios.
- Design coverage and power: select the uplink, gateway, access points, mounting and backup power.
- Pilot one zone: validate coverage, login completion, payment handling and support workload.
- Instrument the system: monitor uptime, congestion, voucher use, failed logins and support incidents.
- Expand only after evidence: roll out further when the pilot proves the operating model.
What should be measured
- successful login rate;
- peak concurrent users;
- bandwidth saturation;
- uptime and recovery time;
- voucher or sponsored-session use;
- support incidents per active user;
- repeat use;
- operating cost per active user.
Privacy and customer trust
Collect only the information required for the access or marketing purpose. Explain what is collected, how it will be used and how a user can obtain help or opt out of promotional communication. Access credentials, administrator accounts and usage records should be protected as operational data.
What would change the recommendation?
The design changes when the site population, upstream service, power conditions, terrain, payment process or customer demand differs from the initial assumptions. A site survey and a measured pilot should therefore control the final architecture and commercial decision.