1) Hosting models for QBM Server

QBM Server hosting is not only "cloud vs not cloud". The real decision is who owns the environment, who controls administrator access, and who is responsible for uptime operations.

Use the selector below to update the architecture diagram and the hosting notes.

On-Prem means QBM Server and SQL Server run on a dedicated server inside your office. You own the hardware, and you own the operations.

Your Business Network

Ownership
  • PCs connect over LAN (and optionally VPN for remote users)
  • Access controlled by QBM login roles and Windows/network controls
  • Performance depends on your server hardware and local network quality

Your Local Server Room

LAN
  • QBM Server hosted as Windows Service / WCF gateway
  • SQL Server hosted locally (same server or dedicated DB server)
  • Backups, patching, monitoring are your responsibility
Operational reality: QBM reliability is mostly determined by (1) server stability, (2) SQL health, and (3) backups and monitoring. The hosting location changes who is responsible for these tasks, not whether the tasks exist.

2) Benefits and drawbacks (in practical terms)

The sections below are designed for decision-makers: clear tradeoffs, not marketing language. Use them to align IT expectations with business risk and budget.

Strengths

  • +Full local control: your data and server stay inside your premises.
  • +Low latency on LAN: excellent performance for office users.
  • +Predictable fixed assets: costs mostly up front (hardware) rather than ongoing monthly compute bills.
  • +Simple network: no dependency on internet for internal usage (remote users still need VPN/remote access).

Limitations and risks

  • -Operations burden: backups, patching, monitoring, and disaster recovery are on you.
  • -Single location risk: fire, flood, theft, power events can stop everything unless you invest in redundancy.
  • -Remote work complexity: secure VPN/RDP setup is required and must be maintained.
  • -Scaling requires hardware: upgrades can mean new equipment and downtime windows.
Clarification: VPS/Private Hosting and hyperscale cloud VMs (AWS/Azure/GCP) are both “your server in a data center” models. The difference is typically complexity and ecosystem: hyperscale clouds offer more optional services and enterprise features, while VPS providers often offer simpler pricing and simpler configuration for a private server instance.

3) Hosting provider examples (links)

Below are examples of providers businesses commonly use for VPS/VM hosting. Availability of Windows licensing, data center regions, and managed services differs by provider and plan. Always confirm what you need before purchasing.

InterServer VPS

VPS hosting option commonly used for private Windows server deployments. Suitable when you want "your own server" in a data center.

Visit provider
OVHcloud VPS

VPS and infrastructure services with multiple regions. Often selected for cost-effective VPS capacity and region choice.

Visit provider
Hetzner Cloud

Cloud servers (VMs) often used for predictable performance per VM with regional options (confirm Windows support based on plan).

Visit provider
DigitalOcean VMs

Simple VM provisioning for many workloads. Common choice when you want a clean UI and predictable VM sizing workflow.

Visit provider
AWS (Amazon EC2) Hyperscale

Enterprise cloud VM platform with extensive options. Suitable when you need advanced networking, scale, or integrations with cloud services.

Visit provider
Google Cloud (Compute Engine) Hyperscale

Cloud VMs with preset/custom machine types. Suitable when you want hyperscale networking options and cloud ecosystem features.

Visit provider
Microsoft Azure (Virtual Machines) Hyperscale

Cloud VM platform frequently selected by organizations already using Microsoft ecosystem tooling. Confirm region, pricing, and Windows licensing approach.

Visit provider
Important for QBM: Because QBM Server is a Windows Service stack with SQL Server, confirm: (1) Windows server availability/licensing, (2) SQL Server licensing plan, (3) backup storage strategy, and (4) remote admin access hardening (VPN/RDP gateway/MFA/allow-lists).

4) FAQ

Common questions about hosting QBM Server. Written in practical terms.

Is VPS the same as AWS/Azure/GCP?
The core concept is similar: you run your own server environment in a data center. The difference is usually the ecosystem and complexity:
  • Typical VPS providers: simpler pricing, simpler configuration, strong value for a private server instance.
  • Hyperscale clouds: more services and enterprise options, but more configuration and billing complexity.
What is the biggest risk with On-Premise hosting?
Operational discipline: backups (with restore tests), monitoring, patching, power/internet stability, and disaster recovery. On-prem can be excellent if these are managed consistently.
In “vendor-hosted cloud”, are customer databases shared?
QBM architecture does not support shared databases. By design, every customer has a separate SQL Server database and data is never mixed inside a single database. In vendor-hosted models, what may be shared is the platform layer (hosting environment, operational tooling, support workflow, and sometimes compute resources). This can reduce your direct control over performance policies, change schedules, and vendor-side access governance compared to a customer-owned private environment (VPS/VM).
If we choose VPS/cloud VMs, what must we do to make it safe?
Baseline requirements:
  • MFA for admin access (RDP/VPN/gateway).
  • Least privilege for users and support.
  • Backups with retention plus periodic restore tests.
  • Patching for Windows and SQL Server, plus monitoring.
  • Clear ownership of admin credentials and backup storage.
Disclaimer: This document is informational and does not constitute legal or security advice. Always validate licensing, security hardening, backup policies, and operational responsibilities with qualified IT professionals.