By day, I teach school in Jaranwala, a small city in Punjab, Pakistan. I also train other teachers in how to use AI in their classrooms. In my remaining hours, I run Loona Automation — a network of 30 tool websites holding 883 free tools, every one of them published in 40 language editions.
No sign-up. No downloads. No servers doing the work. Everything runs in the visitor's own browser, on their own device.
This past weekend I shipped 12 new tools in one go. This post is about how that network is built, why I made three unusual decisions — client-side only, 40 languages, and a strict three-check quality rule — and what those decisions have taught me.
My mission has a name in Urdu: Bolti Duniya — "a world that speaks." The idea is simple: every book should speak, in every language, for everyone who cannot read.
That mission shapes the engineering. If a tool is meant for everyone, it cannot ask for an account. It cannot demand a fast connection to a distant server. It cannot be in English only. And it cannot cost money, because the people who need free tools the most are the ones least able to pay for them.
So the rules for every Loona tool are fixed:
Client-side-only is the decision people question most, so let me explain it honestly.
A server costs money every month, for every user, forever. A static page on GitHub Pages costs nothing to serve, whether ten people use it or ten thousand. For a one-person project funded by a teacher's salary, that difference is the whole project.
Privacy is the second reason. When someone converts a photo, checks a resume, or generates a class attendance register on Loona, their file never leaves their device. There is nothing to leak because there is nothing to collect. I don't have to ask visitors to trust me with their documents — the architecture makes the promise for me.
The third reason is speed and reliability. No round trip to a server means the tool works the moment the page loads, and it keeps working on the slow connections common in my part of the world.
The honest trade-off: some things simply can't be done well in a browser, and I don't pretend otherwise. I would rather offer 883 tools that genuinely work on-device than promise server-grade features I can't sustain.
When someone searches Google in their own language, they deserve to find a tool in that language too. So every Loona site exists in 40 full editions: 35 languages, plus 5 regional variants such as US and UK English and Brazilian and European Portuguese.
These are real translated editions, not a JavaScript text-swap button. Each edition has its own pages, its own navigation, its own search index. That is slower to build and much harder to maintain — 40 editions means every fix has to be verified 40 times — but a teacher in Istanbul or Jakarta should feel the tool was made for them, because it was.
The newest additions, one per real problem I kept seeing:
Every one of them shipped in all 40 editions, not just English.
Here is the lesson I would give anyone building in public: never trust your own "done."
Every Loona release now passes three separate checks:
This weekend alone, the second and third checks caught things the builders had missed: a print layout defect in a new tool that only appeared on paper, published tool counts on the hub that no longer matched reality after the new tools landed, and a broken block in one language edition's sitemap. Each one was small. Each one would have been a real visitor's bad experience. All were fixed before I called the work complete.
The rule costs time. It is worth it. A free tool that fails once doesn't get a second chance from most visitors.
Start with one real problem from your own day. Mine were lesson plans, registers, and date sheets — the paperwork of a school. Solve it completely, for free, in the language of the people who have the problem. Then solve the next one. Eight hundred eighty-three tools sounds like a strategy; honestly, it was just that habit, repeated.
The same packs behind some of these tools also exist as 35 AI skills on Agensi, for people who work through AI agents — but the websites remain the heart of it, because a website asks nothing of the visitor at all.
If any of the 883 tools can save you ten minutes this week, they're all in one place: I'd genuinely like to hear which tool you'd want next — the comments are where most of my roadmap comes from.
— Aurang Zeb Loona
School teacher & AI teacher trainer, Jaranwala, Pakistan
Founder, Loona Automation