Tally on Cloud in Bangalore: What It Really Costs and How It Works

The ₹2.3 lakh afternoon that started with a dropped cable

In August 2025, a 40-person textile exporter in Peenya called us because their Tally data for the previous month was gone. Not corrupted — gone. The accountant's desktop sat under a window, a rainwater leak had tracked down the wall and into the cabinet two days earlier, and the disk had been making a clicking noise nobody escalated. The last usable Tally backup was from 19 days before. Rebuilding purchases, sales and GST output from WhatsApp threads and courier receipts cost them ₹2.3 lakh in accountant overtime and a chartered accountant's re-filing fees, before you count the late-filing penalty under Section 47 of the CGST Act.

That is the real case for Tally on cloud in Bangalore. Not "digital transformation". Not productivity. It is that your bookkeeping data currently lives on one spinning disk in one room, and Bangalore's power and cabling conditions are not kind to that arrangement.

This piece is for the person evaluating this purchase right now: the IT manager at a 150-person distributor, the ops head at a manufacturer, the partner at a CA firm. I'll cover what hosting actually means, what it costs in 2026, how multi-user licensing really works, what to expect from latency over a Bangalore broadband line, and where our own approach is not the right answer.

What "Tally on cloud" actually means

There is no cloud version of Tally. TallyPrime is a Windows desktop application, and Tally Solutions has not shipped a hosted SaaS product. What the market calls "Tally on cloud" is a remote desktop — RDS, AVD, Citrix, or a hosted virtual machine — running TallyPrime on a server in a data centre, with your users connecting to it over the internet.

That distinction matters because everything you care about — licence cost, latency, backup, GST filing — flows from how that remote desktop is built and where it sits.

The four models you will be quoted

1. Hosted RDS in an Indian data centre. A Windows Server with the Remote Desktop Services role, or a shared multi-tenant RDS environment from a provider. Your Tally data sits on that server's disk. Users connect with Remote Desktop or a web gateway. This is what most Indian providers, including us, sell.

2. Public cloud VM you control. An Azure D4s v5 or AWS m5.xlarge in the Mumbai region, Windows Server licence, RDS or Azure Virtual Desktop, Tally installed, data on a separate Azure Disk. You manage it or someone does on your behalf. More moving parts, more control.

3. VPN plus Tally on your own server. Tally stays on a server in your Bangalore office, and remote users connect over a VPN. Cheap, and it keeps the data physically with you. It inherits every power and connectivity problem your office has. We have deployed this and it works — until a BESCOM outage takes the server down at 6 pm on 30th September.

4. Tally on a hosted desktop (DaaS) from an international provider. Generally a bad idea for Indian companies. The Tally data ends up in Singapore or Frankfurt, which starts to raise questions about cross-border data transfer under the DPDP Act and adds 60–120 ms of latency to every screen refresh.

A comparison you can actually use

Notice that the cheapest line item — VPN to your own server — is the one that carries the most hidden operational cost. The server still needs a UPS, an AMC, a disk replacement cycle, and someone to check that the backup ran last night.

Latency: the honest numbers

Latency is where most providers fudge. Here is what we actually measure.

A TallyPrime screen render on a hosted RDS instance in an Indian data centre, from a Bangalore office on a 100 Mbps leased line, typically completes in 90–180 ms of perceived delay per screen. From a home broadband connection with 40 ms RTT plus jitter, the same screen takes 200–400 ms. On a 4G hotspot during the evening, expect 400–700 ms and occasional disconnections.

What that feels like in practice: entry-level data entry, invoice creation and voucher posting are fine on any of these. Banking reconciliation scrolling through a 3,000-line ledger is tolerable on 100 ms and irritating on 400 ms. Generating a 2,000-page consolidated report in one go is where users complain.

The specific choices that move the number

• RDP over TCP vs UDP. Windows Server's Remote Desktop Protocol defaults to TCP, which retransmits on loss. Enabling UDP transport (available in Windows Server 2019 and later, and in Windows 11 clients) cuts perceived latency by roughly 30–40% on lossy connections. Ask whether your provider enables it.
• Colour depth. Setting colour depth to 16-bit instead of 32-bit in the RDP client reduces bandwidth per frame and makes screen updates noticeably snappier on a 4G link. Most users never notice the difference.
• Printer redirection. Disable it if you don't need it. Redirected printers are the single largest RDP latency sink we encounter, because the driver handshake happens on every session.
• Regional proximity. Mumbai-hosted will beat Singapore-hosted by 30–60 ms for a Bangalore user. Hosting in Chennai or Bengaluru data centres is 15–25 ms better than Mumbai. If your users are mostly in Karnataka and Tamil Nadu, insist on a south-India or Mumbai region.
• ISP last-mile quality. Airtel and Jio business circuits behave differently under load. We have seen Jio fibre deliver 6 ms RTT to a Mumbai endpoint at 3 pm and 34 ms at 8 pm, while an Airtel leased line held steady at 22 ms. For Tally, the leased line wins.

