Frequently asked questions

About 90 seconds — email + password, OTP verification, autopay setup, and you’re in the dashboard. KYC for compliance happens in parallel and doesn’t block you from launching your first VM.

No. We use Razorpay autopay over UPI / NetBanking / Debit-card. UPI is the most common — no card required. The first autopay charge funds your wallet so it isn’t a loss.

No free signup credit — you top up your wallet whenever you’re ready, via UPI / card / Razorpay. Billing is per-minute, so you only pay for what you actually run, and there’s no card-on-file surprise. Add just what you need to launch your first VM and top up more later.

Two regions: India (Mumbai) and EU West. Pick the region at launch; see Regions & latency. Indian end-users get ~25 ms from Mumbai; EU West is ~135 ms from India and suits EU-facing workloads.

Your account is prepaid by default: top up the wallet, instances debit hourly from the balance. Razorpay autopay can keep it filled automatically. The wallet balance is shown in the top-right of the portal at all times.

We send 3 emails over a 60-minute grace period, then stop (not delete) instances. Storage continues to bill while instances are stopped — top up to start them again. Data is preserved unless you explicitly delete a volume.

Yes, for trusted accounts with consistent monthly spend. Email billing@cloudnx.in with your last 3 months of usage and we’ll set a credit limit. Once approved, your account can run up to the credit limit and we invoice monthly with 7-day net terms.

Always — CloudNx Technologies is registered for GST in India. 18% IGST is added to invoices for inter-state customers and 9%+9% CGST+SGST intra-state. Your GSTIN, if entered on the billing page, appears on the invoice and is available for input-credit claim.

Compute meters every 60 seconds. A VM that runs 1 hour 23 minutes costs (price_monthly / 730) × (83 / 60) — fractional and fair. Storage is per-hour. Bandwidth is per-GB after the included quota.

No commitment, no minimum spend. Stop an instance at minute 2 and you’re billed for 2 minutes. Delete it and the bill stops entirely.

From the instance detail page → Resize. We stop the VM, change its Proxmox config, and restart. Takes ~60 seconds. RAM and CPU are flexible; disk grows but doesn’t shrink without a full backup/restore.

Yes — create a block volume and attach it to a running instance. The volume appears at /dev/vdb (or next available /dev/vd*). Mount, format, and use it like any other block device. Snapshot independently; detach to move to another instance.

From the instance detail page → Snapshots → Take snapshot. Snapshots are live (no downtime), stored on the host’s NVMe, and billed at ₹2/GB-month. Restore creates a new instance from the snapshot in ~30 seconds.

99.5% monthly uptime for compute instances, measured at the VM level, with service credits. Each region runs on a single dedicated host today, so a host failure means a coordinated restore — typically < 30 min. Measured availability is public at status.cloudnx.in; a multi-host 99.9% tier is on the roadmap.

Today: pick from the 9 first-party Linux distros (Ubuntu / Debian / Rocky / Alma / Fedora / openSUSE). Custom AMIs are planned for v1.1 — upload a qcow2 image, mark it as your own, launch instances from it.

Block (volumes) — when you need a filesystem mounted into one VM at a time. Postgres data, application uploads, logs. Latency: NVMe-fast. Object (S3) — when you need many readers, public URLs, or unlimited size. Photos, backups, static sites. Latency: ~5 ms internal.

Not yet at the block layer — volumes are not on encrypted pools today, and we would rather say so than let you assume otherwise. Secrets we hold on your behalf (access keys, TOTP seeds) are AES-256-GCM encrypted at the application layer. To protect data at rest right now, encrypt it inside your VM, or store it in a file encrypted by CloudNx KMS with your CMK.

Yes. Detach from VM A (data is preserved), attach to VM B, mount. Use this for blue/green deploys, debugging a stuck instance from a fresh VM, or moving data between availability tiers.

10 TB per volume, 50 TB per instance (5 volumes max). Talk to us if you need more — we can carve a custom Proxmox pool for genuinely large workloads.

Every instance gets a NAT’d public IP with port-forwarded SSH (different port per VM, shown on the instance detail page). For a dedicated, attachable public IPv4 use an Elastic IP — 1:1 NAT, full port range.

5 per account by default. Higher quotas via support — we just need a reason and your typical traffic profile.

Use Managed DNS: create a zone, delegate your registrar to ns1.cloudnx.in and ns2.cloudnx.in, manage records from the portal or CLI. Or point an existing zone (Route 53, Cloudflare) at the instance’s public IP / EIP — we don’t require you to use our DNS.

Per-instance today. Each VM has its own stateful iptables ruleset, applied by the host NAT reconciler within seconds of any change. Network-wide security groups land with VPC v1.1 (logical groupings already exist; physical isolation is the next phase).

India (Mumbai) and EU West, both on dedicated bare-metal in ISO 27001 datacentres. CloudNx Technologies (Indian sole proprietorship) is your sole contractual counter-party. Your data stays in the region you choose until you move it.

Yes for the customer-data plane. We capture audit logs on every state-changing API call, expose them to you at /portal/audit-logs, and honour DSAR (data-subject access requests) within 30 days. Personal data of your end-users is handled by your application; CloudNx is the data processor for your account-level metadata.

Yes — every list endpoint returns JSON, the CLI has --output json, and a one-click full account export (instances, volumes, buckets, invoices, audit logs) is in the portal’s Account → Export section. Object storage ships an S3-compatible API so any S3 tool works.

Pre-audit. The engineering preconditions (audit logs, KMS, MFA, RBAC) all shipped in 2026 H1. Formal SOC 2 Type II audit is gated on a second host per region (multi-AZ requirement).

Free tier: best-effort email response in 24 business hours. Paid (any spend in the last 30 days): < 4 business hours. Enterprise (postpaid customers): 1 business hour, with on-call escalation for production-down. We’re honest about not having 24×7 phone support yet.

Yes — status.cloudnx.in. Hosted on a separate provider (Upptime on GitHub Pages) so it stays up when CloudNx is down. Subscribe by email for incident notifications.

Open a support ticket with subject prefix [P1]. For postpaid customers, the dedicated phone number on your contract — that page wakes the on-call engineer.