Hosting NetSuite: a cloud-only ERP and what it means for a UK business

If you are searching for NetSuite cloud because you want to compare hosting models, the first thing to know is that the comparison does not exist in the form you may expect. Oracle NetSuite is a software-as-a-service ERP. The publisher runs the platform, you reach it through a browser, and there is no version to install on your own servers. This page explains what that means in practice for a UK business: where responsibilities sit, how upgrades and customisation behave, what to check on data protection, and how to decide whether the model suits you.

How NetSuite hosting works

In a traditional on-premise ERP, you buy a licence, a supplier installs it on servers you own or rent, and your IT team or a hosting provider maintains the operating system, the database, the backups and the patches. Several ERPs also offer a hosted variant run by a partner, which sits between the two.

NetSuite does not follow that pattern. It is a single cloud service operated by Oracle for all its customers. When people talk about NetSuite hosting, they mean the way Oracle runs that service and the commitments it makes about it, not a deployment you configure.

Three consequences follow straight away:

• No server estate to run. You do not size servers, patch databases or renew hardware.
• No choice of version to freeze. You use the version the publisher currently provides.
• A subscription rather than a licence. What you pay is an ongoing service fee, covered on the NetSuite pricing page.

The hosting options compared

Because buyers often arrive with the three classic models in mind, the table below shows how NetSuite sits against them. It describes the model, not a ranking.

If a quote or a presentation speaks of NetSuite on premise or a privately hosted NetSuite, ask the supplier to explain exactly what is being offered. In most cases the real answer is either a different product or an integration layer that runs next to NetSuite, such as a connector or a reporting tool hosted separately. Those components are covered in NetSuite integrations.

What cloud-only changes for your business

Upgrades and releases

Oracle updates the platform for all customers on a published release schedule. You do not plan an upgrade project, book a weekend for downtime or buy an upgrade licence. The trade-off is that you do not decide the date either.

In practice, the work moves from the upgrade itself to testing around it. Before each release reaches production, your integrator or your in-house administrator should check customisations, scripts, integrations and reports in a sandbox account. A good support agreement makes this routine rather than an emergency, as described in NetSuite support and maintenance.

Customisation

Customisation on NetSuite is done within the platform: custom fields and records, workflows, scripts and the publisher's development tools. This is a strength of the model, because customisation built the intended way is designed to survive releases. It also sets a boundary. You cannot change the core code, install your own database extensions or reach the underlying servers.

Before committing, list the processes that make your company different and ask the integrator which are met by configuration, which need scripting and which would be better handled outside the ERP. The NetSuite customisation page goes into that boundary in detail.

Cost structure

Cloud-only does not automatically mean cheaper or dearer than on premise. It changes the shape of the cost:

• Less capital spending on servers, licences and refresh cycles.
• An ongoing subscription that depends on the edition, the modules and the number of users, so it rises as you grow.
• No hosting bill from a third party, but possible costs for sandboxes, extra environments and add-ons.
• Implementation, data migration, training and support, which exist whatever the hosting model.

For a full cost picture, read the ERP cost guide alongside the NetSuite pricing page. The subscription is rarely the largest uncertainty; scope is.

Performance and availability

Performance depends on the service itself and on your own connection and design choices. Heavy scripts, poorly built saved searches and badly designed integrations slow a cloud ERP as readily as an on-premise one. A UK business with several sites, including those in Scotland, Wales or Northern Ireland, should also check that its internet links are resilient, because staff cannot work in the system if the link fails.

Data location and UK data protection

For many finance directors this is the section that matters most, so here is a practical checklist rather than reassurance.

1. Know what personal data you will hold. An ERP typically contains employee records, customer contacts and supplier details. UK GDPR and the Data Protection Act 2018 apply, and the Information Commissioner's Office is the regulator.
2. Ask where the data is stored and processed. Request the answer in the contract documents, not only in a sales conversation, and ask how support access from other countries is handled.
3. Review international transfers. If any processing happens outside the UK, your data protection lead needs to understand the transfer mechanism that applies and confirm that it is documented.
4. Check the processing terms. The data processing agreement should state roles, security measures, sub-processors and what happens to your data when the subscription ends.
5. Plan the exit. Know how you export your records, in which format and within what notice, before you need to.

None of this prevents a UK company from using a cloud ERP, but it does need to be done deliberately. Your integrator can supply the technical description of the architecture; the legal review is for your own adviser.

Payroll and tax-related data

Payroll data deserves particular care because of its sensitivity. If you are weighing whether payroll should sit in the ERP at all, see NetSuite payroll and HR and the guide to payroll software and RTI. For VAT and digital record-keeping, the cloud model supports the digital links that Making Tax Digital expects, but the way your accountant files, and the software they use, should be agreed early.

Backups and continuity

With a publisher-run service, you do not run backup jobs or test tape restores. That does not remove all responsibility. Separate three questions:

The second row is where incidents actually happen. A well-run project restricts who can mass-update records, tests every import in a sandbox first and documents how to reverse a bad change. Ask your integrator to include this in the handover rather than assuming the cloud covers it.

Sandboxes and environments

A cloud ERP is safest when changes are made in a copy first. NetSuite customers can use sandbox accounts to test customisations, rehearse data loads and train users without touching live records. Use them for:

• Testing each new release against your scripts and integrations.
• Trialling a new workflow before it reaches the finance team.
• Rehearsing a migration before the real cutover, as set out in NetSuite migration.
• Training new staff on realistic data.

Ask which environments are included in your subscription and which would be charged separately, since this varies with the agreement.

How to decide whether the cloud model suits you

NetSuite cloud is a good match when most of the following are true:

• You want to avoid running servers and would rather spend management time on process.
• You can accept the publisher's release cadence and test around it.
• Your data protection review is satisfied by Oracle's contractual terms.
• Your processes can be met through configuration and platform-native customisation.
• You have several entities, currencies or locations and want one system across them, which is where NetSuite is often considered; see NetSuite in the UK.

It is a weaker match when:

• A policy, a customer contract or a regulator requires software on your own infrastructure.
• You need to control exactly when a version changes, for instance because of a long validation process.
• You want to modify the core code or run the database yourself.
• Your budget cannot absorb a subscription that grows with users and modules.

If you find yourself on the second list, compare options that offer a choice of hosting. The cloud versus on-premise ERP guide explains the trade-offs, and NetSuite alternatives shows where to look next. Odoo and Sage, for instance, are commonly discussed when a UK buyer wants more than one deployment route.

Questions to put to a NetSuite integrator

Use these in your first meeting to separate a precise supplier from a vague one:

1. How will you document the data location, sub-processors and transfer arrangements for our review?
2. Which sandbox environments will we have, and who tests each release?
3. What customisation do you propose, and does each item use platform-native tools?
4. Who is responsible for scheduled exports and for recovering from a user error?
5. What happens to our data and our customisations if we leave?
6. How will payroll, tax and VAT data be handled, and who coordinates with our accountant?

A supplier who answers these in writing is more likely to run a clean project. The guide to choosing an ERP integrator and the page on choosing a NetSuite partner give further criteria. For the project itself, see NetSuite implementation.

Next step

ERP Integrator is a free service: you describe your company, your sites and your requirements, and we put you in touch with an integrator suited to your project. We are not affiliated with any publisher, and the integrator carries out the work. If cloud-only is acceptable and you want to explore NetSuite, see how the matching works and send your request.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.