Tally VPS Requirements: RAM, RDP Users, Windows & Backups

Tally VPS requirements are driven mainly by concurrent RDP users, Windows memory, TallyPrime data size and backup windows. VPSWala’s current Tally page recommends 4 vCPU / 8 GB RAM for roughly two to four concurrent users, 6 vCPU / 16 GB for five to ten users, and 12 vCPU / 32 GB for ten or more users or larger data.

Tally VPS sizing at a glance

Why memory usually matters first

Each active RDP session consumes Windows memory before TallyPrime and any supporting applications are counted. VPSWala’s page estimates roughly 1.5–2 GB per active session once TallyPrime is loaded. Treat that as a practical planning range, then monitor the actual environment.

Tally needs Windows

VPSWala’s guidance recommends Windows Server for production TallyPrime hosting. The VPS infrastructure price does not automatically include Windows Server or Remote Desktop Services licensing. TallyPrime licensing is also separate.

RDS licensing is a real cost

For multi-user Windows session-host deployments, appropriate Microsoft RDS licensing may be required. Include Windows/RDS and Tally licensing in the total monthly cost rather than comparing only the VPS sticker price.

Data storage and disk latency

Tally company data is business-critical. NVMe helps with application responsiveness, but backups and free-space monitoring matter just as much. Keep enough capacity for Windows updates, logs, company data and temporary backup files.

RDP latency

For Tally users, stable interactive latency matters more than raw bandwidth. Choose Mumbai, Noida or Jaipur by measuring from the offices that will use RDP all day. Packet loss and jitter can make a low-ping route feel worse than a slightly longer stable path.

Security checklist

• use separate Windows accounts;
• do not share administrator credentials;
• restrict RDP exposure where possible;
• patch Windows and TallyPrime;
• monitor failed logins;
• protect backup credentials separately.

Backups

VPSWala states that off-server backup retention is separately scoped. Keep a Tally-aware backup plus an independent server/data recovery copy. Test a restore instead of assuming a successful backup job is enough.

When to move from 8 GB to 16 GB

Upgrade when concurrent sessions create sustained memory pressure, not merely because the business added employees. Watch available RAM, paging, CPU and RDP experience during peak accounting periods.

Tally VPS checklist

1. Count concurrent users.
2. Measure current data size.
3. Choose Windows and licence model.
4. Budget RDS/Tally licences.
5. Test node latency from each office.
6. Define backup retention.
7. Monitor memory and disk after migration.

Bottom line

For Tally on VPS, 8 GB is a sensible two-to-four-user starting point, 16 GB fits a larger five-to-ten-user environment, and 32 GB is a better direction for more users or larger data. The final size should come from real session memory and data growth.

Next step: review VPSWala Tally on VPS and compare the VPS catalogue.

Frequently asked questions about Tally VPS

Can two users share one Windows login?

Do not design the environment that way. Use separate user accounts, correct Tally licensing and the appropriate Windows/RDS licence model so access is traceable and manageable.

Is 8 GB enough for five Tally users?

VPSWala’s current planning guidance puts 8 GB in the two-to-four-concurrent-user range. Five to ten users are a better fit for the 16 GB direction, then monitoring should confirm the result.

Does VPSWala include the Tally licence?

No. VPSWala’s page states that customers bring their own TallyPrime licence. Windows Server and RDS licensing are also separately quoted.

Where should Tally backups be stored?

Keep an independent off-server copy and test a real restore. Accounting data should not depend on one VM, one disk or one administrative account.

Sources

• VPSWala Tally on VPS
• VPSWala VPS catalogue