Infrastructure

What the MarQi Cloud infrastructure layer covers

Infrastructure at MarQi Cloud is split into three engineering domains that are documented separately: the network fabric that carries traffic between zones and out to the internet, the storage architecture that keeps volumes and objects durable, and the compute platform that runs the virtual machines and bare metal hosts themselves. Each layer is built on open source software rather than proprietary appliances, which is what makes it possible to publish how it works instead of describing it in marketing terms.

Where the hardware lives

Production capacity runs from Zone1 in Alpharetta, Georgia, at 190 Bluegrass Valley Pkwy, inside the facility MarQi Cloud operates in partnership with Digital Ignition. Being in the north Atlanta metro rather than a distant hyperscaler region is the reason latency to businesses across Georgia and the wider Southeast stays low. Customers who want to place their own hardware in the same building use colocation and BYO hardware, and it lands on the same fabric as the cloud side.

How the layers fit together

A virtual machine created on the compute platform gets its disk from the storage cluster, its addressing and isolation from the network fabric, and its outbound path through the same Tier-1 connectivity used by colocation customers. That is what allows a single hybrid cloud VPC to contain both rented virtual machines and hardware a customer owns. Snapshots and backups, VPN and load balancing, and monitoring are part of the platform rather than separately metered add-ons, and there are no egress fees on traffic leaving the platform.

Reading further

If you are evaluating the platform, pricing shows what a VM costs and what is included, our zones describes the physical footprint, and getting started walks through provisioning. Engineering questions can go straight to the team at support@marqi.cloud or +1 770-369-9321.