Technology and AI

Cloud vs on-premise legal software

Cloud or on-premise legal software? Security responsibilities, UK GDPR duties, five-year costs, remote access and a decision path for solicitors.

Ava research teamPublished 6 min read

On this page
  1. The real question: who runs the servers
  2. How exposed UK businesses are
  3. Side-by-side comparison
  4. Security: what moves and what stays
  5. Data protection either way
  6. Cost: compare like with like
  7. Access, resilience and the size of your team
  8. Planning for outages in either model
  9. When on-premise still makes sense
  10. A decision path
  11. Example: a ten-person firm leaves its server
  12. Frequently asked questions
  13. References

Key takeaways

  • Cloud versus on-premise is mainly a choice about who patches, backs up and secures the servers; people and passwords stay your job either way.
  • Cyber attacks are common: 43% of UK businesses identified a breach or attack in a year, and phishing was by far the most common type.
  • UK GDPR processor terms apply to a cloud supplier and to any IT firm with remote access to your own server.
  • Compare five-year costs, including hardware refresh, support, downtime and exit, not just monthly licences.

The real question: who runs the servers

Legal software now comes in three broad forms. On-premise means the firm owns a server in its office and runs the software on it. Hosted means the same kind of software runs on a server in a data centre, managed by an IT provider. Cloud, in the sense most vendors use, means software as a service: the vendor runs one platform for many firms and you reach it through a browser or app.

The choice is less about technology than about responsibility. With cloud software, the vendor patches, backs up and monitors the platform. With on-premise software, your firm or your IT provider does all of that. Neither is automatically safer. What matters is whether the people responsible actually do the work, and whether you can check that they do.

How exposed UK businesses are

The government's Cyber Security Breaches Survey 2025 found that just over four in ten UK businesses (43%) identified a cyber security breach or attack in the previous 12 months, rising to 67% of medium businesses and 74% of large ones[1]. Phishing was the most prevalent and disruptive type, experienced by 85% of businesses that reported a breach or attack[1].

UK businesses identifying a cyber breach or attack in the last 12 monthsCyber Security Breaches Survey 2025
UK businesses identifying a cyber breach or attack in the last 12 monthsColumn chart. All businesses: 43%; Medium businesses: 67%; Large businesses: 74%.0%20%40%60%80%All businesses: 43%43%All businessesMedium businesses: 67%67%Medium businessesLarge businesses: 74%74%Large businessesUK businesses identifying a cyber breach or attack in the last 12 monthsColumn chart. All businesses: 43%; Medium businesses: 67%; Large businesses: 74%.0%20%40%60%80%All businesses: 43%43%AllbusinessesMedium businesses: 67%67%MediumbusinessesLarge businesses: 74%74%Largebusinesses

Source: Department for Science, Innovation and Technology (GOV.UK), 2025[1]

Show the data
ItemValue
All businesses43%
Medium businesses67%
Large businesses74%

Phishing targets people, not servers. A convincing email that captures a fee earner's password works just as well against an office server reached by remote desktop as against a cloud system. The same survey found only 40% of businesses had adopted two-factor authentication[1]. Whatever you choose, enforcing multi-factor sign-in for every user is the single control that most changes your risk.

Side-by-side comparison

General differences; individual products and contracts vary.
FactorCloud (software as a service)On-premise or hosted server
Platform security and patchingVendor's responsibility, applied to all customersYour firm or IT provider, on your schedule
Remote and home workingBuilt in through browser or appNeeds VPN or remote desktop, which must be secured
BackupsVendor's, plus your own export if you want oneYour responsibility, including testing restores
Resilience to office problemsWorks anywhere with internetOffice power or connectivity loss stops everyone
Upfront costLow; mostly subscriptionServer hardware, licences, installation
Ongoing costPer-user subscription, rising with headcountSupport contract, hardware refresh, electricity
CustomisationWithin the vendor's settings and add-onsOften deeper, at your cost and risk
Data location controlAs stated in the contractWhere your server physically is
ExitDepends on export termsData already on your hardware, but formats may be proprietary
Skills needed in the firmAdministration of users and settingsServer management, or a capable IT partner

Security: what moves and what stays

Moving to cloud software shifts platform security to the vendor, which is a good deal only if the vendor is competent. The National Cyber Security Centre's 14 cloud security principles, from data in transit protection to secure use of the service, are designed to help you choose a provider that meets your needs[2]. Ask for evidence against them rather than a general assurance.

Some responsibilities never move. Whatever the hosting model, the firm still decides:

  • Who has an account, at what level of access, and how quickly leavers are removed.
  • Whether multi-factor sign-in is enforced for everyone, including partners.
  • Which devices may connect, and whether they are encrypted and kept up to date.
  • How staff are trained to spot phishing and payment diversion attempts.
  • How data exported from the system, such as reports and downloads, is stored.

Data protection either way

