Security isn't a phase two
Most small businesses get software that looks finished and isn't defended. A breach doesn't cost them a sprint — it costs them the business. So hardening comes first here, not after launch.
Meroidea is one developer's answer to a stubborn question: what if everything I build, learn and teach lived in one place — engineered properly, secured properly, and shared openly with anyone who wants it?
Founded by Sujan Darji · Pokhara → Sydney
Act I — How it started
No garage, no seed round, no overnight breakthrough. Just a question that refused to go away, and a decade of answering it one build at a time.
Chapter 01 — The Name
Meroidea begins in Pokhara, Nepal, with a kid who took things apart to find out why they worked — a philomath long before he knew there was a word for it. That curiosity crossed an ocean to Sydney and into a Bachelor of Information Technology at Victoria University, where “how does this work?” quietly became “give me a weekend and I'll build one.” The name arrived later, and it arrived easy. In Nepali, mero idea means my idea. Not a borrowed one, not a committee's — mine. And now, open for anyone to take further.
Chapter 02 — The Craft
Lectures explained things; projects convinced. A hospital patient-management system in Java and MySQL that won Best Group Project. A complete online management platform for a driving school, architected MVC from the ground up. A business-intelligence system with live dashboards sitting on Postgres. Each one came with real sprints, real code reviews and a shared Git history — and a place on the Dean's Honour List along the way. But the lesson that stuck was smaller and more stubborn: you don't understand a system until you've had to keep it running.

Chapter 03 — The Work
Then people started betting their livelihoods on the work. A photography studio in Sydney. An AQF-accredited training institute. A family health platform in Kathmandu. A migration consultancy operating across two continents. When real users and real data are on the line, “it works on my machine” stops being funny. So everything ships secure by design — hardened authentication, row-level security enforced in the database itself, OWASP-aware engineering from the very first commit. Not to satisfy a checklist. Because somebody's business opens tomorrow morning on top of it.
Chapter 04 — The Mission
The fastest way to find the holes in your own understanding is to explain it to someone who will ask why. So Meroidea grew a classroom: six full courses — data structures in Java, MERN full-stack, an AI/ML job-ready program, computer networking, cybersecurity and PTE Academic — alongside free articles, annotated problem walkthroughs and a curated library of open textbooks. Every lesson is written by the person who had to learn it the hard way first. That's the whole loop: what gets learned gets built, and what gets built gets taught.
Every complex system was once a simple idea, kept alive by someone who refused to let it go.
Act II — What Meroidea offers
One side builds software for businesses that can't afford to get it wrong. The other teaches anyone who wants to build it themselves. The same hands do both — which is exactly why neither goes stale.
Custom platforms and SaaS products with security built in from the first commit — hardened auth, row-level data policies, OWASP Top 10 coverage, automated backups.
Executive-level technical direction without the executive headcount: an audit of how you actually operate, then a clear roadmap for stack, cloud and workflow.
The quiet engines behind a business — pipelines, assistants trained on your own data, and generative AI wired into the systems you already run.
Every engagement starts with a plain-English audit of what you actually need — not a quote for what's easiest to sell.
Start a conversationCourses are priced so a student can afford them — and the first five lessons of each are free, so you can judge the teaching before you pay for it.
Pick a courseAct III — Why it matters
A platform is only as good as the convictions underneath it. These are the four that decide what gets shipped here — and what gets refused.
Most small businesses get software that looks finished and isn't defended. A breach doesn't cost them a sprint — it costs them the business. So hardening comes first here, not after launch.
The same lesson that unlocks a student in Sydney unlocks one in Pokhara. When knowledge is put online properly, geography stops being a gatekeeper — and that's the point.
Work scattered across a résumé, a repo and a dead hard drive evaporates. Held in one living platform, every project teaches the next one — and teaches everyone reading.
Anyone can follow a tutorial. Explaining a system to someone who will ask why is where real understanding gets tested — and where it finally becomes someone else's too.
Whether you need something built properly and defended from day one, or you want to learn to build it yourself — the door is open, and it always will be. That was the whole idea.