MPM·VDC

Data center

Pods built for a workload, not an instance size

A pod is a defined layout: compute sized to the application, an isolated storage volume, a Vault backup policy, and a runbook that says how to restart, patch and restore it. You pick the workload; the sizing conversation happens once, with an engineer.

Scope a pod

Pricing tiers

Entry pod

starting at$79/mo

Sites, apps and media platforms that need real isolation and real backups.

Web Hosting · Media & Podcast Hosting

  • Dedicated VM on enterprise hardware
  • NVMe storage, ECC memory
  • Daily Vault backup included
  • Documented runbook
  • Response commitment with a named engineer

Business pod

starting at$199/mo

Line-of-business workloads where an outage stops work or stops revenue.

Sage 300 · Client-Server · E-commerce · Distributed

  • Multi-VM layout sized to the workload
  • Separated application and database tiers
  • Tightened backup interval with verified restores
  • Migration from VMware or physical included
  • Runbook plus quarterly review with the engineer who built it

Starting prices. Final sizing and price are quoted after a scoping call.

The six pods

Sage 300 Hosting

sage-300

Business pod

Sage 300 and its SQL back end, sized for concurrent users rather than raw core count. Built for accounting teams that need the application responsive at month-end close, not just available.

  • Dedicated application and database VMs
  • NVMe-backed storage tier
  • Nightly Vault backup with retention policy
  • Documented runbook for restart, patch and restore

Client-Server Hosting

client-server

Business pod

The line-of-business server you still run on-prem — file, print, application or database — lifted into the data center with the same access model your users already have.

  • Isolated tenant server with dedicated resources
  • Site-to-site or per-user secure access
  • Vault backup policy matched to the workload
  • Migration from physical or VMware included

Web Hosting

web-hosting

Entry pod

Marketing sites, CMS installs and small applications on a managed pod instead of shared hosting — with real isolation, real backups and someone who answers when it breaks.

  • Managed web stack on a dedicated VM
  • TLS, DNS and deploy assistance
  • Daily Vault backup
  • Runbook for rollback and restore

E-commerce Hosting

ecommerce

Business pod

Storefronts where downtime is lost revenue. Sized for checkout traffic, with a backup policy that assumes you will one day need to restore mid-day, not overnight.

  • Storefront and database separation
  • NVMe storage, ECC memory, dedicated metal
  • Tightened backup interval with verified restores
  • Migration and cutover planning

Media & Podcast Hosting

podcast

Entry pod

Media libraries and publishing platforms where storage grows steadily and bandwidth matters more than CPU. Capacity is planned with you rather than metered by surprise.

  • Capacity-oriented storage tier
  • Publishing platform hosting
  • Daily Vault backup of media and metadata
  • Growth planning reviewed with you

Distributed Applications

distributed

Business pod

Applications that expect more than one machine — an app tier, a database tier, a worker tier — laid out as a set of pods with a defined internal network between them.

  • Multiple coordinated VMs on a defined internal network
  • Per-tier sizing and storage policy
  • Vault backup policy per tier
  • Runbook covering start order and dependencies

Architecture

One dedicated host running Proxmox VE, isolated pods, an NVMe storage tier, and a separate Proxmox Backup Server datastore. This is the current buildout — not a target-state diagram.

MPM VDC single-node architectureCustomer sites and users connect over an encrypted path to a single Proxmox host on dedicated enterprise hardware. The host runs purpose-built customer pods on an NVMe storage tier, and backups are written to a separate Proxmox Backup Server datastore.YOUR ENVIRONMENTOn-prem serversOther cloudsWorkstationsLaptopsencrypted pathSINGLE DEDICATED HOST · PROXMOX VEenterprise hardware · ECC memory · NVMeCUSTOMER PODSsage-300web-hostingclient-serverecommercepodcastdistributedSTORAGE TIERNVMe · internal, not a podper-pod volumes, isolatedVAULT · PBSProxmox BackupServer datastoreseparate fromproduction volumesdeduplicated,encrypted, verifiedDR TIERcross-site replicationoffered at the DR tier
Current buildout: one dedicated host. No cluster, no multi-site claim — the diagram shows what runs today.

Compared with the alternatives

MPM VDC compared with a commodity VPS host and a do-it-yourself in-house build
What you getMPM VDCPurpose-built pod (compute + storage + backup + SLA + runbook)Commodity VPS hostA raw VM, you configure everythingDIY / in-houseHardware you buy, rack, and maintain
Operated byMPM VDCFormer bank data center managerCommodity VPS hostSupport tier reading scriptsDIY / in-houseYour own staff's spare time
Backup & DRMPM VDCVault, three tiers, verified restoresCommodity VPS hostUsually add-on or noneDIY / in-houseWhatever you build yourself
LicensingMPM VDCNo per-core fees (open-source stack)Commodity VPS hostVariesDIY / in-houseVMware/Windows licensing on you
Migration helpMPM VDCIncluded (VMware/physical → pod)Commodity VPS hostSelf-serviceDIY / in-houseN/A
SupportMPM VDCTalk to the engineer who built itCommodity VPS hostTicket queueDIY / in-houseYou are the support
Talk to an engineer