VPS or private hosted server
QBM runs in a customer-specific private hosted environment with a dedicated database boundary. Predictable monthly cost, no on-prem hardware, full operational isolation.
QBM Deployment: Cloud, Private Hosting, or On-Premise
QBM is available for cloud, private hosting, or on-premise deployment. It can run in a local, private hosted, or cloud server environment while keeping each customer's QBM environment and database separated.
One QBM, three deployment paths
Choose how QBM runs, without changing what QBM is
The QBM application environment, modules, reports, database boundary, and integrations are the same in every model. What changes is where it runs and who operates the underlying infrastructure.
Customer-controlled cloud environment
QBM can run in a customer-controlled cloud environment. The customer keeps the cloud relationship, billing, and policies; QBM keeps the application and database boundary separated.
On-premise local server
QBM runs on a server you own, inside your office or data centre. Best fit for businesses that want full local control, fast LAN performance, and operational independence from external internet.
Architecture
One private QBM environment per customer, with a separated database
QBM keeps each customer's environment separate. Whether you deploy on-premise, in private hosting, or in a cloud environment, every customer gets a dedicated QBM application environment and database boundary. Customer data is never mixed with other customers.
- Dedicated QBM application environment for each customer
- Dedicated database boundary with no shared customer records
- Customer-specific configuration, security boundaries, backup and recovery policies
- Predictable performance - capacity is planned around your usage, not other tenants
- Clean integration boundaries for e-commerce, payroll, banking, and e-invoicing partners
Deployment comparison
What changes between cloud, private hosting, and on-premise
The QBM product is identical. The differences are about who runs the infrastructure, where the data lives, how internet dependency is handled, and how cost is structured.
| Area | VPS / Private Hosting | Cloud Environment | On-Premise |
|---|---|---|---|
| Customer boundary | Dedicated QBM environment and database per customer | Dedicated QBM environment and database per customer | Dedicated QBM environment and database per customer |
| Hardware | Provider's data centre, no hardware to buy | Hyperscale cloud, no hardware to buy | Customer-owned server, on customer premises |
| Internet need | Reliable internet required for daily access | Reliable internet required for daily access | Core access works over the local network even if external internet is slow |
| Infrastructure operations | Provider runs the platform; backup and maintenance policies set per customer | Customer's cloud account; cloud team or Business Aim partner handles environment operations | Customer's IT team runs the local environment, backups, maintenance, endpoint protection, and recovery planning |
| Cost shape | Predictable monthly hosting; lowest upfront commitment | Cloud usage-based; aligns with existing cloud spend | Higher upfront server, licensing, and IT effort; lower recurring hosting fee |
| Customization & integrations | Full QBM customization available | Full QBM customization available | Full QBM customization available |
| Typical best fit | Most SMB and mid-market businesses that want a private environment with minimal IT overhead | Businesses already standardized on a preferred cloud provider | Businesses that need offline-tolerant local operations or strict on-site data policies |
What every QBM deployment gives you
Same product, same controls, same data boundary
Customers should not have to choose between "cloud convenience" and "on-prem control". With QBM, the application, security model, and database boundary stay consistent across deployment models.
Data ownership
Customers retain ownership of their business data in every model. Backups, access policies, and data residency are defined per environment, not by a shared platform vendor.
Separated database
Every customer environment uses its own database boundary. There are no shared customer records, shared customer tables, or cross-customer reporting joins, regardless of where QBM runs.
Predictable performance
Because each customer has dedicated resources, performance is planned around your users, branches, transaction volume, and reporting workload - not someone else's.
Operational clarity
Backup schedules, restore tests, monitoring, and maintenance windows can be defined per environment, which makes audits and DR planning simpler.
Customization room
Reports, print templates, document flows, custom fields, integrations, and workflow configuration are available in every deployment model.
Implementation support
Business Aim consultants help size users, modules, integrations, hosting, and migration whether you choose cloud, private hosting, or on-premise.
How we recommend a deployment
We size the deployment around your business, not a sales tier
Most businesses pick a deployment model based on five practical factors. We work through them with you on the first call.
- Number of users, branches, warehouses, and POS counters that connect to QBM
- Internet reliability across your offices, branches, and remote teams
- Internal IT capacity - do you want to run servers, or have us host them
- Compliance and data-residency requirements (UAE VAT, ZATCA, PINT AE, audit)
- Existing cloud relationship - if you already use a preferred cloud provider, we plan around that environment
Common deployment patterns
- Single-office SMB: VPS / private hosting - lowest IT overhead
- Multi-branch retailer: private hosting or cloud environment with branch POS sync
- Manufacturing / warehouse: on-premise plus VPN for off-site users
- Group with cloud standard: cloud environment in the group's existing account
- Strict on-site policy: on-premise local server with planned backup and DR
Reference architecture
QBM deployment reference documents
These help-library guides explain hosting choices, component flow, data privacy, and deployment planning across QBM deployment models.
QBM Cloud Architecture
Interactive walkthrough of VPS / private hosting, on-premise, and shared-platform models, with isolation, performance, and operations notes.
Open guideHosting QBM Server
Practical guide to hosting QBM across on-premise dedicated environments, VPS / private hosting, cloud environments, and shared vendor-hosted ERP models.
Open guideCloud ERP Data Privacy
What to ask any cloud ERP vendor before signing: data location, isolation, ownership, exit terms, and recovery commitments.
Open guideQBM System Architecture & Component Flow
Component-level view of how QBM application, service, and database layers connect across deployment models.
Open guideFAQ
Frequently asked questions about QBM deployment
Quick answers to the deployment questions buyers ask most often. The full architecture guides above go deeper.
Is QBM cloud or on-premise?
Both. QBM is available for cloud, private hosting, or on-premise deployment while keeping each customer's QBM environment and database separated.
Is QBM customer-specific or shared?
Every customer gets a dedicated QBM environment and database boundary. Customer data is never mixed with other customers.
Can QBM run in a cloud environment?
Yes. QBM can be deployed in a customer-specific cloud environment. The architecture stays the same: a separated QBM environment with a dedicated database boundary.
Can QBM run on a VPS or private hosted server?
Yes. QBM runs well on a VPS or private hosted server. This is typically the most cost-effective way to get a private, dedicated environment without buying on-premise hardware.
Can QBM still run on a local office server?
Yes. QBM supports on-premise deployment in a local business server environment. Many customers choose this when they need full local control, predictable local-network performance, or operational independence from external internet.
Who owns the QBM data?
Customers retain ownership of their business data in every deployment model. Backups, access policies, and data residency can be defined per environment.
Get the right QBM deployment for your business
Tell us about your users, branches, internet reliability, and IT setup. We will recommend cloud, private hosting, or on-premise - and the right edition, modules, and implementation scope to go with it.