Blog
SaaS or On-Premise: choosing your Business Central deployment
Business Central runs in two places: as a Microsoft-hosted cloud service (SaaS) or on infrastructure you control (On-Premise). The choice shapes your costs, your update cadence and how much of your team’s time goes to keeping the system alive rather than running the business. Here is how we walk clients through the decision — without the marketing gloss.
Updates: who carries the burden?
SaaS receives two major updates a year automatically, plus monthly service updates, on Microsoft’s schedule. You get new features as they ship and you never fall behind. On-Premise puts you in control of when you update — which sounds appealing until you realise it also means you own every upgrade project, with its testing, downtime and cost.
Why it matters: the On-Premise systems that cause the most pain are the ones nobody updated for five years. SaaS makes “staying current” the default rather than a recurring project you have to budget and fight for.
Infrastructure and maintenance
With SaaS, Microsoft runs the servers, the database, the backups and the security patching. With On-Premise, that is your responsibility — or your hosting partner’s — including hardware, SQL Server licensing, disaster recovery and the people to manage it all.
Why it matters: for most SMBs the hidden cost of On-Premise is not the licence, it is the staff time and the 2 a.m. phone call when a server fails. SaaS converts that into a predictable subscription and hands the on-call burden to Microsoft.
The cost model
SaaS is a per-user subscription: operating expense, predictable, scaling with headcount. On-Premise mixes a larger upfront investment (licences, hardware) with ongoing maintenance, and the real total only becomes clear when you add the infrastructure and people behind it.
Why it matters: a sticker-price comparison almost always flatters On-Premise, because it ignores everything it takes to keep the lights on. Compare total cost of ownership over three to five years, not licence against subscription.
Data residency and regulatory constraints
This is where a genuine hard constraint can appear. Some organisations face rules about where data physically lives, or sit in regulated sectors with specific certification requirements. Business Central SaaS runs in defined Microsoft datacentre regions with a broad compliance portfolio — which satisfies the large majority of cases — but a small number of organisations have obligations that only an On-Premise or private deployment can meet.
Why it matters: this is the deciding factor that is worth verifying early, with your compliance team, before any other discussion. If you do not have a written requirement that rules out the cloud, you almost certainly do not have this constraint.
Integrations and customisation
SaaS runs AL extensions and connects through APIs and standard connectors — which covers the overwhelming majority of integration needs. On-Premise can still be the answer when you depend on deep, low-level integration with on-site systems that cannot be reached cleanly from the cloud.
Why it matters: modern Business Central is built to be extended, not modified. If your “we need On-Premise for our customisations” instinct dates from a NAV system full of code changes, it is worth revisiting — most of that work is cleaner and cheaper as SaaS extensions.
Our honest recommendation
Choose SaaS unless you have a hard constraint that genuinely rules it out — a written regulatory requirement or an integration that truly cannot be reached from the cloud. For everyone else, SaaS lowers maintenance, keeps you current, makes costs predictable and lets your team focus on the business instead of the plumbing.
On-Premise remains a legitimate, fully supported path. But it should be a deliberate choice driven by a real requirement, not a default carried over from how things used to be.
Not sure which path fits your constraints? Tell us your story and we will give you an honest, free assessment.