SAP Business One · U.S. Hosting Decision

Choose where B1 runs by responsibility, recovery and operational dependency

Choose the deployment model from operating ownership, data and backup location, plant and branch connectivity, recovery targets and long-term infrastructure plans.

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

Requires coordinated network, identity and support operations
Recovery and integration testing must cover both environments

Compare the operating model behind each deployment option

Dimension	Cloud	On-Premise	Hybrid
Cost pattern	Recurring hosting and operations	Upfront capacity + internal operations	Both cost models
Operational owner	Contracted provider + company application owner	Company or named managed-services team	Explicitly divided
U.S. region choice	Confirm region and backups	Company selects facilities or account	Document each workload
Local dependencies	Test network, devices and integrations	Direct local connectivity	Coordinated around site dependencies
Recovery evidence	Provider runbook + customer testing	Company-owned runbook and tests	End-to-end recovery test

How the operating team works together

Operating area	MTC	Hosting provider	Customer IT
B1 application & database	Configure, monitor and support	Operate contracted infrastructure	Approve access and change windows
Backup & recovery	Define and test the B1 recovery plan	Run infrastructure backup services	Confirm business recovery targets
Identity & endpoints	Configure B1 roles and access	Support hosted access controls	Own users, devices and security policy
Integrations	Design, test and support interfaces	Provide network and platform services	Approve connected systems and owners

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 for a clear operational reason

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

Build one operating plan: For infrastructure, database, B1 application, identity, endpoint, backup, recovery and integrations, MTC coordinates the operating and approval roles with the hosting provider and your IT team. 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?

Managed hosting combines infrastructure with SAP Business One monitoring, backups, patch coordination, recovery procedures and support management. Compare the operating scope, recovery design and response commitments alongside the monthly 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.

Turn your U.S. hosting decision into one operating plan

MTC USA will map your locations, integrations, security standards, recovery targets and IT operating model to a recommended deployment design.

Review Deployment Requirements