ERP Deployment Models Compared
Cloud ERP, on-premises or hybrid? Compare four ERP deployment models on cost, upgrades and control. Business Central lists at $80 per user a month (Oct 2026).
Key takeaways
- The deployment model describes how and where the ERP's three layers, database, application logic, and presentation, are hosted and operated.
- In the public-cloud (SaaS) model, the vendor hosts the software in its own multitenant cloud, takes responsibility for infrastructure, patches, backups, and uptime, and sells it as a monthly or annual subscription per user.
- Private cloud means the ERP runs on cloud infrastructure dedicated to you rather than shared in a multitenant pool: a hyperscaler VM, a managed single-tenant tenant, or a vendor private-cloud offering (for example SAP S/4HANA Private Cloud or Odoo.sh as a managed PaaS).
- On-premises deployment installs the ERP on servers you own and operate inside your own data center or office.
What an ERP deployment model is
The deployment model describes how and where the ERP's three layers, database, application logic, and presentation, are hosted and operated. It is a separate decision from which product you buy. The same Dynamics 365 Business Central is available as Microsoft-hosted SaaS or as an on-premises installation; the same Odoo can run on Odoo Online (SaaS), Odoo.sh (managed platform), or a server you control. IBM frames the landscape as three primary forms: a cloud SaaS subscription model, an on-premises licensing model, and a hybrid model that blends characteristics of both, with private or dedicated cloud sitting as the control-oriented middle ground buyers use.
Deployment determines five things buyers care about most: how you pay (subscription versus license), who is responsible for patches, backups, and uptime, how often you get new features (and whether AI tools ship to your edition), how much you can customize, and how much capital you tie up in infrastructure. Getting the model wrong is expensive, not because the software features differ on day one, but because the operating model around them does. A team that buys on-premises expecting cloud hands-off maintenance, or buys multitenant SaaS expecting deep code-level customization, is set up to be disappointed.
In 2026 the market is cloud-first but not cloud-only. Industry summaries of ERP deployments put cloud-based systems at roughly seven in ten of all live deployments, with an even higher share of new implementations choosing cloud. On-premises still accounts for a meaningful minority (especially regulated industries, deep custom estates, and intermittent-connectivity sites) and hybrid remains common as a migration path or for edge workloads that cannot tolerate full round-trips to a distant SaaS region.
Public-cloud SaaS: the default for most SMEs
In the public-cloud (SaaS) model, the vendor hosts the software in its own multitenant cloud, takes responsibility for infrastructure, patches, backups, and uptime, and sells it as a monthly or annual subscription per user. You never touch a server, a database, or an upgrade. IBM defines SaaS straightforwardly: a third party manages the ERP software in the cloud, which removes the on-site infrastructure and technical maintenance burden. Microsoft steers most new Business Central customers online; Odoo Online is the equivalent multitenant path for Odoo Enterprise certified apps.
The trade-offs are well understood. The upside is predictable per-user cost, fast implementation, automatic and regular upgrades (major cloud ERP vendors commonly ship multiple application updates per year), built-in disaster recovery, and the ability to scale users up and down. The cost is less control over the upgrade calendar and the underlying infrastructure, tighter limits on deep customization (because changes that touch the shared codebase can break other tenants), and ongoing subscription expense that never ends as long as you use the system. For the great majority of SMEs (especially those without a dedicated infrastructure team) public-cloud SaaS is the correct default.
Public SaaS is also where new AI, analytics, and continuous-delivery features land first. If your growth plan depends on vendor roadmaps for copilots, embedded forecasting, or industry packs that only ship on the multitenant edition, choosing on-premises or a lagging private stack is a feature decision as well as an ops decision. Price the full subscription including known vendor price increases (Business Central Essentials and Premium list prices moved higher in late 2025) into any three-year model rather than assuming year-one list rates hold forever.
Business Central online shows how the SaaS rhythm works. Microsoft ships two major updates a year, generally available on the first workday of April and October, plus minor updates in every other month. Each major update has a five-month update period, a one-month grace period and then an enforced update, and administrators set a maintenance window for each environment. Microsoft presents this as the end of expensive upgrades every few years, which also means your extensions need a test pass twice a year.
Private cloud: SaaS-like hosting, your own instance
Private cloud means the ERP runs on cloud infrastructure dedicated to you rather than shared in a multitenant pool: a hyperscaler VM, a managed single-tenant tenant, or a vendor private-cloud offering (for example SAP S/4HANA Private Cloud or Odoo.sh as a managed PaaS). You still get cloud elasticity and off-site hosting, but you gain an isolated instance you control more tightly. Bring-your-own-cloud (BYOC) patterns (where a vendor operates software inside your AWS, Azure, or GCP account) are also rising in B2B software more broadly as buyers push back on putting the most sensitive operational data in a shared SaaS tenancy.
Private cloud sits between multitenant SaaS and classic on-premises. You get more control over the environment, the upgrade calendar, and integrations, and you avoid some multitenant customization limits (third-party modules, deeper extensions, staged upgrades). You also take on more operational responsibility (patching the OS, managing the database, scheduling backups) unless you pay a managed-services provider or a vendor PaaS (like Odoo.sh) to do it. The profile that fits private cloud is a business that wants cloud economics but needs tighter control for integration depth, data residency, upgrade freezes around peak seasons, or customization that multitenant SaaS will not allow.
Do not confuse "private cloud" marketing with true isolation. Ask whether the database is single-tenant, who holds encryption keys, which regions store backups, and who schedules upgrades. A "private" SKU that still forces vendor-timed major upgrades and blocks custom modules is closer to premium SaaS than to on-premises freedom.
On-premises: maximum control, maximum responsibility
On-premises deployment installs the ERP on servers you own and operate inside your own data center or office. IBM describes it as deployed onsite and controlled in-house, with the company responsible for technical and application maintenance. You buy perpetual or term licenses, own the infrastructure, and decide entirely when and whether to upgrade.
On-premises maximizes control and customization (you can modify the system deeply because you are not sharing code with other tenants) and it can avoid a pure per-user subscription bill, replacing it with a large upfront license plus annual maintenance. The costs are equally real: you carry all infrastructure, security, backup, and upgrade responsibility; you fall behind on new features unless you fund major version upgrades; and you tie up capital in hardware that depreciates. On-premises now makes sense for a narrow set of SMEs: deep customizations, strict data-residency or air-gap requirements, intermittent connectivity, or regulated industries with explicit on-premises mandates.
Vendor policy is reinforcing that on-premises is a special case, not the default. Microsoft clarified that end dates for Business Central on-premises perpetual licensing apply to new-customer purchases; customers with an active Enhancement Plan retain transition paths (for example Dynamics NAV perpetual to Business Central on-premises perpetual under service-plan rules). Separately, on-premises Enhancement Plan rates have continued to rise (partners reported a move from 19% to 20% of license value in 2025). Odoo still supports full on-premises for Enterprise and Community, with no SaaS SLA from Odoo SA, you own uptime, backups, and upgrades unless a partner contracts them.
Hybrid: blending cloud, on-premises and the edge
Hybrid deployment mixes worlds: some ERP capabilities run in the cloud while others stay on-premises or at the edge, often with shared identity and integration between them. IBM defines hybrid as a system for companies that want characteristics of both an onsite and a SaaS model. A common enterprise pattern keeps a regulated financial core private or on-premises while running analytics, CRM, or e-commerce in public SaaS. Another pattern (especially relevant for retail, distribution, and manufacturing) keeps POS, shop-floor, or warehouse execution local for latency and offline resilience while the financial and planning spine runs in the cloud.
Practitioners and cloud partners increasingly describe hybrid not as "half-migrated forever" but as intentional placement: factory and logistics systems may need ultra-low latency and local resilience, while corporate ERP and analytics scale better on Azure, AWS, or a vendor SaaS region. That is a durable architecture for multi-site operations, not just a temporary compromise. Still, for a single-site SME with one ERP database, pure hybrid is often higher TCO than either pure SaaS or pure on-premises because you inherit two security models, two upgrade calendars, and an integration seam that must be monitored.
Treat hybrid as a migration tactic when you are moving a monolith off the server room over 12 to 36 months. Treat it as a steady-state architecture only when you have a concrete, durable reason to split the workload, edge latency, sovereignty for a subset of data, or a two-tier model where HQ runs one ERP and subsidiaries run a lighter cloud system.
How Odoo and Business Central map to each model
Abstract models only help if you can place the products you are shortlisting. Two SME-relevant stacks make the mapping concrete: Odoo's three hosting types and Microsoft Dynamics 365 Business Central's online versus on-premises paths.
Odoo Enterprise runs in three official hosting modes. Odoo Online is multitenant SaaS: certified (core) apps only, Studio-level no-code customization, third-party apps and source changes blocked, Odoo-managed upgrades, backups, and a 99.9% uptime SLA. Odoo.sh is a managed PaaS for customized implementations: certified apps plus third-party modules, GitHub-linked CI, staging branches, and the same class of uptime and backup commitments as Online, with you choosing workers and staging capacity. On-premises is self-hosted (your metal or any IaaS you choose): unlimited customization including Community, no Odoo SA infrastructure SLA, and you own disaster recovery and upgrades, or you hire a partner. You can migrate between platforms; complexity depends on direction and custom code.
Business Central online is Microsoft-hosted SaaS: Microsoft stores the data, partners focus on configuration and extensions rather than SQL Server install, and environments are administered as cloud tenants. Business Central on-premises remains available for customers who need local install, multi-server component layouts, and full environment control, but Microsoft's commercial posture is online-first, with new-customer on-premises perpetual purchasing restricted and Enhancement Plan customers following service-plan transition rules. Extensions via AppSource and AL remain the customization model online; on-premises allows deeper environment control at the cost of self-managed infrastructure.
Use the map below when a salesperson says "we do cloud" without specifying multitenant SaaS, managed single-tenant, or self-hosted IaaS. The same product name can mean three different operating models, and three different TCO curves.
The phrase "managed ERP cloud" covers two different jobs. The first is vendor-managed SaaS, where Microsoft runs Business Central online or Odoo runs Odoo Online and hosting, maintenance and upgrades come with the subscription. The second is a specialist running the estate with you: regression tests on each Business Central update, maintenance of custom Odoo code, and support for Odoo.sh or self-hosted systems. Ask which of the two a quote means. Odoo.sh is covered in the Odoo.sh hosting guide.
| Product path | Closest model | Customization | Who runs infra | Typical SME fit |
|---|---|---|---|---|
| Odoo Online | Public-cloud SaaS | Studio / certified apps only | Odoo SA | Standard processes, fast go-live |
| Odoo.sh | Private / managed PaaS | Third-party apps + custom modules | Odoo SA (PaaS) | Custom Odoo without self-hosting |
| Odoo on-premises | On-premises (or self-managed IaaS) | Unlimited (Enterprise or Community) | You or your hoster | Sovereignty, deep code, offline sites |
| Business Central online | Public-cloud SaaS | Extensions / AppSource AL | Microsoft | Default for new BC customers |
| Business Central on-premises | On-premises | Deeper environment control + extensions | You | EP customers, residency, air-gap cases |
Cost, control, upgrades, and customization side by side
The decision collapses to a few axes: how you pay, how much you control, how often the system changes under you, who patches security, and how deep customization can go. Public cloud trades capital for subscription and gives you frequent, automatic upgrades in return for less control. On-premises does the opposite, you own and control everything, fund your own upgrades, and keep a perpetual or term license. Private cloud and managed PaaS split the difference with cloud hosting and more control. Hybrid inherits the cost of both sides and the upgrade complexity of keeping them in sync.
Upgrade responsibility is the axis most RFP scorecards underweight. Multitenant SaaS means the vendor picks the window; you test extensions ahead of the wave. Private cloud and on-premises mean you (or your MSP) schedule upgrades, and you own the risk of staying on an unsupported version. Customization depth tracks the same axis: multitenant SaaS pushes an extension model; single-tenant and on-premises allow deeper change at the price of upgrade friction.
The table below summarizes the four models on the dimensions that drive SME decisions. Read it as a starting point, not a verdict, the right model always depends on operational capacity, compliance constraints, and whether your differentiator lives in configuration or in custom code.
| Dimension | Public cloud (SaaS) | Private cloud / PaaS | On-premises | Hybrid |
|---|---|---|---|---|
| How you pay | Per-user subscription | Subscription + usage / workers | License + annual maintenance | Mix of both |
| Upgrades | Automatic, vendor-paced | You or vendor schedule; often staged | You fund and run major upgrades | Two calendars to keep in sync |
| Customization depth | Limited (extension model) | Moderate to deep | Deep | Varies by component |
| Infrastructure responsibility | Vendor | Shared / you or MSP / PaaS | Fully yours | Yours + vendor |
| AI / new features lag | Lowest (ships first) | Medium | Highest if versions lag | Cloud side first |
| Upfront cost | Low | Low to medium | High | High |
| Ongoing cost | Continuous subscription | Continuous + ops or PaaS fee | Lower run cost, big upgrade spikes | Highest combined |
| Best for | Most SMEs without infra teams | Control + cloud economics | Deep customization / residency / air-gap | Edge + cloud spine, or phased migration |
What cloud ERP costs in the US and Canada
Cloud ERP is two purchases: the subscription, quoted per user per month, and the implementation project. As of October 2026, Microsoft lists Business Central at $80 per user per month for Essentials, $110 for Premium and $8 for Team Members in the US, paid yearly. In Canada the same plans list at CAD $108.50, CAD $149.20 and CAD $10.90, paid yearly and plus applicable tax. Microsoft notes that displayed prices are informational and the checkout price can differ by currency, country and region.
Premium includes everything in Essentials plus enhanced service management and manufacturing capabilities, so a plant that plans production should price Premium. Worked example with stated assumptions: 8 full users on Premium, paid yearly at October 2026 list price, before tax and partner discounts. That is 8 x $110 x 12 = $10,560 a year in the US, or 8 x CAD $149.20 x 12 = CAD $14,323.20 a year plus tax in Canada. The same 8 users on Essentials would cost $7,680 in the US, a $2,880 difference, but would leave manufacturing off the license.
Odoo prices by plan rather than by module. Odoo Standard runs on Odoo Online only and cannot use custom modules. Odoo Custom adds Studio, agentic AI, multi-company and an external API, and can run on Odoo Online, on Odoo.sh (hosting cost not included) or on-premises. Odoo shows several per-user figures on its pricing page and states that the discount is valid for 12 months for the initial users ordered, so confirm the rate that applies to you on the day you buy.
None of these totals include implementation, which covers configuration, data migration and training and is scoped separately. For the full Business Central price table and a three-year example, see the Business Central pricing guide. For Odoo plans and Success Packs, see the Odoo pricing guide, and for vendor-by-vendor benchmarks see ERP cost per user. Over three years cloud ERP is usually cheaper than a legacy install for a company without an infrastructure team, for the reasons in the next section.
| Plan | US price | Canada price | What it covers |
|---|---|---|---|
| Business Central Essentials | $80 | CAD $108.50, plus tax | The base Business Central plan |
| Business Central Premium | $110 | CAD $149.20, plus tax | Everything in Essentials, plus service management and manufacturing |
| Business Central Team Members | $8 | CAD $10.90, plus tax | Limited license for reading data, approving workflows and updating selected information |
Total cost of ownership over three years
The most common deployment mistake is comparing only the first-year bill. A public-cloud SaaS looks cheap at month one because there is no infrastructure to buy, but its subscription compounds: by year three the cumulative per-user cost has often overtaken a naive on-premises license line, provided you had already budgeted for servers, backups, database licenses, and the staff to run them. Conversely, on-premises looks cheaper on a license line and hides its real cost in depreciation, electricity, security tooling, and the major-upgrade bill that arrives every few years.
A fair three-year comparison must include every hidden line: SaaS subscription including announced price increases, private-cloud compute and storage and the managed-services or PaaS fee, on-premises hardware depreciation and replacement, database and OS licensing, backup and disaster recovery, security tooling, partner retainers, and the internal hours to keep it all running. When all of that is on the page, public cloud wins for most SMEs precisely because it converts an unpredictable capex-plus-staff burden into predictable opex, and most small businesses undervalue the staff time that on-premises quietly consumes.
Market context is directional, not a substitute for your spreadsheet. Vendor incentives, partner skills and new product features cluster on cloud editions. That does not make SaaS automatically cheaper for a 15-year deep-custom manufacturer with idle server capacity. Model your own user count, integration estate, and upgrade policy before accepting any generic "cloud saves 30 to 50%" claim.
Security, data residency, and digital sovereignty
A persistent myth is that on-premises is more secure because the data sits behind your firewall. In practice, the reverse is usually true for an SME. A major cloud vendor invests more in security, certification, patching, and disaster recovery than almost any small business can match, and a multitenant SaaS shares that investment across all tenants. The cases where on-premises or private cloud improves the risk posture are narrower: specific data-residency or sovereignty rules that forbid certain data leaving a jurisdiction, air-gapped environments, regulated industries with explicit hosting mandates, or a security team that can out-execute the vendor's shared responsibility model.
Digital sovereignty has become a louder buyer theme in 2025 to 2026, including classic GDPR residency and control over who operates the stack, which law enforcement can compel the hoster, and whether AI features send operational data to a shared model endpoint. That is why private cloud, SAP private cloud messaging, and BYOC-style deployments show up in practitioner discussions alongside classic on-premises. Sovereignty is a control and legal decision; it is not automatically a "safer against ransomware" decision. A poorly patched on-premises box inside a jurisdiction still loses to a well-run SaaS region.
For Business Central online, data residency is a country setting. The country chosen when an environment is created sets both the localization and the Azure geography that stores the database: Canada environments use the Canada geography and United States environments use the United States geography. Pick the country deliberately when you create the environment. On Odoo, Standard stays on shared Odoo Online, while Custom can move to Odoo.sh or a self-hosted server, which changes who operates the host.
For the great majority of SMEs, the security question is not "where does the data sit?" but "who is responsible for patching, backups, access control, and recovery, and are they better at it than I am?". If the vendor's dedicated security team is better at it, public cloud is the safer choice. If the answer is a regulated obligation, customer contract, or air-gap requirement, then private cloud or on-premises is forced, but that is compliance and control, not a free security upgrade.
A practical decision checklist for SMEs
Walk these questions in order. Stop when a hard constraint appears; otherwise keep the default of public-cloud SaaS.
First, hard constraints: Do laws, customer contracts, or an air-gap require data to stay in a specific facility you control? Is connectivity intermittent at sites that must keep selling or shipping when the WAN is down? Do you already run custom code that a multitenant SaaS vendor will refuse to host? Any yes here pushes private cloud, on-premises, or a hybrid edge design, not a pure SaaS default.
Second, operating capacity: Do you have (or will you fund) people who patch OS/DB, restore backups, and own major upgrades? If no, multitenant SaaS or a fully managed PaaS (Odoo.sh-class) is the answer even if you "prefer" control. Control you do not staff turns into outages.
Third, differentiation: Can you live inside configuration, workflows, and an extension model, or does your competitive process depend on custom code? Configuration-friendly teams stay on SaaS. Code-heavy teams budget for private cloud or on-premises and for the upgrade tax that comes with it.
Fourth, economics: Build a three-year TCO with subscriptions (including list-price increases), partner hours, infrastructure, and internal time. Compare that to license + maintenance + hardware + people. Then choose. The deployment decision is reversible but expensive to undo, so pressure-test it against real operational capacity before you sign.
Before you shortlist vendors, settle three more points. Decide the deployment before the brand, so that "cloud" is never an open checkbox. Decide seats from the work: people who post invoices or run production need full licenses, while people who only approve or look up data may fit a limited license. Decide ownership by name: your IT lead owns identity, access and device security, and the implementation partner owns configuration, data migration, testing and the update calendar, with one person on your side accountable for each. For migration steps see the ERP migration guide, and for project budgets see ERP implementation cost.
| Signal | Lean toward | Watch-outs |
|---|---|---|
| No infra team, standard processes | Public-cloud SaaS | Extension limits; subscription forever |
| Need third-party modules / custom apps, still want managed hosting | Private cloud / managed PaaS (e.g. Odoo.sh) | PaaS fees; still test every upgrade |
| Air-gap, strict residency, or deep fork of the codebase | On-premises or self-managed IaaS | You own security and upgrade debt |
| Stores/plants need offline or ultra-low latency | Hybrid edge + cloud spine | Integration monitoring; dual ops models |
| Phased move off a legacy server | Temporary hybrid migration | Do not leave hybrid as accidental forever |
How to choose the right deployment model
Start from the default and deviate only with a reason. For an SME without a dedicated infrastructure team, public-cloud SaaS is almost always correct: it minimizes upfront cost, offloads operations, and delivers continuous upgrades and cloud-first AI. Move to private cloud or managed PaaS when you need cloud economics plus tighter control over the environment, the upgrade calendar, third-party modules, or integrations that multitenant SaaS restricts. Choose on-premises only when you have a durable, specific reason (deep customizations, data residency, air-gap requirements) and the staff (or a contracted partner) to run it.
Avoid hybrid as a destination unless you have a concrete workload split (edge latency, two-tier subsidiary ERP, or a regulated core) that justifies the added integration cost; use it as a migration tactic otherwise. Map the shortlist products explicitly (Odoo Online versus Odoo.sh versus on-premises, Business Central online versus on-premises) so "cloud" never remains an ambiguous checkbox on a vendor slide.
Whatever you choose, model the full three-year total cost of ownership including every hidden line, not just the year-one invoice. Document who owns upgrades, backups, and security patching by name. Pick the model your team can operate for the next five years.
The table below puts the main cloud options side by side for a buyer in the US or Canada.
For a wider product comparison, read Odoo vs Dynamics 365 and Odoo vs Business Central.
| Option | Who hosts | Customization | Best fit |
|---|---|---|---|
| Business Central online (Essentials or Premium) | Microsoft; the environment country places the database in the US or Canada Azure geography | Extensions and AppSource apps | Finance, sales and operations; Premium for manufacturing and service management |
| Odoo Standard | Odoo, on Odoo Online only | Configuration; no custom modules | Standard processes and a fast go-live |
| Odoo Custom | Odoo Online, Odoo.sh (hosting extra) or self-hosted | Studio, external API and custom modules | Multi-company, custom workflows or code |
| Business Central on-premises | You | Deeper environment control | Residency, air-gap or legacy Enhancement Plan cases |
How Flectic can help
Flectic is an independent consultancy that implements both Odoo and Dynamics 365 and earns no vendor quota on either. For companies of 20 to 100 people in the US and Canada choosing a platform and a hosting model, our ERP selection service compares the options in discovery and ends with a written recommendation. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call.
Sources
ERP software systems come in three forms: a cloud SaaS subscription model, an on-premises licensing model, and a hybrid model; IBM defines SaaS, onsite, and hybrid characteristics accordingly.
ibm.comOdoo Enterprise can be hosted on Odoo Online (SaaS), Odoo.sh (PaaS), or on-premises; Online limits third-party apps and source changes; Odoo.sh and on-premises allow third-party apps; Online and Odoo.sh share 99.9% uptime SLA class commitments from Odoo SA.
odoo.comVentor.tech comparison: Odoo Online is simplest with very limited customization (Studio); Odoo.sh supports third-party apps with limited-to-moderate customization; on-premises allows unlimited customization and Community or Enterprise.
ventor.techMicrosoft Learn deployment overview: Business Central can be deployed online (Microsoft-hosted) or on-premises; online removes local SQL install burden; on-premises Setup supports multi-computer component installs.
learn.microsoft.comMicrosoft partner response (Feb 2025): Business Central on-premises end date for perpetual licenses applies to new-customer purchases; Enhancement Plan / service-plan license transition policies (e.g. NAV to BC on-prem) remain unchanged.
techcommunity.microsoft.comPartner reporting: Dynamics 365 Business Central on-premises Enhancement Plan maintenance rate increased from 19% to 20% (effective October 2025) for NAV/BC on-prem maintenance.
agolution.comIndustry reporting of Business Central SaaS list price increases effective around November 2025 (Essentials ~$80/user/month, Premium ~$110/user/month band cited by partners).
congruentsoft.comQuantumrun Global ERP Statistics 2026 summary: ~70.4% of ERP deployments cloud-based in 2025; ~78.6% of new implementations cloud; on-premises still a material share of installed base.
quantumrun.comHouseblend 2025 analysis: cloud-first strategies are widespread yet hybrid ERP remains common for security, compliance, sovereignty, and complex integration reasons; wholesale cloud migration is not feasible for every enterprise.
houseblend.ioGartner predicted more than 85% of organizations would embrace a cloud-first strategy by 2025 (TechRepublic summary of Gartner research).
techrepublic.comNTT DATA (May 2025): ERP deployment choices among on-premises, public cloud, private cloud, and hybrid affect agility, compliance, and cost; hybrid blends models per workload.
services.global.nttX/practitioner signal: hybrid cloud framed as placing each workload where it delivers most value rather than a binary on-prem vs cloud choice (ITPro hybrid cloud overview shared in Jul 2026 discussion).
x.comX/industry signal: BYOC (deploy vendor software into the customer cloud account) rising as an alternative to pure multitenant SaaS for sensitive operational data (Nuon, Jul 2026).
x.comX/case signal: manufacturing hybrid with Azure + Azure Local for low-latency factory systems alongside large SAP landscapes; intentional hybrid rather than full lift-and-shift (Nordcloud/IBM, Jul 2026).
x.comBusiness Central list prices, paid yearly: Essentials $80, Premium $110, Team Members $8 per user per month in the US. Premium adds service management and manufacturing over Essentials.
microsoft.comCheckedBusiness Central Canada list prices, paid yearly and plus applicable tax: Essentials CAD $108.50, Premium CAD $149.20, Team Members CAD $10.90 per user per month; prices are informational and can differ at checkout.
microsoft.comCheckedOdoo Standard runs on Odoo Online only; Custom adds Studio, agentic AI, multi-company and external API and can run on Odoo Online, Odoo.sh (hosting cost not included) or on-premises; the discount is valid for 12 months for initial users ordered.
odoo.comCheckedBusiness Central online has two major updates a year, in April and October, minor updates in other months, a five-month update period, a one-month grace period and then an enforced update; administrators set a maintenance window per environment.
learn.microsoft.comCheckedThe environment country sets the localization and Azure geography for the database; Canada maps to the Canada geography and the United States to the United States geography.
learn.microsoft.comChecked
Frequently asked questions
What are the four ERP deployment models?
The four realistic deployment models for an SME are public-cloud SaaS (vendor-hosted multitenant, sold per user as a subscription), private cloud or managed PaaS (a dedicated or single-tenant-style instance on cloud infrastructure with more control), on-premises (installed on servers you own and operate), and hybrid (a mix of cloud, on-premises, and sometimes edge components). IBM frames the landscape as cloud SaaS, on-premises licensing, and hybrid; private cloud is the dedicated-hosting middle ground buyers use between pure SaaS and classic on-premises.
Is cloud ERP cheaper than on-premises?
Usually yes over three years for an SME, but only when you count every line. Public-cloud SaaS has low upfront cost but a continuous subscription that compounds and may rise with vendor price updates; on-premises has a lower ongoing software run cost on paper but hides hardware depreciation, database and OS licensing, backups, security, partner hours, and major-upgrade spikes. Include the staff time on-premises quietly consumes. For most SMEs without an infrastructure team, cloud wins because it converts unpredictable capex-plus-staff into predictable opex.
When does on-premises ERP still make sense in 2026?
On-premises still makes sense for a narrow set of SMEs: deep customizations multitenant SaaS will not host, strict data-residency or sovereignty rules, air-gapped or intermittently connected sites, and regulated industries with explicit on-premises mandates, plus the budget and people to run infrastructure, security, and upgrades. It is no longer the default. Microsoft restricts new-customer Business Central on-premises perpetual purchasing while Enhancement Plan transition policies for existing NAV/BC on-prem customers remain; Odoo still fully supports self-hosting for teams that accept the operational burden.
What is the difference between public cloud and private cloud ERP?
Public-cloud ERP is almost always multitenant SaaS: many customers share an application stack with logical data isolation, vendor-paced upgrades, and the lowest operational burden. Private cloud ERP runs on dedicated or single-tenant infrastructure (your hyperscaler account, a vendor private cloud, or a managed PaaS) so you gain more control over isolation, integrations, and often upgrade timing, at higher cost and more shared operational responsibility. Ask vendors who holds the keys, who schedules upgrades and whether third-party modules are allowed, because "private" marketing is not always single-tenant.
Odoo Online vs Odoo.sh vs on-premises, which should I choose?
Choose Odoo Online if you can live on certified apps and Studio-level customization and want Odoo to run hosting, backups, and upgrades under a 99.9% uptime SLA. Choose Odoo.sh if you need third-party apps or custom modules with Git-based development, staging, and CI while still keeping managed hosting. Choose on-premises (or self-managed IaaS) if you require full control, Community edition options, or sovereignty that a managed platform cannot meet, and you have the skills or a partner to own uptime and upgrades. Migration between platforms is possible but is a real project when custom code is involved.
Can I switch ERP deployment models after implementation?
Yes, but it is rarely trivial. Migrating between on-premises and cloud (or Odoo Online to Odoo.sh, or the reverse) is a real project involving data relocation, re-licensing, retesting integrations, and often re-platforming customizations. Treat it as a mini-implementation, not a setting change. The most common lowest-risk path is a phased migration from on-premises to public-cloud SaaS, sometimes via temporary hybrid. Choosing a vendor whose product runs across models (Business Central or Odoo) keeps the option open without changing products.
Does multitenant SaaS put my data at higher security risk?
For most SMEs, no. Major SaaS ERP vendors typically outspend small IT teams on certification, patching, monitoring, and disaster recovery. The residual risks are shared-responsibility mistakes (weak identity, over-privileged partners), contractual or sovereignty constraints, and concentration risk if you care who can be compelled to produce data. On-premises only improves security if your team patches, hardens, and tests restores. Choose private cloud or on-premises for control and compliance obligations; do not assume local servers are safer by default.
What is cloud ERP?
Cloud ERP is business software that runs your finance, sales, inventory and operations on the vendor's servers, which you reach over the internet. The vendor handles hosting, backups and upgrades, and you pay a subscription per user. Business Central online and Odoo Online are the two most common examples for companies of 20 to 100 people.
How much does cloud ERP cost for a small business?
As of October 2026, Business Central Essentials lists at $80 per user per month in the US and CAD $108.50 in Canada, paid yearly. Ten full users on Essentials come to $9,600 a year in the US before tax and discounts. Implementation, covering configuration, data migration and training, is a separate project cost.
Who hosts Business Central, and where is the data stored?
Microsoft hosts Business Central online. The country you pick when you create an environment sets the Azure geography for the database, so a Canada environment is stored in the Canada geography and a United States environment in the United States geography. Business Central can also be installed on-premises if you need to run it yourself.