What Cloud Scalability Means in Practice
Scalability is one of the most cited benefits of cloud — but what it means specifically for Tally/Busy hosting and Windows application infrastructure is worth explaining concretely. Cloud scalability for accounting software means: when your business grows and more users need simultaneous access, the server's resources (RAM, CPU) are increased without replacing hardware, without migrating data, and without extended downtime.
Scaling Up: Adding Users to Your Plan
When your team grows from 5 to 8 concurrent users and the server needs more RAM and CPU to support the additional sessions: M A Global Network resizes the server — a managed operation typically completing within a few hours. The process:
- Contact M A Global Network support with your new user count
- Maintenance window scheduled (typically late evening or overnight)
- Server resources increased — more RAM allocated, CPU cores adjusted
- Server restarts with new specification
- Users reconnect to the same environment — same applications, same data, same settings
No data migration. No reinstalling applications. No reconfiguring user accounts. The server is the same — just with more resources. Your team notices nothing except the upgrade to a larger plan on the next invoice.
Scaling Storage
As Tally company databases grow over years of transactions, or as more client companies are added to a CA firm's server, storage can be expanded. Storage expansion on M A Global Network servers typically requires no server restart — the additional storage is provisioned and the existing volume expanded, or a new volume mounted. Contact the team when storage is running low for a smooth expansion with no disruption.
Scaling Down
Scaling down (reducing the plan when usage drops) is handled at yearly plan renewal. If your team contracts or concurrent usage patterns change, the plan is adjusted at the start of the next yearly contract. Mid-year scale-ups are handled immediately; mid-year scale-downs are addressed at renewal.
Contrast With Local Server Scaling
| Scaling Scenario | Cloud Server | Local Server |
|---|---|---|
| Adding 3 new concurrent users | Hours — resource resize + account creation | Potentially weeks — hardware procurement, delivery, installation, configuration |
| Temporary peak (filing season) | Temporary resize — revert after peak period | Must size for peak permanently or accept degraded performance |
| Adding a branch location | Add users to plan + whitelist new IP | New server or VPN infrastructure for the branch |
| Expanding storage | Volume expansion — typically no downtime | Hardware procurement + possible RAID reconfiguration |
Planning Ahead: The Right Starting Point
Start at the correct plan size for today's concurrent user count — with one user of headroom for expected near-term growth. Cloud's scaling flexibility means there is no cost penalty for starting conservatively and adding resources as needed. Over-provisioning from day one costs money without providing benefit.
If you are expecting to add 2 users in the next 3–6 months: start at the plan that includes today's users plus 1–2 for headroom. When the additional users join, the plan is expanded without any disruption.
Frequently Asked Questions
Yes, at the next yearly contract renewal. The plan is adjusted to reflect the new concurrent user count for the following year. Mid-year, the plan continues at the contracted level. Scale-ups are processed immediately at any time during the contract year; scale-downs are processed at renewal.
No. Vertical scaling changes only the resource allocation — RAM and CPU. It does not touch the storage layer where your Tally/Busy data lives. All company files, user settings, TDL configurations, and application data are completely unchanged by the resize operation. The brief restart required is equivalent to the server being rebooted — data integrity is fully maintained.
Scale When Your Business Grows — Not Before
Start right-sized. Expand in hours. No hardware. No data migration. ₹700/user/month + 18% GST. Yearly plan.