Blog
How Lodge Internet works, how to get the most from it, and what we've built along the way.
How a Wi-Fi code gets from a hostel router to your phone
The short code you type into your hostel's Wi-Fi page was made by the hostel's own network, copied into our stock, held for you, handed over once, and emailed. Here's the whole trip.
For everyone
Why our bot sometimes goes quiet
Since 1 October 2026, WhatsApp bills us for bot replies past a monthly allowance. So our bot packs more into each message, answers a repeat once and then waits, and points you to Telegram, where none of that applies.
For everyone
One price, wherever you buy
The website and our WhatsApp and Telegram bot charge the same total for the same plan, because our server works it out in one place and both of them simply show it.
For customers
Our terms, read for you in five minutes
A plain summary of our Terms of Service, Privacy Policy, Refund & Wallet Policy, Acceptable Use Policy and Cookies notice, with a link to each full page.
For customers
A new website, built for the phone in your hand
We redrew the Lodge Internet website for phones first. Here is what's different: finding your hostel, the new bars and sheets, dark mode, wallet card designs, and a one-time hello from your wallet.
For everyone
The rules we build by
Every change to Lodge Internet is held against a short written list of rules. Here they are in plain words, with the reason each one exists.
For everyone
2026 so far: what we built, month by month
From the first commit in March to a new database, a new sign-in, one price and a Telegram bot in the autumn. Every date here comes from our own code history.
For everyone
Your wallet has its own bank account number
Top up your Lodge wallet by transfer to an account number opened just for you. Every naira lands in full, extra stays yours, the balance doesn't expire, and a transfer can finish a waiting order by itself.
For customers
Why your account is linked to your hostel
A code only works on the network it was made for, so your account belongs to one hostel. Here's what that means, what to do if you've moved, and why your wallet isn't affected.
For customers
Wi-Fi in two minutes: buying a code on the website
Find your hostel, pick a plan by how many devices it's for, pay from your wallet, by bank transfer or by card, and get your code on screen, by email and in your Account.
For customers
WhatsApp or Telegram? Same bot, different strengths
Our bot works the same on WhatsApp and Telegram, with one account, one wallet and one price. The difference is balance checks and how chatty the bot can afford to be, and here is the honest reason why.
For customers
Paid, but no code yet? Here's exactly what happens
Every safety net between your card payment and your access code, in the order each one kicks in, and the three details to send us if none of them do.
For customers
Find your hostel, and what to do if we're not there yet
How to find your hostel by school, area or name, what its own page is for, and how the waitlist tells us where to go next.
For customers
Signing in to a Wi-Fi controller with no browser, and the servers that logged each other out
To read a voucher's balance, our backend signs in to TP-Link's cloud the way a person at the dashboard would. The account allows one session at a time, and for a while our own servers kept signing each other out.
For engineers
Every code you've bought, in one place
Your Account page keeps your recent codes, live balances and TV subscriptions together. Show a code again, resend it by email, and see what this phone keeps for you and for how long.
For customers
Buy Wi-Fi without leaving WhatsApp
Say hi to our bot, pick a plan, transfer to your own account number, and your code arrives in the chat by itself. Card is there if you'd rather, and your wallet pays for whatever it can.
For customers
You never pay for a code you don't get
Before you pay, a code is set aside for you. After you pay, our server checks with Paystack itself and hands it over, even if you closed the page. Here is each step, and what happens in the rare case a code can't be issued.
For customers
One engine, three doors: how Lodge Internet is built
The website, WhatsApp and Telegram are three ways in to one backend that owns every price, stock count and balance. Here is how the pieces fit, and why the clients are kept deliberately simple.
For engineers
Small things that keep the website standing
Five small pieces of the Lodge Internet website that rarely get noticed, each written because something real went wrong without it, from stale tabs after a deploy to the Android back button.
For engineers
No token in JavaScript: cookie sessions and two API clients
Our website keeps every sign-in in a cookie no script can read, and a cookie only counts when the request says which part of the site sent it. This is the lesson that made us build it that way.
For engineers
Money arithmetic lives in one file
Why the browser never decides what a checkout costs, how the server quotes a total and checks the payment against that same total, and why partner payouts are worked out once, on the server, for every screen.
For engineers
Moving a live money system off Firestore without anyone noticing
On 1 October 2026 we moved every record from Firestore to Postgres. We did it by putting one interface in front of the database, teaching Postgres to answer exactly as Firestore did, and proving it byte for byte before the switch.
For engineers
Six characters aren't an address
Every Wi-Fi controller issues its own voucher codes, so the same six characters can exist on two networks at once. How a balance check works out which voucher you actually mean, and refuses to guess.
For engineers
How much is left on my code?
Check the data and days left on your code from the website's Account page or from our bot, what each answer means, and why we only show a balance to the account that bought the code.
For customers
Selling the last code exactly once
How the backend holds one Wi-Fi code for you before you pay, re-checks it inside the transaction, and makes the claim that hands it over safe to run twice.
For engineers
Making a website feel like an app
How we rebuilt the Lodge Internet website for a 360 px phone first, with colour tokens that flip for dark mode, glass bars, bottom sheets, and one Tailwind rule we learned the hard way.
For engineers
Your sign-in, and why scripts on the page can't touch it
How we keep you signed in on the website without any code on the page ever holding your sign-in, how to end a session properly, and how our WhatsApp and Telegram bot signs in on your behalf.
For customers
Leaving Firebase Auth in a day
On 2 October 2026 customer sign-in moved from Firebase Auth to our own backend. Nobody had to reset a password: we check Firebase's hashes with Firebase's own algorithm, then rewrite each one in ours the first time its owner signs in.
For engineers
Hostels by id, not by name
A hostel's name was its key everywhere, so renaming one left references behind and checks compared ids with names. How we're moving to ids, why a rename now runs references first and the hostel last, and why closing a hostel is a switch, not a delete.
For engineers
Credit first, then spend: the wallet that replaced three special cases
Every bank transfer now lands in the customer's wallet first, exactly once, and only then pays for whatever is waiting. Part-payments, overpayments and transfers with no order stopped being special cases.
For engineers
Getting help: who to message and what to send
Where to find a person when something goes wrong, which one to pick, and the few details that let us fix it in one reply.
For customers
A device list with no "add one" button
TV access at a hostel is a list of device addresses on the Wi-Fi controller, and the controller only lets us replace the whole list at once. Here is how we stop two purchases from erasing each other.
For engineers
Designing a chatbot when every message costs money
From 1 October 2026, WhatsApp bills us for replies past a monthly allowance. How that changed the way our bot talks, when it chooses to say nothing, and the tests that stop a stray message creeping back in.
For engineers