+1-980-999-8888
EN/中文
MTC · Industry Depth, Global Breadth
SAP Business One · U.S. Hosting Decision

Choose where B1 runs by responsibility, recovery and operational dependency

For a U.S. IT team, cloud versus on-premise is not just a server-location question. Compare who operates each layer, where data and backups reside, how plants and branches connect, and how the company exits or recovers.

Review Your Hosting Requirements→

Last reviewed · June 2026

Three workable U.S. operating models

Managed U.S. Cloud

Cloud-hosted B1

SAP Business One runs in a selected U.S. cloud region and is operated under a documented responsibility model for infrastructure, backups, patching, monitoring and recovery.

Advantages

  • Avoid buying and refreshing server hardware
  • Define backup and recovery service levels contractually
  • Support remote teams and multiple U.S. locations
  • Scale compute and storage through the hosting design

Considerations

  • Validate region, subcontractors, security controls and exit terms
  • Test latency for sites, scanners, printers and integrations

Customer-Controlled Infrastructure

On-Premise

The company runs B1 on infrastructure it owns or controls, either at a facility or in its chosen cloud account. Internal IT or a named provider operates the environment.

Advantages

  • Direct control over network, identity and infrastructure policies
  • Fit existing data-center or private-cloud standards
  • Coordinate tightly with plant-floor or local systems
  • Choose the operating and recovery model

Considerations

  • Company retains more security, backup and lifecycle responsibility
  • Hardware, licenses and specialist coverage must be budgeted

Hybrid Operating Model

Hybrid

The B1 core, remote access, integrations, data services or disaster-recovery components are split across controlled and managed environments for a specific operational reason.

Advantages

  • Keep plant or legacy dependencies close to the site
  • Use managed access for branches and remote staff
  • Phase infrastructure changes around business constraints
  • Separate workloads by operational need

Considerations

  • More network, identity and support boundaries to manage
  • Recovery and integration testing must cover both environments

Compare the responsibilities—not just the hosting label

DimensionCloudOn-PremiseHybrid
Cost patternRecurring hosting and operationsUpfront capacity + internal operationsBoth cost models
Operational ownerContracted provider + company application ownerCompany or named managed-services teamExplicitly divided
U.S. region choiceConfirm region and backupsCompany selects facilities or accountDocument each workload
Local dependenciesTest network, devices and integrationsDirect local connectivityDesigned around dependency boundaries
Recovery evidenceProvider runbook + customer testingCompany-owned runbook and testsEnd-to-end recovery test

A U.S. IT decision sequence

Start with operational dependencies and accountable owners, then compare cost and convenience.

Start with managed cloud

You want a contracted infrastructure owner, U.S.-region hosting, remote access and predictable backup and recovery responsibilities.

Start with customer-controlled infrastructure

Plants, local devices, existing security standards or other systems require direct control—and your team can operate or contract that environment.

Use hybrid only for a defined boundary

A plant, legacy system, branch-access pattern or staged migration creates a real reason to split workloads. Document support and recovery across both sides.

Write the responsibility matrix: For infrastructure, database, B1 application, identity, endpoint, backup, recovery and integrations, name what MTC, the hosting provider and your IT team each operate and approve. Learn about managed services →

Separate database from hosting: The HANA-versus-SQL decision affects skills and capabilities, but it is not the same decision as cloud versus on-premise. Compare HANA vs SQL →

U.S. Deployment FAQ

Which deployment model works best for a U.S. SMB?
Most U.S. teams with limited infrastructure staff start with cloud or managed hosting. On-premise remains reasonable when a plant has strict local-system dependencies or an established IT operation. The decision should document recovery objectives, security ownership, internet dependency, integration needs and five-year cost rather than follow a blanket cloud-first rule.
Can we move between cloud and on-premise later?
Yes. The move still requires a migration plan, downtime window, integration retesting and validation of backups and access controls. It is cheaper to include expected acquisitions, new locations and remote-user growth in the original three-to-five-year architecture.
How is MTC managed hosting different from simply renting a cloud server?
A cloud server is infrastructure. Managed hosting adds the operating work around SAP Business One: monitoring, backups, patch coordination, recovery procedures and support ownership. The service boundary and response commitments should be compared, not just the monthly server price.
What deployment options does SAP Business One support?
SAP Business One can run in cloud, on-premise or hybrid environments. Cloud reduces local infrastructure work, on-premise puts operations in your team’s hands, and hybrid keeps selected plant, warehouse or integration workloads local while the main environment is hosted.
What is hybrid deployment?
A hybrid design keeps selected systems or integration services at a plant or warehouse while hosting the ERP environment elsewhere. It is useful when scanners, production equipment, shipping systems or local files must continue operating with a controlled connection to the central system.
Does the deployment model affect price?
Yes. Deployment is one of the six pricing factors and affects both infrastructure cost and implementation. See the Pricing and TCO pages for a full breakdown.

Put your U.S. hosting decision on one responsibility map

Bring your locations, integrations, security standards, recovery target and IT ownership. MTC USA will compare the three models against those facts.

Review Deployment Requirements

Last updated: 2026-06-11 · Reviewed quarterly