Commercial model
Three billing lines. No module sprawl.
Buyers should be able to quote VexylCloud fast. The commercial model follows the workload dimensions that actually move MSP cost: managed devices, mailbox-based SaaS backup, and hosted backup storage when you use it. The rest of the product surface stays inside that same model instead of turning into new module lines every time you widen the rollout.
Quote it in three numbers
Managed devices
$1.49
- 1-249 devices: $1.49
- 250-999 devices: $1.19
- 1000-4999 devices: $0.99
- 5000+ devices: $0.79
SaaS Backup
$1.00
- Microsoft 365 and Google Workspace backup
- Mail, OneDrive or Google Drive, Teams, SharePoint, Shared Drives, contacts, and calendars included
- No separate per-site or per-drive line item
Hosted backup storage
$15
- Only applies when you use VexylCloud-hosted backup storage
- Forecasted in clean 1 TB buckets
- Kept separate from mailbox licensing
Compact coverage matrix
| Product surface | Device line | Mailbox line | Hosted storage line |
|---|---|---|---|
| RMM, PSA, documentation, vault, cloud, and AI workflows | Included | Not separately billed | Only if backup storage is used |
| Microsoft 365 and Google Workspace SaaS backup | Not separately billed | Included | Only if backup storage is used |
| Endpoint and server backup operations | Included | Not separately billed | Only if backup storage is used |
That covers RMM, PSA, documentation, vault, cloud, and AI workflow coverage without turning every adjacent product surface into another contract line.
The mailbox line carries the wider SaaS collaboration protection story instead of fragmenting into extra workload-based pricing.
Storage remains visible as its own number, so backup economics stay easy to explain to owners and finance reviewers.
Devices, protected mailboxes, and storage make it easier to sanity-check spend without another module spreadsheet.
The model does not get rebuilt every time rollout widens into PSA, IAM, docs, vault, cloud, or AI workflows.
Hosted backup storage remains visible as its own number instead of being buried inside a wider licensing story.
Illustrative monthly math
2,000 devices plus 1,500 mailboxes lands at about $3,754.50 / month.
That is the kind of quote buyers can sanity-check quickly: count devices, count protected mailboxes, then decide whether hosted backup storage is part of the plan.
What stays inside
You do not re-buy the platform every time rollout widens.
- RMM, PSA workflows, remote actions, patching, and service coordination stay inside the device-driven core.
- IAM, site documentation, credentials, vault, and customer records do not create a new pricing structure.
- Cloud actions, approvals, and governed AI workflows remain part of the same wider commercial story.
Example MSP scenarios
Lean MSP
250 devices + 150 mailboxes
Useful when a smaller team wants the core commercial model in one fast number.
- Devices at current public tier: about $297.50 / month
- Mailbox protection: about $150 / month
- Total before hosted storage: about $447.50 / month
Growth MSP
2,000 devices + 1,500 mailboxes
This is the same modeled footprint used across the homepage and comparison page.
- Illustrative public-model total: about $3,754.50 / month
- No extra pricing layer for PSA, IAM, docs, vault, cloud, or AI
- Good fit when the stack conversation is already commercial as well as operational
Backup-heavy rollout
2,000 devices + 1,500 mailboxes + 8 TB storage
Use this model if you expect to keep hosted backup storage in the same commercial view.
- Base public-model total: about $3,754.50 / month
- Hosted storage: about $120 / month
- Total with 8 TB hosted storage: about $3,874.50 / month
Software-cost framing only: The public pricing model covers product spend only. It does not include the softer gain from less tool switching, simpler administration, faster technician execution, or less handoff loss across disconnected systems.
What buyers usually need answered before they move
What changes the bill?
Device count, protected mailbox count, and hosted storage use are the main commercial inputs. That keeps the model tied to real workload volume.
Can rollout start small?
Yes. Teams can start with the surface that hurts first, then widen into backup, admin, vault, cloud, and AI without rebuilding the pricing structure.
How do we sanity-check the math?
Count devices, count protected mailboxes, decide whether hosted backup storage is part of the plan, then compare that against today’s fragmented contracts.
Need pricing mapped to your environment?
Share device count, mailbox count, and expected storage footprint. We can map the commercial model against your real MSP operating volume and the stack you are already paying for.