
What hybrid actually has to solve
Hybrid cloud is usually sold as a migration story, but most teams reach for it because of a constraint that will not move: hardware still inside its depreciation window, a database that is not going anywhere this year, a compliance boundary, or a latency budget that a distant region cannot meet. The job of a hybrid platform is not to replace those things — it is to put elastic capacity next to them without a rewrite.
How MarQi Cloud connects the two halves
Your existing environment reaches Zone1 in one of three ways. A WireGuard tunnel over your current circuits is included with every plan and takes minutes to stand up. A dedicated private circuit with BGP peering removes the public internet from the path entirely when latency has to be predictable. And if the hardware itself moves into Zone1 colocation, the hybrid link stops being a wide-area link at all — your racks sit beside the managed cloud in the same building.
What runs on the MarQi side
Apache CloudStack orchestrates KVM compute, and Ceph and PetaSAN provide block, object and shared file storage with triple replication. Every layer is open source, so the platform you build against is one you could run yourself — the exit path is a migration, not a rewrite. There is no per-gigabyte egress charge, so moving data back towards your own hardware does not generate a bill.
Where the line sits
We operate the hypervisor, the hosts, the storage cluster and the network fabric, 24/7, from the same building the hardware is in. You keep your operating systems, your data and your application stack. That boundary is deliberate: it is the one that lets you leave.
Hosted private cloud vs. private cloud hosting — what you actually get
The two phrases are used interchangeably in the market, and they should not be. “Private cloud hosting” usually means dedicated capacity you still administer yourself. A hosted private cloud means somebody else operates the control plane, the storage cluster and the hardware lifecycle for you. MarQi Cloud is the second: an engineer-operated private cloud on dedicated resources, with the orchestration layer run for you.
| What you compare | Self-managed private cloud | MarQi hosted private cloud |
|---|---|---|
| Hardware lifecycle | You buy, rack and refresh | Operated by MarQi in Zone1 |
| Control plane | You install and patch it | Apache CloudStack, operated for you |
| Storage layer | You design and tune it | Ceph-based, triple replicated |
| Egress billing | Depends on transit contract | No egress fees |
| Exit path | Yours by definition | Open-source stack — no proprietary lock-in |
OpenStack, CloudStack and the lock-in question
People searching for an OpenStack private cloud are usually asking a different question underneath: can I leave? MarQi Cloud runs Apache CloudStack on KVM rather than OpenStack. Both are open source and both answer that question the same way — your workloads run on standard KVM guests and standard block storage, so there is no proprietary instance format to unwind. CloudStack is the lighter of the two to operate reliably at a single-operator scale, which is why it is what we run.
Atlanta private cloud: where your workloads physically sit
Private cloud is only meaningfully “private” if you know where it is. MarQi Cloud workloads run in Zone1, Alpharetta, Georgia — Atlanta metro — in a facility we operate, with an option to place your own hardware in the same building through colocation.
Service levels and credits
Availability for the hybrid cloud platform is committed per service, not as a single blended figure across an account. Compute, block storage, network and connectivity, VPN and load balancing, and colocation power and space are each covered separately. Availability is calculated per calendar month as the percentage of minutes during which the service was available, and an unavailability period starts at the earlier of our monitoring detecting it or you opening a ticket.
When we miss a commitment the remedy is a tiered service credit against the affected service. The specific commitment that applies to your services is stated in your order or agreement with us; if you are evaluating us and need the figures before you sign, ask an engineer and we will put them in writing. The full framework — covered services, how availability is measured, exclusions and the credit mechanism — is published in our Service Level Agreement.
Frequently asked questions
What is hybrid cloud and when does it make sense?
Hybrid cloud runs part of a workload on infrastructure you control and part on a provider's platform, joined by a private network path. It makes sense when something cannot move - hardware still inside its useful life, a database with a hard latency budget, or a compliance boundary - but you still need elastic capacity beside it. MarQi Cloud connects the two halves with WireGuard tunnels, dedicated private circuits with BGP peering, or by taking your hardware into Zone1 colocation so the link is inside one building.
How does MarQi Cloud connect my existing data center to the cloud?
Three ways. A WireGuard site-to-site tunnel over your existing circuits is included with every plan and deploys in minutes. A dedicated private circuit with BGP peering gives predictable latency and keeps traffic off the public internet. Colocating your hardware in Zone1 removes the wide-area link altogether, because your racks and the managed cloud share the same fabric.
Does hybrid cloud lock me into MarQi Cloud?
The platform is Apache CloudStack orchestrating KVM, with Ceph and PetaSAN for storage - all open source, all runnable in your own data center. There is no per-gigabyte egress fee, so exporting your data does not carry a penalty. The portability test is whether you can export the data, run the stack elsewhere and read the format; the answer is yes on all three.
Who operates what in a MarQi Cloud hybrid deployment?
MarQi Cloud engineers operate the hypervisor, the compute hosts, the storage cluster and the network fabric, 24 hours a day, from the Zone1 facility in Alpharetta, Georgia. You keep your operating systems, your data and your application stack. That boundary is what keeps the platform exitable.
Related engineering articles
- Future-Proof Your Network: The Essential Guide to IPv6 Adoption in Cloud Infrastructure
- The Complete Guide to Cloud DNS Architecture for High-Availability Applications
- Why Redundant Network Paths Are Essential for Enterprise Cloud Availability
- Ultimate Guide: How Cloud Network Monitoring Tools Identify Latency and Throughput Issues
- The Complete Guide to Cloud VPN Architecture for Secure Remote Access
- How Virtual Private Cloud Networks Secure Business Workloads
- The Complete Guide to Software-Defined Networking in Enterprise Cloud Environments
- Why Cloud Network Architecture Is as Crucial as Compute and Storage Decisions
Browse the full archive: Hybrid Cloud (111) · Cloud Infrastructure (277)