What nobody should promise you: local-feeling latency. If you are used to Tally on your own desktop with an SSD, RDS will feel slightly slower every single day. Four out of five users stop noticing within a fortnight. The fifth user — usually the partner who reviews vouchers — will complain for a month. Plan for it.

Multi-user licensing: the part that surprises the FD

TallyPrime licensing is per-user and per-company-in-a-data-directory, and the licence is not tied to a machine or a server. That's good news for cloud hosting — you can move a licence to and from your hosted environment — but it is also where finance teams get their arithmetic wrong.

The 2026 TallyPrime licence price bands

Tally changed its commercial model in 2022 to an annual subscription and has adjusted pricing since. As of early 2026, indicative figures for the Indian market:

Two things to internalise. First, Gold is unlimited users on the company data you have licensed, which makes it almost always cheaper than Silver once you have more than three people touching the books. A 10-user deployment on Silver is not possible without breaking the licence; on Gold it is trivial. Second, the Windows Server user CALs are a separate cost that many small providers bundle invisibly into their monthly fee. Ask whether they do, and how many CALs sit behind your fee.

For a 10-user hosted Tally deployment with Gold licensing, the realistic 2026 all-in monthly is ₹12,000–₹18,000, of which ₹5,600–₹5,700 is the amortised Tally licence and the rest is the hosted server, CALs, backup and monitoring. If you are quoted ₹6,000 all-in for the same thing, the provider is skipping either the CALs or the backup. Neither omission is worth the savings.

How many "users" do you actually have?

Audit this before you buy. In our experience, a firm with "10 Tally users" usually has 6 regular users, 2 occasional users (the partner who approves once a week and the auditor who visits monthly), and 2 people who have a licence but log in twice a year. Hosting makes this easier to manage, because you can provision an RDS user for the occasional partner and not provision one for the twice-a-year contact. Talk to your provider before you sign up for a fixed concurrent-user count — many Indian hosted-Tally providers still price on concurrent RDS sessions, which is a different number from Tally licences.

GST filing on hosted Tally: what has to work

If you are doing GST compliance, your hosted Tally environment has to talk to the GSTN. There are three practical dependencies:

1. GST Suvidha Provider (GSP) integration. TallyPrime connects to a GSP, either the built-in one or a third-party such as ClearTax, Vayana or IRIS. The connection uses the server's outbound HTTPS, which means your hosted provider must allow outbound 443 to the GSP endpoints, and the e-invoice and e-way bill portals. Most do; a few lock down outbound traffic aggressively. Test it in the first week.
2. Digital Signature Certificate access. DSC tokens are USB devices. In a hosted environment, the token must be plugged into a local machine and passed through RDP USB redirection, or held on a network USB hub. USB redirection works, but every RDS session that hops between users needs the token physically present for sign-off. For the 11th-hour GSTR-1 filing at 11:40 pm on the 10th, this is exactly where things go wrong. Test your DSC path before the filing deadline, not during it.
3. Return filing window. GSTN performance is worst between 8 pm and 11:59 pm on the 10th, 15th and 20th of each month. Your RDS session will not be the bottleneck, but your internet link might be. Keep a 4G failover router on the accountant's desk.

A GST deadline failure worth knowing about

In October 2025, a 70-person FMCG distributor in Bommanahalli hosted Tally with a provider that had a single internet link in its Mumbai data centre. On the evening of the 10th, the provider's uplink to the GSTN had an unexplained 45-minute outage, and the accountant's GSTR-1 filing missed the deadline by 90 minutes. The penalty under Section 47 was ₹200 per day, so small — but the disrupted e-invoice series cascaded into three days of customer reconciliation chaos. The fix was multi-homed connectivity and a contractual uptime commitment with a specified remedy. Our standard for hosted Tally environments now is two upstream providers with BGP, and any provider that cannot tell you their upstream redundancy should not be on your shortlist.

Data security and backup

