QBM Cloud — VPS / Private Hosting (How It Works)

Choose a deployment model

Select a model below to update the diagram and notes. This keeps the explanation simple for business owners while still giving enough detail for IT decision-makers.

Important: VPS / Private Hosting can be hosted inside hyperscale clouds (AWS / Azure / Google Cloud) or on a VPS provider. The key idea is the same: a customer-specific environment and database boundary.

VPS / Private Hosting means: a customer-specific server instance and database boundary, isolated from other customers. This improves predictability and operational control.

Your Business

Users

Environment view

In VPS / Private Hosting, each customer environment is isolated. Hosting can be inside hyperscale clouds (AWS / Azure / Google Cloud) or via VPS providers. Below is an example of separate customer instances with clear boundaries.

Client A — Private Instance Isolated

App

QBM application instance (per customer)

Svc

QBM Server (Windows Service / WCF)

Sec

Customer-specific configuration and security boundaries

Dedicated SQL Server Database Data is not mixed with other customers

Client B — Private Instance Isolated

App

QBM application instance (per customer)

Svc

Private service layer (WCF gateway)

Ops

Operational controls (backup, monitoring, maintenance windows)

Dedicated SQL Server Database Predictable growth planning

Client C — Private Instance Isolated

App

QBM application instance (per customer)

Svc

QBM Server (Windows Service / WCF)

Cfg

Custom configuration aligned to business needs

Dedicated SQL Server Database Clear boundaries for governance

Integration-ready by design

A private environment makes integrations easier to govern and operate. For example, QBM can support e-commerce integration workflows (such as stock synchronization and item management) without mixing data across tenants, while keeping operational ownership clear per customer.

What you get with VPS / Private Hosting

These are practical outcomes customers care about. The wording below is intentionally concrete: less “marketing language”, more “what this architecture delivers”.

Business and IT outcomes

✓Complete data isolation: your database is not shared with other customers.
✓Predictable performance: sizing and scaling decisions are based on your usage, not other tenants.
✓Operational clarity: backups, monitoring, and maintenance can be managed per customer environment.
✓Security boundaries: isolation reduces blast radius and simplifies governance.
✓Flexible hosting: VPS provider or hyperscale cloud (still private per customer).
✓Upgrade control: isolated environments make scheduling changes and upgrades more controllable.

Who is this ideal for?

✓Businesses that want dedicated resources and consistent user experience.
✓Companies with multiple branches and the need for stable operations.
✓Organizations that prefer clear ownership of their environment and data boundaries.
✓Teams that require governance options (access rules, monitoring depth, maintenance policies).

Comparison: VPS / Private Hosting vs Shared Multi-Tenant

This is written to be fair and accurate. Multi-tenant ERPs are valid for many cases. VPS / Private Hosting is designed for customers who want stronger isolation and clearer operational control.

VPS / Private Hosting (Private QBM Environment)

✓Separate database per customer (clear data boundary)
✓Private service/app environment per customer
✓No “noisy neighbor” effect: resources are planned around your workload
✓Per-environment operations: backup, monitoring, maintenance can be defined per client
✓Customization and configuration are simpler in isolated environments
✓Hosting choice: VPS provider or hyperscale cloud (still private per customer)

Shared Multi-Tenant ERP (common model)

!Database and application resources are shared across tenants
!Performance can vary depending on other tenants’ load
!Customization is often limited to protect shared stability
!Upgrade schedules are typically global (same for all tenants)
!Incident impact may have broader blast radius in shared stacks
!Governance can feel less “direct” for customers with stricter requirements

FAQ

Common questions decision-makers ask when comparing hosting options. Adjust wording to match your real scope (backup policies, monitoring, high-availability options, and support hours).

Do we keep ownership of our data?

Yes. Customers retain ownership of their business data. Private environments make it easier to define clear boundaries for access and governance.

Do we have to host on AWS, Azure, or Google Cloud?

No. VPS / Private Hosting can be done on a VPS provider or inside hyperscale clouds. A VPS (Virtual Private Server) gives you a customer-specific server instance, typically at a predictable monthly cost, with practical benefits:

Private environment: your ERP services and database run in an isolated server instance.
Operational control: clearer control over access, backups, and maintenance policies.
Cost-effective: avoids buying on-prem hardware while still keeping a private, dedicated setup.

What does “private hosting” actually mean in practice?

It means the environment is provisioned for one customer: application instance, services layer, and database boundary. This improves:

Predictability (capacity planning based on your usage)
Isolation (reduced cross-tenant risk and blast radius)
Operational clarity (backup/restore and maintenance policies per environment)

Is On-Premise still possible?

Yes. On-premise can be suitable where full local control is required. However, server hardware, backups, monitoring, patching, and security remain the organization’s responsibility.

How does a private environment help with performance?

In shared platforms, tenants compete for common resources. In a private environment, capacity is planned around one customer, which makes performance more stable and easier to troubleshoot and scale.

How does this affect integrations (e-commerce, reporting, automation)?

Integrations often become easier to govern in private environments because data boundaries are clear and operations can be managed per customer instance (scheduling, monitoring, and troubleshooting).

Important note: Exact features included (monitoring depth, backup retention, high-availability options) depend on your plan and hosting choice. This page focuses on the architecture approach and the business impact.