CreaNext runs a website, a client app, two team apps, a billing system, an exam platform and several small tools, and most of the code comes from one developer. The only way that works is a stack that is boring, cheap and easy to maintain. Here is what I picked.
One identity layer: Firebase
Every CreaNext product signs people in through the same Firebase project, and stores real-time data like chats, requests and project stages in Firestore. A client who signs up on the website can open the Android app and see their projects immediately. One account system means one thing to secure.
Mobile apps with Capacitor
The client app, the Admin and Support apps and Munimji are web apps wrapped as native Android apps with Capacitor. The client app is built with Vite and plain JavaScript, with no heavy framework. That keeps the APK small, lets me reuse web skills, and means a change can ship to the website and the app together.
Static where possible, APIs where needed
Most of creanext.in is static HTML, CSS and JavaScript, which is fast and almost impossible to break. The parts that need a server, like payment links, video uploads and push notifications, are small PHP endpoints that check a Firebase token on every request and only let each user touch their own data. Bigger services, like CreaNext Billing's cloud, run on Node.js.
Payments with PhonePe
Clients pay by UPI, card or netbanking through PhonePe. Amounts are always read on the server, never trusted from the browser, and receipts are stored against each project.
Edge functions for AI
AI features like Prompt Studio run on Cloudflare Workers, which are cheap, fast and keep API keys off the client. Each one has a non-AI fallback, so the product still works when a model is slow or down.
Hosting on Hostinger
All the sites, subdomains and the Node.js services are hosted on Hostinger, including client websites on yourname.creanext.in. A single hosting account for everything keeps costs predictable for a bootstrapped studio.
What I would tell another solo developer
- Pick one sign-in system and use it everywhere.
- Make anything static that can be static.
- Never trust the browser with money or permissions.
- Build the fallback before the clever feature.
Need something built on a stack like this? See our web development service or read everything I have built so far.