Cloud services
& infrastructure.
Somewhere reliable for your website or app to run. One-time setup from ₹15,000, managed plans from ₹4,000 a month, with the provider’s bill shown separately from ours.
AWS, GCP, Azure and DigitalOcean usage charges are billed by those providers and are never bundled invisibly into the Netqorix fee.
01 / Who this is for
For businesses whose website or app needs somewhere reliable to live.
Every website and application runs on a computer somewhere. "The cloud" simply means renting that computer from a provider such as Amazon Web Services, Google Cloud, Microsoft Azure or DigitalOcean, instead of buying and running a server yourself.
This page is for businesses that need that set up properly the first time, or need someone to look after it afterwards. If you already have a working website on basic shared hosting and it is coping fine, you may not need this page at all.
02 / Cloud explained in everyday terms
Renting a shop, not buying the building.
Buying a server is like buying a building
You pay a large amount up front, you own it, and you are responsible for the electricity, the locks, the repairs and the fact that it is the wrong size in two years.
Cloud is like renting a shop unit
You pay monthly for the space you use. If business grows, you take a bigger unit. If it shrinks, you take a smaller one. You are not stuck with hardware you no longer need.
You still pay the landlord and the shopfitter separately
The cloud provider is the landlord and bills you for usage. Netqorix is the shopfitter and the manager, and bills for the work of designing, building and running the setup. These are two different bills, and your quote shows both.
The meter runs on usage, not on a fixed plan
Cloud providers bill for what you actually consume: server time, storage, data transfer, database hours. A quiet month costs less than a busy one. This is why a cloud bill is an estimate until real traffic exists.
03 / Problems this can address
When basic hosting stops being enough.
- The site slows down or falls over when traffic rises. A campaign, a festival season or press coverage brings more visitors than the current hosting can handle.
- There are no real backups. Nobody can say when the last backup was taken or whether it can actually be restored.
- Deployment is manual and risky. Files are dragged onto a server by hand, and every release is a gamble.
- Nobody knows who has access. Passwords are shared, there are no separate accounts, and ex-staff or ex-vendors may still have keys.
- The bill is unpredictable. Cloud charges arrive with no explanation of what drove them.
- There is no test environment. Every change is made directly on the live site.
04 / How it works
What setup and management actually involve.
Setup is a one-time piece of engineering
Choosing the provider, sizing the servers, configuring the network and firewall rules, setting up access control so each person has their own account with only the permissions they need, installing SSL, connecting the database, and building a deployment pipeline so releases are repeatable instead of manual.
Management is an ongoing arrangement
Watching that everything is up, taking and testing backups, applying security patches, adjusting capacity when traffic changes, renewing certificates, and reporting on what the infrastructure is doing and costing.
Provider choice is decided by your workload
Netqorix works with AWS, Google Cloud, Azure and DigitalOcean. The right one depends on your application, expected traffic, who needs to operate it and your budget — not on a blanket preference. A small business website and a high-traffic application deserve different answers.
05 / Plans and rates
One-time setup, then a managed plan if you want one.
Setup is billed once per project. Managed plans are billed every month. The tier depends on how much infrastructure there is to look after and how quickly incidents must be handled, not on the size of your company.
| Tier | Scope and management | Rate band |
|---|---|---|
| Cloud Setup (one-time) | Cloud architecture configuration, VPCs, IAM security rules and CI/CD pipeline deployment on AWS, GCP, Azure or DigitalOcean. | ₹15,000 – ₹60,000 |
| Managed — Starter | Small application or static and serverless stack. Health monitoring, backups, SSL setup and routine security patching. | ₹4,000 / mo |
| Managed — Business | Multi-service backend, autoscaling rules, managed database cluster tuning, automated alerts and a monthly infrastructure report. | ₹10,000 / mo |
| Managed — Scale | High-traffic enterprise application, load balancing, DevOps engineering and 24x7 incident monitoring with priority SLA. | ₹25,000+ / mo |
| Provider Cost Markup | Actual AWS, GCP, Azure or DigitalOcean usage, billed at direct cost plus a management margin. | cost + 15–20% |
Managed plans are optional. If you would rather hold the cloud account yourself and pay the provider directly, Netqorix can set it up, hand over the access and stop there.
06 / How cloud billing works
Two bills, and which one is which.
Bill one: the cloud provider
AWS, Google Cloud, Azure or DigitalOcean charge for what your application consumes — server time, storage, data transfer, managed database hours, and any extra services. This is metered and varies month to month with your actual usage. Netqorix does not set these prices and cannot fix them in advance.
Bill two: Netqorix
The one-time setup fee, and the monthly managed plan fee if you take one. These are Netqorix rates and are fixed in your quote.
When Netqorix holds the account for you
If the cloud account sits under Netqorix management, provider usage is passed on at direct cost plus a 15–20% management margin. You see the underlying provider cost and the margin as separate lines.
When you hold the account yourself
The provider bills your card or your business directly, and there is no markup because Netqorix is not paying that bill. You pay only the setup and managed plan fees. Many businesses prefer this because it keeps ownership of the account unambiguous.
07 / What you get and what is excluded
Deliverables and exclusions, stated up front.
Included in the agreed scope
- A configured, working production environment for your application.
- Network, firewall and access-control configuration.
- SSL installation and, with a managed plan, renewal.
- A deployment pipeline so releases are repeatable.
- Backups and, with a managed plan, monitoring and alerting.
- Documented handover of accounts and access.
- A monthly infrastructure report on the Business and Scale plans.
Not included unless quoted separately
- The cloud provider’s own usage charges.
- Domain registration, renewal and business email subscriptions.
- Paid third-party licences, APIs and monitoring tools.
- Application development and bug fixing. See app development and maintenance.
- Formal compliance certification and audits.
- A guaranteed uptime figure. Monitoring detects failures quickly; it does not remove the provider’s own risk of outage.
- Recovering data that was never backed up before the engagement began.
08 / What this looks like in practice
Two situations, described as hypotheticals.
These are illustrative scenarios written to explain how the tiers differ. They are not Netqorix client projects.
A five-page business website with a contact form. Low traffic, no logins, nothing to process. This can run on a small static or serverless setup. A one-time setup at the lower end of the band plus a Starter managed plan at ₹4,000 / mo is usually more than enough, and the provider bill itself will be small.
A booking application with accounts, payments and busy weekends. Traffic spikes, a database that must not lose data, and downtime that costs real bookings. This needs autoscaling, a managed database, alerting and a tested restore procedure — a Business managed plan, with the provider bill rising and falling with booking volume.
09 / The delivery process
How a cloud engagement runs.
Share what you are running
Tell us what the application is, roughly how much traffic it handles, where it runs now, and whether anything has already failed.
Review and recommendation
Sanjeev reviews the workload and recommends a provider and a setup sized to it, with the reason stated rather than assumed.
Fixed quote
You receive the one-time setup fee, the recommended managed plan if any, an estimate of provider usage with its assumptions stated, and who will hold the account.
Build and migrate
The environment is built, the application is deployed to it, backups and monitoring are switched on, and the setup is tested before anything is cut over.
Handover and ongoing management
Account access and documentation are handed over. If you have taken a managed plan, monitoring, patching and reporting continue from there.
Frequently asked questions
Cloud and infrastructure questions.
What does 'cloud' actually mean for my business?
It means renting computing power from a provider such as AWS, Google Cloud, Azure or DigitalOcean instead of buying and running your own server. You pay for what you use, you can grow or shrink the setup as needed, and the provider looks after the physical hardware.
Do I have to use cloud hosting?
No. A small, low-traffic business website often runs perfectly well on ordinary shared hosting at a much lower cost. Cloud makes sense when you need to handle variable traffic, run an application with a database, keep separate test and live environments, or control who has access to what.
Is the cloud provider's bill included in your monthly fee?
No. The managed plan fee is what Netqorix charges for the work of running your infrastructure. AWS, GCP, Azure or DigitalOcean bill separately for the resources you consume. If the account is held under Netqorix management, provider usage is passed on at direct cost plus a 15–20% management margin, shown as separate lines.
Can I hold the cloud account in my own name?
Yes, and many businesses should. You pay the provider directly, there is no management margin because Netqorix is not paying that bill, and ownership of the account is unambiguous. Netqorix sets it up, hands over the access and can still manage it under a monthly plan.
How much will my cloud bill be?
It depends on real usage, which nobody can know precisely before launch. Your quote includes an estimate with the assumptions stated — expected traffic, storage and database size. Actual charges will move with actual usage, and the first two or three months are the honest test.
Which provider do you recommend?
It depends on the application, expected workload, who needs to operate it and your budget. Netqorix works with AWS, Google Cloud, Azure and DigitalOcean and gives a reason for the recommendation rather than defaulting to one provider for every client.
Can you guarantee 100% uptime?
No. Cloud providers themselves publish availability targets rather than guarantees. Monitoring means a failure is detected and acted on quickly, and tested backups mean it can be recovered. Netqorix does not publish an uptime guarantee it does not control.
What happens if I want to leave?
The account and its access are yours. Documentation and credentials are handed over, and you can move to another provider or manage it in-house. There is no lock-in mechanism designed to make leaving difficult.
10 / Related services
What usually goes with a cloud engagement.
Your next step
Get your cloud setup priced properly.
Send what you are running, roughly how much traffic it gets and where it is hosted today. You will get a provider recommendation, a fixed setup fee and a provider-cost estimate with its assumptions stated.
Compare every Netqorix rate on the pricing page.