Tally data is a flat file (an .xml or compacted data directory), which makes it easy to access and easy to destroy. In a single-office setup, any accountant with the data path can delete a company or run a year-end split wrong. In a hosted setup, that risk goes up, not down, because multiple people have RDS access.

The controls that actually matter

• Per-user data folders. Each RDS user gets their own Windows profile and a network share mapped to the Tally data with folder-level permissions. This is basic and routinely skipped.
• Daily automated backup to object storage. Not the RDS disk, not a second disk in the same VM. A separate account, ideally a different provider. AWS S3 or Azure Blob in the Mumbai region, with versioning on. Backup runs at 22:00 IST nightly, retention 30 days. Cost is ₹800–₹2,500 per month for typical Tally data volumes (a 5 GB data directory with 30 versions stays small).
• Monthly restore test. Not a backup log. An actual restore to a staging VM and a login to TallyPrime. We have seen too many providers whose "backup" was a Windows Server Backup job that had been silently failing for 90 days because the destination volume was full.
• Tally audit trail. TallyPrime has a built-in audit trail feature (enabled per company) that records every alteration with user, timestamp and old/new value. Turn it on if you have any external or internal audit requirement. It is free and it catches more problems than any bolt-on control.
• MFA on the RDP gateway. Windows RD Gateway with NPS and RADIUS to an MFA provider, or an Azure AD Application Proxy in front of the RDS. Without MFA, a hosted Tally server is a brute-force target — we see 40,000–120,000 credential attempts per day on exposed RDP endpoints in Indian data centres.

The specific failure story

A CA firm with 60 clients on its hosted Tally engagement called us in March 2026. Their provider had changed backup software six months earlier and no longer had restorable backups of the previous quarter. One client's FY 2024-25 data had been split into two companies by a junior staffer, incorrectly, and merged back — and the data had a reconciliation gap. Restoring the pre-split data would have required going back to a previous version, which no longer existed. The firm re-created two months of the client's ledgers manually at a cost of roughly ₹1.8 lakh in staff time and, more painfully, a client relationship. Their old provider's response was that the backup was "working as designed". It was — the design just didn't include retention or restore testing.

Where Tally on cloud is the wrong answer

Our service page is here — software services — and it lists what we do. But we have talked three Bangalore customers out of hosting this year. Here is when the fit is wrong:

• You have one user and one company. A single-user TallyPrime Silver on the accountant's desktop, backed up nightly to a synced OneDrive or S3 bucket, costs ₹22,500 per year plus ₹3,000 in storage at most. Hosting doubles the annual cost for no benefit.
• Your internet is unreliable and you have no second line. If you get 4-hour outages monthly and cannot get a second ISP in, hosting will make you angrier than your current setup does. Fix the connectivity first. Visit the service page and ask about leased line and failover procurement, not hosted Tally.
• Your team resists remote desktop. Some firms have users who will not adapt. If your partner would rather work from a printed ledger than a remote session, you will end up running both — and then the data diverges. In that case, keep Tally local on a server with proper backup, and improve the backup.
• You need on-premises data residency for an audit reason. A few regulated subsidiaries and MNC-controlled entities require books to stay on-premises. Hosting contradicts that. There are paths (Azure Dedicated Host, or a private cloud with a clear data-location contract), but they cost 3–4× hosted RDS.

If none of those apply, hosting is likely the right call.

What we actually deploy (and what it costs in 2026)

For a typical 10-user Bangalore customer, our reference architecture looks like this:

• Windows Server 2022 with RDS, hosted in a Mumbai tier-III+ data centre
• 8 vCPU, 32 GB RAM, 500 GB SSD storage for the OS and Tally data, plus separate storage for backups
• TallyPrime Gold licensing handled directly by you or via us, with the licence uploaded to the server
• Clean RDP configuration: UDP enabled, 16-bit colour, printer redirection only where needed, RD Gateway with MFA
• Nightly backup to AWS S3 Mumbai with 30-day versioned retention
• Monthly restore test documented and shared with you
• 24×7 monitoring for the VM, RDS session health, and GST portal reachability

Pricing bands for 2026, all-in and excluding GST:

Add 18% GST for Indian customers. Add ₹4,500–₹7,500 per user one-time for Windows Server CALs if not bundled. Add ₹15,000–₹40,000 one-time for migration, user setup and DSC configuration. If you are migrating mid-year and your current Tally licence is still valid, we will usually carry it across — most hosted providers can, but ask before signing.

Migration: what the first fortnight looks like

