"Tally on Cloud" is not a special cloud edition of Tally. It is your normal TallyPrime, with your own licence, installed on a Windows Server in a data centre, and everyone opens it over Remote Desktop (RDP). Before you pay for it, check five things: how licences work (Tally's and Windows'), round-trip latency from your offices, whether the CPU is shared or reserved, who can reach the RDP port, and how backups and exit work.
This post walks through each of those, with commands you can run yourself instead of taking a sales page's word for it.
What is actually running
Strip away the marketing and a hosted Tally setup is three layers:
- A Windows Server virtual machine (2019 or 2022 is typical) with CPU, RAM and disk sized for how many people use Tally at the same time.
- TallyPrime installed on it, with your company data folder on the server's disk.
-
One Windows user account per person, each logging in with an RDP client:
mstscon Windows, Microsoft's Remote Desktop app on macOS, iOS and Android.
Tally never runs on the user's laptop. Only screen updates, keystrokes and mouse clicks cross the network. That is why it works on ordinary broadband, and why head office, a branch and your CA can all work on the same books without emailing backups or merging data.
It also explains the main weakness: no internet, no Tally. Most offices that switch keep a mobile hotspot as a fallback.
Check 1: licences (there are two kinds)
Tally licence. Hosting providers generally don't sell Tally. You bring your own, and it activates on the server the same way it would on a desktop. Tally Solutions' rule is what matters here: Silver is single-user, and you need Gold if two or more people will have Tally open at once. Moving to the cloud doesn't change that, so a five-person team on a Silver licence has a licensing problem whoever hosts it.
Windows Remote Desktop licensing. People forget this one. Out of the box, Windows Server allows two simultaneous RDP sessions for administration. More concurrent users normally means Remote Desktop Services (RDS) client access licences. Ask the provider directly: "Are RDS CALs for N concurrent users included in the price?" Get the answer in writing.
Check 2: latency from where your people actually sit
Tally over RDP feels fine at a few tens of milliseconds and starts to drag once round trips get long or jittery, especially when people scroll through long reports. Test before you commit, from the office network, not from home.
From a Windows PC in the office (PowerShell):
# Is the RDP port reachable, and from which local interface?
Test-NetConnection tally.example.in -Port 3389
# TCP connect time to the RDP port, 20 samples
# (psping is from Microsoft Sysinternals; ICMP ping is often blocked on servers)
psping -n 20 tally.example.in:3389
Look at the spread as well as the average. A connection that reads 20 ms with occasional 200 ms spikes will feel worse than a steady 35 ms.
As a rough guide, a Mumbai data centre is usually closer for western and southern India, and a Delhi NCR one for the north. Pick the region with the lowest measured round trip from your main office, and test from your branches too. If a provider publishes typical latencies by city, treat them as a starting point and confirm with your own measurement.
Check 3: shared vCPU or reserved cores
Tally is not a heavy application, but several people running reports at month-end, plus Excel and a browser in each RDP session, add up.
Small plans are usually built on shared (fair-share) vCPUs: the host's physical CPU time is divided between tenants, with room to burst. That is fine for one to a handful of users. Larger plans may use dedicated cores, physical cores reserved for your server alone, which keeps response times steadier when the host is busy.
You can see what you have from inside the server:
# CPU model and core counts as Windows sees them
Get-CimInstance Win32_Processor |
Select-Object Name, NumberOfCores, NumberOfLogicalProcessors
# Overall CPU use and run-queue length, sampled every 2 s for a minute
Get-Counter '\Processor(_Total)\% Processor Time',
'\System\Processor Queue Length' -SampleInterval 2 -MaxSamples 30
If CPU use stays low but Tally still feels sluggish during closing, and the processor queue length stays above about two per core for long stretches, ask the provider about contention on the host or a move to reserved cores. Linux users will know steal time (st in top, or the eighth value on the cpu line of /proc/stat); Windows guests don't expose it as a standard counter, so you have to ask.
Check 4: who can reach port 3389
An RDP server open to the whole internet gets password-guessing attempts within hours. The fix is simple: only allow connections from your office IP addresses. A leaked password alone then isn't enough to get in.
On the server you can check what the firewall actually allows:
Get-NetFirewallRule -DisplayGroup "Remote Desktop" |
Where-Object Enabled -eq True |
Get-NetFirewallAddressFilter |
Select-Object RemoteAddress
If RemoteAddress says Any, the port is open to everyone. Ask for it to be locked to your offices' static IPs, or put RDP behind a VPN. Also:
- One account per person. Shared logins make it impossible to see who did what. Give your CA a separate account you can disable when the engagement ends.
-
See who is logged in.
quser(orquery user) on the server lists active and disconnected sessions. - Keep Tally's integration port private. If you use Tally's ODBC/XML server for integrations (port 9000 by default), it should never be reachable from the internet.
Check 5: printing, files and the "real desktop" question
Two RDP features do most of the work for day-to-day accounting:
- Printer redirection, so an invoice printed in Tally comes out on the printer beside you.
- Drive redirection, so you can import a bank statement from your laptop or export a report back to it.
Both are client-side settings in the .rdp file (or the "Local Resources" tab in mstsc):
redirectprinters:i:1
drivestoredirect:s:*
Then check whether you get a full Windows desktop (Excel, a PDF printer, a browser for the bank portal) or a locked-down window with only Tally. Both are valid choices, but they suit different teams.
Check 6: backups, restores and leaving
Ask these, and expect specific answers:
- How often are backups taken, and how many restore points are kept?
- Can I trigger an on-demand backup before year-end close?
- Can I restore a single day myself, or do I raise a ticket?
- Where is the data stored (which country, which city)?
- If I cancel, do I get my company data folder and a final backup, and how long is data kept before it is deleted?
The exit question matters most. Your books should never be held hostage by a hosting contract.
A one-screen checklist
| Check | What a good answer looks like |
|---|---|
| Tally licence | You bring your own; Gold if 2+ concurrent users |
| Windows RDS licensing | RDS CALs for your concurrent users confirmed in writing |
| Region | Lowest measured round trip from your main office; branches tested too |
| CPU | Shared vCPU for small teams; reserved cores as concurrency grows |
| Sizing | Based on concurrent users, not total staff |
| RDP exposure | Port 3389 limited to your office IPs or a VPN |
| Accounts | One Windows user per person; CA on a revocable account |
| Printing/files | Printer and drive redirection working before go-live |
| Backups | Nightly at minimum, plus on-demand; self-service restore |
| Exit | Company data folder and final backup handed over |
When you don't need it
If one person uses Tally on one reliable office PC that is backed up properly, hosting adds a monthly bill and an internet dependency for little gain. Tally on Cloud earns its keep when there are several users, more than one location, an outside CA, or an office PC you no longer trust with your only copy of the books.
Where we fit
Disclosure: this post comes from Bigdomainhost, an Indian hosting company launched in September 2026 (not connected with Big Domain Host LLC in the US). Our Tally on Cloud service follows the model above: a single-tenant Windows Server in Mumbai or Delhi NCR with your own Tally licence, sized by concurrent users, with shared vCPUs on the smaller plans and dedicated cores on the larger ones, RDP locked to your office IPs, printer and drive passthrough, and nightly backups. Windows Server and Remote Desktop come with the plan; if more than two people will be connected at once, ask us (as you would any provider) to confirm in writing how Remote Desktop licensing is handled for your user count. Before you decide, run our browser latency test from your office, or see the typical round trips by city. Whichever provider you choose, put the checklist above to them first.
Top comments (0)