
What is included in every plan
Every MarQi Cloud plan includes the things other providers meter: a VPN and load balancer, snapshots and backups, enterprise SSD block storage, and 24/7 monitoring by our NOC. They are part of the plan because a virtual machine you cannot reach privately, cannot restore, and nobody is watching is not actually a service.
No egress fees — and why that matters more than the hourly rate
We do not charge for data leaving the platform. On a small workload that is a rounding difference. On anything that moves real volume — backups to another site, analytics exports, media delivery, AI training data, or simply leaving for another provider — egress is routinely the largest single line on a cloud invoice, and it is the line that grows fastest as you succeed. Removing it changes the shape of the bill, not just the size.
It also removes the exit tax. Combined with an open source stack and standard machine images, nothing about our pricing is designed to make leaving expensive.
Storage pricing
Block storage is billed on capacity. IOPS are not sold as a separate provisioned tier, snapshot storage is not priced at a premium, and inter-zone copies are not charged as transfer. The architecture behind it — dedicated per-zone Ceph/PetaSAN clusters with triple replication — is described under storage architecture.
Comparing a quote properly
When you put our figure next to a hyperscaler's, compare the whole invoice rather than the instance line. Add provisioned IOPS, snapshot storage, load balancer hours, VPN gateway hours, monitoring, support tier, and projected egress. In our experience that exercise moves the comparison substantially, and it is the only version of the comparison that predicts what you will actually pay.
Custom builds
Standard plans cover most workloads. When they do not — unusual memory ratios, dedicated GPU capacity, large storage footprints, colocated hardware alongside virtual capacity, or dedicated circuits — we quote the build rather than making you fit a tier. Engineers price it, not a configurator.
Operated for you
If you would rather not staff an on-call rotation, our engineers can run the whole estate under managed services. And whichever way you buy, the platform underneath is the same: compute, network and storage described openly rather than abstracted behind a brand name.
Not sure which plan fits? Getting started walks through a first deployment, or talk to an engineer and we will size it with you.
Published unit prices
| Resource | Unit price | Billed on |
|---|---|---|
| vCPU | USD 2.00 per vCPU / month | Provisioned |
| Memory | USD 2.00 per GB RAM / month | Provisioned |
| Block storage | USD 0.13 per GB / month | Provisioned capacity, triple replicated |
| Snapshots | Included in volume capacity | No separate snapshot tier |
| Provisioned IOPS | Not sold separately | Performance comes from the NVMe tier, not a paid add-on |
| Egress / data transfer out | USD 0.00 | Not metered |
| Entry instance | From USD 8.00 / month | Smallest published configuration |
Worked example: a 1 TB block volume is 1024 × USD 0.13 = USD 133.12 per month, replicated three times, with snapshots and egress included. GPU and colocation configurations are quoted per deployment — contact us with the shape you need.
Frequently asked questions
Does MarQi Cloud charge egress fees?
No. Data leaving the platform, moving between zones, or returning to your own hardware is not charged. Egress is often the largest line on a cloud invoice, so removing it changes the shape of the bill rather than just its size.
What is included in every plan?
Every plan includes a VPN and load balancer, snapshots and backups, enterprise SSD block storage, and 24/7 monitoring by our NOC. They are part of the plan rather than metered add-ons.
How is block storage priced?
Block storage is billed on capacity. IOPS are not sold as a separate provisioned tier, snapshot storage is not priced at a premium, and inter-zone copies are not charged as transfer.
Are custom builds available?
Yes. Unusual memory ratios, dedicated GPU capacity, large storage footprints, colocated hardware alongside virtual capacity, and dedicated circuits are quoted as a build by engineers rather than fitted to a tier.
Related engineering articles
- Why Cloud Cost Transparency Tools Empower Teams to Control Spending
- The Complete Guide to Cloud Cost Forecasting and Budget Planning
- Why Egress Fee Elimination Transforms Cloud Architecture Economics
- How Right-Sizing Cloud Resources Cuts Infrastructure Spending by 40%
- Why Reserved Instances and Committed Use Plans Can Waste Money
- The Complete Guide to Cloud Cost Optimization Strategies for Enterprise IT Budgets
- How to Build a Cost-Effective Cloud Infrastructure Without Sacrificing Performance
- Why Private Cloud TCO Analysis Favors Dedicated Over Shared Public Cloud
Browse the full archive: Cloud Cost & Pricing (91)