A clean migration from desktop Tally to hosted RDS takes two to three weeks end-to-end. The steps that catch people out:

1. Licence transfer. Tally licences are user accounts tied to Tally's licensing portal. Moving a licence from one machine to another is easy; moving it from one organisation to a reseller-managed licence can require coordination. Keep your original licence email.
2. Data cleanup before migration. This is the right moment to close out dormant companies, split data directories sensibly, and remove test companies. Moving 40 messy companies is the same effort as moving 10 clean ones but causes five times the confusion.
3. User provisioning and MFA enrolment. Allow 30 minutes per user. Do not underestimate the 55-year-old partner whose phone has to be re-enrolled.
4. DSC and e-invoice testing. File one dummy invoice, one dummy e-way bill and one GST return (non-filing test mode) before going live.
5. Parallel running for one filing cycle. Keep the old desktop Tally accessible for the first GST cycle after go-live, then decommission.

We schedule this over two weeks and are on call for the first week. If you want to talk through whether your situation fits, our contact page is the right place to start.

ISP, power and the Bangalore operational reality

A few things that only show up when you actually operate in this city:

• ISP lead times. Airtel and Jio business fibre in most Bangalore industrial and office areas takes 7–15 working days for a new connection. Leased lines (Tata, Sify, ACT Enterprise) take 21–45 working days and often require a site survey. If you are migrating to hosted Tally and rely on a home broadband connection for the accounts team, order your business line first, not last.
• Power. Even hosted Tally does not fully remove power dependency — your users need working desktops and internet. A 1 kVA online UPS per desk cluster, or a 3 kVA for the accounts room, gives 30–60 minutes of buffer for the RDS session to survive short BESCOM dips. Label the UPS so the accountant knows which socket to plug into.
• Monsoon cabling. Every July–September, we get calls about water-damaged OFC terminations and RDP drops. If your building has outdoor cable runs, get them inspected in June, not in August. This is the single most common cause of "Tally is slow" complaints during the monsoon.
• Weekly power-cut calendar. Some Bangalore industrial areas still have scheduled outages. Your hosted RDS survives, but the user does not. If your accounts team cannot work through the outage, that is a business decision, not a technical one.

FAQ

Can I run TallyPrime on cloud without a Windows server? No, not practically. TallyPrime is a Windows desktop application. The hosted environment is always a Windows Server (or Windows 11 VM) with some form of remote access. There is no Linux or macOS hosted Tally.

Is Tally on cloud legal and compliant with GST rules? Yes. The GST law does not specify where records must be stored, only that records be maintained and produced on demand. A hosted Tally environment in an Indian data centre is standard practice and is accepted by GST auditors. Cross-border hosting raises questions you should discuss with your CA before committing.

How much does Tally on cloud cost in Bangalore in 2026? For 10 users with TallyPrime Gold, plan for ₹14,000–₹18,500 per month excluding GST, all-in. A single-user, single-company deployment with Silver licensing and shared hosting can come down to ₹5,000–₹7,000 per month.

Will Tally be slow on cloud? It will feel 10–30% slower than a local SSD desktop. Screen renders take 90–180 ms from a Bangalore office on a business broadband line. Voucher entry is fine; large report generation is the visible cost. Most users adapt within two weeks.

What happens to my data if the provider shuts down? Contract for it. Insist on a monthly full data export in standard Tally format, a documented exit process, and no lock-in beyond a 30-day notice. If a provider will not commit to this in writing, do not sign.

Can I access hosted Tally from my CA's office or from home? Yes, from any internet connection. CA firms typically want read-only or audit access, which can be provisioned with restricted RDS profiles and Tally's own user rights. Home access works but needs MFA, since a home connection is not on your office IP.

Do I need a VPN to use Tally on cloud? Not usually. The RDS gateway handles authentication and encryption, and a full VPN on top adds latency for no security benefit. VPN is more relevant in the alternative model where Tally stays on your office server.

One concrete step for this week

Before you call anyone, do three things. Open your current Tally data folder and note the size and the last-modified time of every company. Check where your last three nightly backups actually are, and try to restore one. Then ask your current accountant or IT person how many concurrent users actually log in on the 10th of a month, not on a quiet Tuesday.

When you have those three numbers, the hosting decision gets much easier. If you want to walk through them with someone who has migrated more than 300 Indian companies to hosted Tally, get in touch with our team — bring the numbers and we will tell you honestly whether hosting is the right move, or whether you should fix your backup and keep Tally where it is.