Coin-operated internet, done properly
Every coin,
exactly accounted for.
Integer-centavo accounting, MAC-bound sessions, and a coin acceptor that stays electrically dead until a purchase window says otherwise. Runs on a ₱1,000 board. Licensed per device, activated in seconds.
Raspberry Pi 3/4
Orange Pi One
Orange Pi PC
Orange Pi Zero 3
The purchase window, start to finish
The acceptor is only ever live inside these three steps — never before, never after.
-
01
Open a window
A client taps Add Time. The engine opens a purchase window bound to exactly one MAC address and energizes the coin acceptor.
-
02
Insert coins
Each debounced pulse adds centavos to that window only. The rate engine tracks the best combination in real time.
-
03
Time is credited
Tapping Done commits the optimal duration and authorizes that one MAC–IPv4 pair in nftables. The acceptor goes dead again.
Default rate table
Fully editable per site — this is what ships out of the box.
Multiple coins combine deterministically — the engine always resolves the longest duration that doesn't exceed what was inserted. No floating-point money, anywhere.
Built for the field, not a demo
Exact MAC–IPv4 authorization
Session state is bound to the resolved client, not a cookie. Closing the browser doesn't lose the session; a second device never inherits it.
Fail-safe GPIO
The acceptor-enable line is forced inactive at boot, outside a purchase window, on cancellation, and during shutdown — always, not just usually.
Offline-tolerant licensing
Signed, hardware-bound entitlements keep working through a configured offline window if the license server is briefly unreachable.
VLAN-isolated client network
A managed-switch trunk keeps client traffic on its own tagged VLAN, with automatic conflict-free subnet selection at install time.
One static binary
7–8 MB, no runtime, no database server. Config and state are atomic, root-only files you can back up with tar.
White-label ready
One engine, one license service, two storefronts. gpisotab and g-wifi run on the exact same appliance build.
Get your license key
One license per device. Activation binds it to that appliance's hardware ID — recovery re-issues a fresh device token if you ever need to re-provision.