Our Zones

A zone is a data center, not a label

Each MarQi Cloud zone is a physically separate facility running its own storage cluster and its own compute capacity. That is a deliberate design choice: it means data locality is real rather than nominal, and it means a cross-zone copy gives you genuine geographic separation rather than two copies in one building.

Zone 1 — Alpharetta, Georgia

Our primary zone is in Alpharetta, GA, inside the Atlanta metro, with sub-5ms latency across the metro area. For customers in Georgia and the wider Southeast that proximity is the practical argument: training data, database replicas and backup targets do not have to cross the country to reach compute. It is also where hardware racked under colocation and dedicated GPU capacity live.

How zones talk to each other

Inter-zone traffic rides tier-1 backbones rather than the public internet and is encrypted in transit — see network fabric. Because we do not charge egress, moving data between zones is not a metered event, which changes what is reasonable to do: cross-zone snapshot copies and second-site backup targets become architectural decisions rather than budget decisions. See snapshots and backups and pricing.

Choosing a zone

Put compute in the zone closest to whoever consumes it, and put your second copy somewhere else. Where regulation or a specific latency budget constrains the choice, our engineers will design around it — including dedicated connectivity between your sites and a zone, described under private circuits and peering.

The platform in each zone is the same: KVM compute, per-zone block storage with triple replication, and private VPC networking. Getting a first workload into a zone is walked through under getting started, or talk to an engineer.

Zone1 — Alpharetta, Georgia: our Atlanta-metro data center

Zone1 is MarQi Cloud’s own facility at 190 Bluegrass Valley Pkwy, Alpharetta, GA 30005 — inside the Atlanta metro area. It is not a reseller footprint in someone else’s hall: the racks, the storage cluster and the network fabric are operated by the same engineers who answer your support ticket. A second zone, Zone2, is planned.

Why a Southeast US data center changes your latency budget

For an application serving the Southeast US, physical distance is the part of latency you cannot optimise away in code. Serving Atlanta, Georgia and the wider Southeast from a facility in the same metro removes the long-haul segment entirely; for everything beyond it, private circuits and BGP peering over tier-1 carriers keep the path off the public internet. Distance sets the floor — routing decides how close you get to it.

Georgia data center, engineer-operated

Every zone is run on the same principle: open-source infrastructure (KVM, Apache CloudStack, Ceph), published unit pricing, no egress fees and no vendor lock-in. Hardware refreshes are an engineering decision made in-house, not a vendor ticket.