BlogChoosing an ERP
Cloud or on-premise ERP: how to choose.
For most small and mid-sized companies, a cloud ERP is the simpler choice: there is no server to maintain and access works from anywhere. On-premise makes sense when you have specific network or data requirements.
What the two mean
Cloud ERP runs on servers in a data centre. You open it in a browser or an app. The vendor looks after the server, the backups and the updates.
On-premise ERP runs on a server in your office or on a server you rent. You or your IT administrator are responsible for the hardware, backups and access.
In both cases the data is yours. The difference is who looks after the place where it lives.
There are in-between options too. For example, the system can run on a dedicated server just for your company, but in a data centre. For the owner, one thing matters: who is responsible when something stops.
Cost: up front and over three years
On-premise looks cheaper because there is no monthly hosting fee. But the calculation has to include everything that comes with your own server.
- A server, backup power and a place to keep it.
- Replacing the hardware after a few years.
- An IT administrator’s time for updates and backups.
- Remote access for people outside the office.
- The cost of downtime if the server fails.
The last line is often forgotten. If the server fails on Friday afternoon and the administrator comes on Monday, the loss is not just the repair. It is the orders that didn’t go out.
With a cloud ERP, most of these costs are included in the monthly fee. Compare the cost over three years, not the first month. How to do that is in the guide to ERP cost.
Security: which is safer
People often assume the server in the office is safer because it is “ours”. That is only true if someone actually looks after it.
An office server is as protected as the door, the passwords and the backups. A data centre has security staff, backup power and people whose job is exactly this.
Security depends on practices, not on location. Ask the same questions about both options:
- How often are backups made and where are they kept?
- When was a restore from backup last tested?
- Who has access to the data and how is that access logged?
- How is the software updated, and how quickly?
- What happens in case of fire, theft or a failed disk?
If you can’t answer these for your own server, the cloud with a good vendor is probably safer.
The most common problems in small companies are not hacker attacks but simple things. A backup nobody has checked. One shared password. A server under a desk that anyone can reach. These risks exist wherever the system runs.
Access and working outside the office
A cloud ERP opens anywhere there is internet: in the warehouse, on the shop floor, on a salesperson’s phone at a customer’s site. No separate setup is needed for each person.
An on-premise ERP generally works best on the office network. Access from outside needs extra setup and maintenance. With several sites, this quickly gets complicated.
Think about updates as well. With a cloud ERP, the vendor applies them for everyone at once. On-premise, someone has to install them, check that everything works and not put them off for months.
Consider the dependence on the internet. If the connection on the shop floor is weak, a mobile backup connection solves it. Raise it during the analysis.
Example: the numbers for a small company
Take a hypothetical company with 15 people, one warehouse and one office. The numbers below are only an illustration; use your own.
On-premise: a server costing, for example, 3,000 €, replaced after five years. Add, for example, four hours a month of support from an external administrator. There is also the risk of a day of downtime after a failure.
Cloud: a monthly fee that includes hosting, backups and updates. No hardware in the office and no administrator needed for the server.
Work out both totals over three years. Add the value of one day when nobody can issue an order or an invoice. That usually settles the question.
In this hypothetical case, the on-premise hardware and support alone come to 3,000 € plus 144 administrator hours over three years. Compare that with the monthly fee times 36. Then add the hours you yourself spend thinking about the server.
When on-premise makes sense
- You have your own IT team that already runs servers.
- Your site has no stable internet and no reasonable alternative.
- A customer contract requires the data to be physically on your premises.
- The ERP has to control machines on a closed network.
Even then, it is worth working out what that infrastructure costs and who maintains it when the person who built it leaves.
If none of these apply, the cloud is almost always the simpler path.
Conversely, the cloud suits you especially well if you have several sites, salespeople on the road, a warehouse in another town or nobody in charge of IT. Then your own server is one more responsibility nobody wants.
Questions for the vendor before you decide
Ask the same questions of whoever would maintain your on-premise server. If the answers are vaguer, you have your answer to the main question too.
How we approach it
We host the system in the EU and look after the server, backups and updates as part of monthly support. Your data stays yours: we hand it over in an open format whenever you ask. More on data and access is on the security page.