Under UK GDPR, a controller may only use processors that provide sufficient guarantees of appropriate technical and organisational measures, under a contract with specified terms[3]. A cloud vendor is clearly a processor. So, often, is the IT company that maintains your office server with remote access to it. Firms that keep software on-premise sometimes forget that second relationship and have no written terms with their IT support at all.

Breach duties are the same in both models. A personal data breach must be notified to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it[4]. Check how your vendor or IT provider will tell you about an incident, how fast, and what logs they can give you to work out what was affected.

Cost: compare like with like

Cloud subscriptions look expensive next to software you have already paid for, but the comparison is rarely fair. A server-based setup carries costs that appear irregularly: replacement hardware every few years, operating system and database licences, a support contract, backup storage, and the cost of downtime when something fails at the wrong moment.

Example: a fictional eight-user firm compares five years of cloud subscriptions against a server route that needs one hardware replacement, a yearly support contract, backup licences and an allowance for two days of downtime. Once every line is included, the gap between the two is far smaller than the licence prices alone suggested, and the deciding factor becomes remote access.

  • Licences or subscriptions for every user, including support staff.
  • Hardware purchase and refresh, plus installation.
  • IT support hours for patching, backups and incidents.
  • Migration and training, which apply to both routes.
  • Exit costs at the end of the period.

Access, resilience and the size of your team

Most legal businesses are too small to employ IT staff: 78% of UK legal activities enterprises employed four people or fewer in 2026[5]. For them, running a server reliably means depending entirely on an outside provider's diligence. Cloud software also removes the office as a single point of failure, which matters for firms that offer home working or need to reach files from court or a client's home.

Planning for outages in either model

Every system goes down eventually. The difference is who fixes it and how you keep working in the meantime. With cloud software, a vendor outage affects every customer at once and you wait for the fix; with a server, a failed disk or a ransomware infection is yours alone to recover from. Write a one-page continuity plan for whichever route you choose, and test it once a year.

  • Ask the cloud vendor for its availability record over the last year and how it reports incidents to customers.
  • Keep a regularly refreshed export of key dates, client contact details and ledger balances outside the main system.
  • Agree who can authorise payments from client account by an alternative route during an outage, with call-back checks.
  • For a server, test a full restore from backup to separate hardware, not just a single file.
  • Make sure staff know how to tell clients and other parties about delays without using a compromised mailbox.

When on-premise still makes sense

  • You rely on a specialist system that has no cloud version and no plans for one.
  • You have capable in-house IT staff and a well-tested backup and recovery routine.
  • Your connectivity is unreliable and you cannot get a resilient second line.
  • A client contract requires data to be held on hardware you control, and the client will not accept a cloud alternative.

Even then, consider a hosted server in a professional data centre rather than a machine in the office cupboard. It keeps your software choice while improving power, cooling, physical security and backup.

A decision path

  1. Map your systems

    List each application, where it runs and who maintains it. Note which have cloud versions.

  2. Check obligations

    Review client contracts, insurer requirements and your processor agreements for any hosting conditions.

  3. Cost five years

    Build a like-for-like cost table for both routes, including downtime and exit.

  4. Test a vendor's evidence

    Ask for answers against the NCSC principles and a sample data export.

  5. Plan the move

    If cloud wins, move one system at a time, starting with the least integrated, and keep the old server read-only until the new system has run through a full accounts period.

Example: a ten-person firm leaves its server

Example (fictional): a ten-person firm runs case management and accounts on a seven-year-old office server. A power cut on a completion day stops all work for four hours. The partners compare routes, choose a cloud suite with built-in accounts and keep the old server, switched to read-only, for 12 months as an archive. Multi-factor sign-in is enforced from day one, and the firm signs a processor agreement with its IT provider for the first time.

Before choosing a product, use the practice management buyer's checklist and compare categories in case management systems for UK firms compared. If accounts are moving too, read legal accounting software and the SRA Accounts Rules.

Frequently asked questions

Is cloud legal software secure enough for client data?

It can be, if the vendor gives clear evidence of its security, offers enforced multi-factor sign-in and signs a proper processor agreement. The firm still controls users, devices and training.

Is on-premise software cheaper than cloud?

Not always. Once hardware refresh, support, backups, downtime and exit are included over five years, the difference is often smaller than licence prices suggest.

Do I need a processor agreement with my IT support company?

Usually yes, if they can access personal data on your systems, for example through remote access to a server. UK GDPR requires written processor terms.

Can we move to cloud software in stages?

Yes. Many firms move email and documents first, then accounts or case management, keeping the old server read-only as an archive for a period.

References

  1. Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber Security Breaches Survey 2025 (opens in a new tab) ↑

  2. National Cyber Security Centre (2025). The cloud security principles (opens in a new tab) ↑

  3. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 28: Processor (opens in a new tab) ↑

  4. legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑

  5. Office for National Statistics (2026). UK business: activity, size and location, 2026 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo