We got tired of dollar hosting bills, so we built the platform
CloudNX is our own managed cloud hosting platform, built because Indian client deployments kept hitting the same three walls: dollar billing, no GST invoice, and support tickets that sit for 48 hours. One Indian region, rupee invoices, and our own products running on it.
The problem
Every Indian developer or agency hits the same wall when picking cloud hosting. AWS bills in dollars, support tickets sit for 48 hours, and DigitalOcean's cheapest tier is still about $6 a month before forex conversion, where variance on USD billing runs 2 to 5 per cent a month.
Support hours make it worse. A provider on an Indian support window saves roughly 8 hours of recovery time during an incident, and a 12-hour outage in the middle of an Indian business day is expensive in a way that does not show up on the hosting invoice.
The cheap way out is worse again. Most ₹99 a month shared plans deliver 6 to 9 second mobile load times, which quietly ends any hope of competing on Core Web Vitals. We were having this conversation on nearly every client deployment, so we built the platform we wanted to put those deployments on.
What we built
Next.js, Laravel, WordPress, Node.js and static sites deploy in a click on managed servers, with no SSH required unless you want it. The gap it aims at is the middle ground: shared hosting is too slow and too limited, raw AWS is too complex and too expensive for most projects.
Billed entirely in rupees, so no dollar conversion and no forex markup on the card statement. Every paid invoice carries GST against our GSTIN, so an accountant claims input credit the same way as any other Indian vendor bill.
Servers sit physically in Mumbai, so requests from the metros resolve in the low tens of milliseconds instead of routing overseas first. Keeping Indian user data in India is also what makes DPDP Act 2023 compliance straightforward rather than a matter of consent flows and contractual clauses.
SSL is issued and renewed per domain without anyone remembering to do it. Backups run daily against a 30-day one-click restore window, which is the difference between a bad morning and a lost client.
CPU, memory, disk, bandwidth and error rate are watched with email or Slack alerts on threshold breaches, on the view that a dashboard you have to remember to check is not monitoring.
Built for the case we were living: an agency running many client sites that wants infrastructure without a DevOps team, and one place to spin up, monitor and scale rather than a login per client.
How the architecture fits together
The platform runs on Next.js and Node.js with PostgreSQL and Redis, containerised with Docker, in a single Indian region. That one-region decision drives most of the rest of the design.
It buys low tens of milliseconds to users in the metros instead of an overseas round trip, and it keeps Indian user data in India. SSL is per-domain and automatic, backups are daily against a 30-day restore, and monitoring alerts on thresholds rather than waiting to be looked at. INR billing with GST invoicing is built into the platform rather than bolted on beside it.
We run CloudNX on our own infrastructure rather than reselling someone else's, which is the part that makes the rest of this page checkable: two production systems already sit on it.
Where it stands
- Launched 2026, with the free three-month offer live alongside the launch post on 30 April 2026: full platform access, as many projects as you need, no credit card to start and no auto-billing at month three.
- CloudNX managed WordPress now carries 80 per cent of our own client WordPress sites, with Cloudways covering the rest. Client Laravel work goes to DigitalOcean Mumbai or a CloudNX VPS.
- PlugEV, our production OCPP platform, runs its whole stack on CloudNX, with the Go gateway on a CloudNX Mumbai VPS at ₹3,500 a month.
- Jai Shri Balaji Store, the Delhi NCR kirana we built a three-app grocery system for, runs its Node.js backend on CloudNX.
- Running a hosting product changed our client defaults. Backups, SSL renewal, monitoring and log retention stopped being line items to argue about and became things we assume.
Questions we get about this build
Why build a hosting platform instead of reselling AWS or DigitalOcean?
Because the problems were billing and support, and reselling fixes neither. A reseller still passes on dollar pricing, still cannot issue a GST invoice against its own GSTIN, and still cannot promise a reply inside Indian business hours. Running our own infrastructure is what lets CloudNX bill in rupees and answer in IST.
What does the Mumbai region actually buy an Indian site?
Low tens of milliseconds to users in the metros instead of an overseas round trip, which usually shows up as a visible Core Web Vitals improvement against a US or EU region. It also keeps Indian user data in India, which makes DPDP Act 2023 compliance a simpler conversation. If most of your traffic is outside India, a global provider may still be the better answer, and we say so.
How does the INR and GST billing work in practice?
You are billed in rupees, so nothing is converted and no forex markup appears on the statement. Each paid invoice carries GST against our GSTIN, so your accountant treats it like any other Indian vendor bill and claims input credit normally. Paid plans start in the low hundreds of rupees a month.
Do you put all of your client work on CloudNX?
No, and that is deliberate. Managed WordPress goes to CloudNX for about 80 per cent of our client sites, with Cloudways covering the rest, and custom Laravel work goes to DigitalOcean Mumbai or a CloudNX VPS depending on the build. We pick per project rather than defaulting to our own product.
Can you migrate an existing site onto CloudNX?
Yes, and it is most of what a move looks like: copy the site to a staging server, check it renders and the integrations still work, then cut DNS over during a quiet window. What matters more is what the site was running on before, since a slow site on shared hosting is usually slow for reasons a faster server does not fix on its own.
What is the uptime figure for CloudNX?
We do not publish one, and we would rather say that than quote a number we have not measured and committed to. PlugEV has held 99.7 per cent in production since January 2025, but that is measured across the whole PlugEV system rather than the hosting layer, so it is not a CloudNX uptime figure and we will not present it as one.
Want something like this built?
We run this in production ourselves, so the estimate you get is based on having done it rather than having read about it.