What Cloud Scalability Actually Means
Scalability means your infrastructure capacity can grow as your business grows — without hardware procurement delays, capital expenditure surprises, or data migration overhead. Cloud scalability is not just a marketing claim: it is a specific technical capability of virtualised infrastructure that fundamentally changes how businesses should plan their IT growth.
The Traditional Scaling Problem
A local server is purchased with a specific capacity — say, 16 GB RAM supporting 5–6 concurrent Tally users. When the business grows to 9 concurrent users, the options are: (1) purchase additional RAM and have an IT consultant install it (₹8,000–₹15,000 cost, 2–4 hours downtime, advance planning required), (2) purchase a new server (₹1 lakh+ capex, 2–3 days procurement, full migration), or (3) squeeze users onto the existing server at degraded performance.
None of these is ideal. All involve delays, costs, and disruptions that cloud scaling eliminates.
Cloud Scaling in Practice: M A Global Network
When you need to add users on M A Global Network's cloud hosting:
- Contact the support team with your new user count
- M A Global Network adjusts the VM resource allocation — more RAM, additional vCores
- The server is restarted with the new configuration — typically 10–15 minutes of maintenance
- Users reconnect and experience the new, higher-capacity server immediately
- The plan is updated to the new user count at ₹700/user/month + 18% GST from the date of upgrade
Total elapsed time from request to productive new users: under 2 hours in most cases, with 10–15 minutes of actual downtime during the restart.
Planning for Growth: Right-Size, Then Scale
The economically optimal approach to cloud infrastructure sizing:
- Start at your current correct size: Don't over-provision for hypothetical future growth — you pay for what you have
- Know your trigger points: Identify the concurrent user count at which you'll need to scale — typically when the current plan is consistently fully utilised
- Scale proactively, not in crisis: A scaling request submitted 2 days before bringing on new staff is smoother than an emergency request when the new staff member cannot log in on their first day
The rule of thumb: if your team is regularly at full concurrent capacity (all users logged in simultaneously for extended periods), it is time to consider scaling up.
Scaling vs Upgrading: When to Do Each
| Situation | Action | Time Required | Cost Change |
|---|---|---|---|
| Adding 1–3 new staff members | Vertical scale — increase RAM/vCores | 2 hours total (15 min downtime) | ₹700/user/month per added user + GST |
| Adding a new branch office | Add users + whitelist new branch IP | 2–4 hours total | ₹700/month per additional concurrent user + GST |
| Opening a new entity needing its own server | Provision a second server | 24–48 hours | New plan at ₹700/user/month for new entity + GST |
| Reducing team (seasonal downsizing) | Scale down at plan renewal | Contact support team | Reduced to new user count |
Frequently Asked Questions
For Tally and Busy hosting, practical scaling ceiling is around 20–25 concurrent users on a single Windows Server instance before considering multiple server options. Beyond this, separate server instances for different teams or entities become more manageable. For the vast majority of Indian SMEs (2–15 concurrent users), vertical scaling within a single server covers all realistic growth scenarios. M A Global Network can advise on multi-server architectures for larger organisations.
Scale From 3 Users to 15 Users — With No Hardware Changes
Add users in hours as your team grows. ₹700/user/month + 18% GST. 7-day risk-free guarantee.