The Day 300 Students Showed Up.

Brian Mwangi never expected a university newsletter to change everything. CampusLink started as a side project between two computer science students in Nairobi — connecting students with local vendors, tutors, photographers, second-hand textbook sellers, and small businesses, all in one place. Between lectures and late-night coding sessions, they built the first version using React, Node.js, and PostgreSQL, proving that two students could ship a real product with almost no budget.

Getting people to use it was the next challenge. Like many student founders, Brian relied on free hosting to keep costs at zero. It worked — until it didn't. After free tiers disappeared, the cheapest alternative came with a frustrating trade-off: the application went to sleep after thirty minutes of inactivity. Every new visitor had to wait around eight seconds before the homepage even appeared. Most never did.

Friends kept telling Brian they had tried the platform but assumed it was broken because nothing happened after they clicked the link. It wasn't the product that was disappointing people. It was the infrastructure behind it.

"It wasn't the product that was disappointing people. It was the infrastructure behind it."

Then came the day everything changed. The university featured CampusLink in its weekly newsletter. Within a few hours, more than 300 students had signed up to try the platform. It should have been their biggest milestone. Instead, the application crashed before the afternoon was over.

Brian watched new users arrive in real time while sitting in class. The traffic was there. The interest was real. But the infrastructure couldn't keep up, and there was nothing two students with almost no budget could do in that moment. That evening, they decided to rebuild the way they deployed software — not the product itself.

Connecting their Git repository meant every new version could be deployed with a single push. Their PostgreSQL database became a managed service instead of another responsibility. They finally had a stable application URL they could confidently share across campus, and paying for infrastructure became as simple as topping up a prepaid wallet with M-Pesa. Even better, if the balance ever reached zero, the application would stop instead of creating debt they couldn't afford.

For two students building between exams and assignments, that mattered just as much as performance. A month later, CampusLink felt like a different product. The cold start was gone. The URL always responded. The product was finally able to speak for itself.