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.
Lodge Internet · 14 November 2026 · 3 min read
The first commit in our code history is dated 9 March 2026. Most of what follows was built since. Every date below comes from that history, so treat each as the day the work was written down, which is usually but not always the day it reached you.
March
The website's first commits landed on 9 and 10 March, followed within days by a filter for transactions and a round of fixes for small screens. On 11 March, the support details became dynamic.
On 28 March came work on keeping hostels separate from one another, along with rate limiting, which slows down anyone hammering a form.
April
On 5 April, unlimited plans gained durations and custom dates, and admins got email drafts. On 12 April, the website got its customer sign-in route and the site-wide lockdown switch, the one that shows a maintenance message while we work. Admin user management followed on 13 April.
May
On 27 May we added the waitlist, so a student whose hostel we don't serve yet can ask to be told when we do, plus images in the emails we send.
June
On 25 June, hostels could be grouped together, and plans could be edited after they were made.
July
On 13 July the backend began as a service of its own, written in Python, with the website moving its logic across to it. On 22 July the WhatsApp bot made its first commit. TV access arrived in the backend and the bot on 24 July, and on 27 July the bot learned to explain how it works.
August
On 1 August we added low-stock alerts and proper handling for a plan that runs out of codes. On 10 August came the balance checker, so you could ask how much data is left on a code. On 29 August, codes started arriving automatically from the hostel Wi-Fi controllers instead of being uploaded by hand, and balance checks got faster.
September
On 1 September, TV subscriptions became automatic. On 18 September, hostels could be grouped by school, and the customer pages were redesigned. On 20 September, a change described in one line as making the client purely a client: the website showing what the backend says, and nothing more.
The last week of September was the start of the database move. The first Postgres schema is dated 27 September, and the layer that let us change databases without changing behaviour was built across 30 September and 1 October.
October
October was the month the foundations changed.
- 1 October. Every record moved from Firestore to Postgres. The same day, hostels gained a proper id link beside their names. The story is in Moving a live money system off Firestore.
- 2 October. Customer sign-in left Firebase Auth for our own, with sign-ins kept in cookies no script can read. Nobody had to reset a password. See Leaving Firebase Auth in a day.
- 4 October. Admin sessions became revocable, and the bot's plan list started showing the full checkout total.
- 5 October. Every payment notice from Paystack is now stored before anything is done with it, so one we can't match straight away is kept, not lost. See Webhooks get lost. Payments don't.
- 6 October. Every step in a code's life, from stocked to held to gone, began being recorded by the database itself, and every sale began being recorded as balanced ledger entries. Bot messages are now retried until WhatsApp confirms them, and balance checks name the exact voucher that was sold.
- 9 October. The backend learned to talk to self-hosted Wi-Fi controllers through their documented interface. The bot began keeping a daily count of messages per user, counts only, never what was said.
- 14 October. The balance check came to the website.
- 21 October. One price: the bot now charges exactly what the website charges. The same day, the bot opened on Telegram.
- 23 October. Wallets, each with its own bank account number, and our privacy policy.
- 24 October. A round of redesigns, including the privacy and wallet screens.
November
By 9 November, Firestore was fully retired. Everything runs on Postgres.
And on 14 November, this blog got its writing rules. Every post on it is checked against the code it describes, and a post goes up only after a person at Lodge approves it.
What's next
We don't publish dates for work that isn't live. When something new ships, it will show up in What's New, and the posts here will be checked against the code again. If you want the shortest route to buying a code today, start with Wi-Fi in two minutes.
Last checked against the product on 14 November 2026.