Zeway runs
India's EV charging network on CloudNx

The starting position

Like most India-first product teams, Zeway hit a fork in the road early: AWS Mumbai (great infrastructure, USD invoice, finance team headache), DigitalOcean (cheaper but no Indian-entity invoice, no GST input credit), or self-host on a VPS (cheaper still but no managed primitives, no team-collaboration tooling).

None of the three were quite right for an Indian-incorporated company running an Indian-customer product whose CFO was filing monthly accounts in INR.

Why CloudNx

They picked CloudNx for a specific bundle of three things that neither AWS Mumbai nor DigitalOcean offer at the same time:

• Indian-entity tax invoices. Every top-up generates a GST-compliant tax invoice with their GSTIN, IRN, and a downloadable PDF — their CA files it directly, no USD-to-INR conversion gymnastics required.
• Per-minute INR billing. Predictable. No exchange-rate surprises at month-end. No per-hour rounding tax on workloads that scale up and down for charging-session bursts.
• A real human to email. When their integration with the payment gateway hit an edge case, they emailed [email protected] and got the founder on a call the same afternoon. AWS Premium Support doesn't move that fast at any tier.

What they run on CloudNx

A multi-tier production stack on bare-metal Hetzner AX41 hardware via CloudNx's managed Proxmox layer:

• Web + API tier — Node.js services handling charging-session lifecycle, OCPP protocol bridging to physical stations, and user-facing app endpoints.
• Database tier — Postgres with WAL backups streamed offsite.
• Payment-processing API — Razorpay webhook handler with idempotent settlement flow.
• Admin console — internal tooling for the operations team.

All deployed via standard rsync + systemd workflows; no CloudNx-specific lock-in. If they ever wanted to leave, the migration to any other Linux host would take an afternoon.

What changed after the move

Without sharing internal numbers (Zeway will share more if asked directly), the picture is consistent with our other early customers' experience:

• Cloud bill in INR.No more month-end FX recalculation. Predictable line item on the P&L.
• GST input credit. Materially better post-tax effective rate on the cloud spend than the AWS-USD path.
• Faster support. Sub-4-hour reply from the founder, on business hours. Sub-hour during incidents.
• Same engineering velocity. Standard Linux VMs accept any deployment workflow they already used.

What we're building next for Zeway (and customers like them)

• Mumbai region (Q3 2026).When Zeway's charging-station fleet grows in southern + western metros, sub-50 ms RTT to Mumbai becomes the right floor.
• Managed Postgres (Q3 2026).So the database tier doesn't need anyone's sysadmin attention.
• Monitoring & logs as a service (Q3 2026). Today they self-host; we'll offer a managed Mimir + Loki tier with per-org isolation.

Want to do what Zeway did?

If you're an Indian-incorporated B2B SaaS or product company running on AWS Mumbai or DigitalOcean Bangalore today, and your finance team has complained more than once about USD invoices, the shape is the same.