Solutions

Hybrid Cloud, Colocation, Private Circuits, GPUs

From hybrid deployments and colocation to GPUs for AI/ML, private circuits, and managed services - explore how MarQi Cloud fits your stack.

Solutions for every stage of scale

01

Place your hardware in the same zone as your KVM VMs. Keep everything on isolated networks with tagged VLANs/VXLAN. Scale compute elastically; keep specialized hardware close by.

02

Rack your hardware in our zones—air or liquid cooled. Connect to storage SANs, your virtual estate, and out to your own data centers.

03

Bring your own circuits or let us help provision. We’ll terminate links in your VPC for private point-to-point communication. Inter-zone traffic uses tier-1 providers only and is encrypted in transit.

04

A separate compute pool tailored for AI/ML training and inference. Pair with high-IOPS block storage and private circuits for data gravity and speed.

05

We embed an engineer to design, build, and run your environment. From cluster deployment to HA architecture, monitoring, backups, and upgrades.

06

Our software engineers build your application end-to-end and host it in MarQi Cloud. We default to distributed databases, distributed storage, and load-balanced, highly available deployments.

Solutions for every stage of scale

Choose the path that fits—from pure virtual compute to hybrid colocation and private circuits.
Ai3 How Icon1

One VPC. Virtual + physical.

Ai3 How Icon1

Your servers, our fabric.

Ai3 How Icon1

Private links between your DCs and ours

Ai3 How Icon1

Dedicated GPU clusters for AI

Ai3 How Icon1

White-glove from day zero

Ai3 How Icon1

Full-stack app builds on your cloud

Diagram of the MarQi Cloud platform: KVM compute orchestrated by Apache CloudStack, Ceph triple-replicated storage, tier-1 and private network connectivity, all in the Zone1 data center in Alpharetta, Georgia with 24/7 engineer operations.
Every layer of the platform in one view.

Choosing between them

Most customers arrive with one of four problems, and the right starting point follows from which one it is.

"Our cloud bill is unpredictable and we cannot move." The cost is usually egress and per-feature metering rather than compute. Start with hybrid cloud and pricing — the comparison that matters is the whole invoice, not the instance line.

"We own hardware with life left in it." Replacing it with rented capacity is rarely the cheapest answer. Rack it with us and connect it to the same VPC as your cloud instances — see colocation and BYO hardware.

"We need GPUs and the queue is long." Dedicated accelerators, close to your data, with no transfer charge on training sets — see GPUs for AI/ML.

"We do not want to staff this." Our engineers operate the estate end to end under managed services, and build on it under application development.

Where connectivity itself is the constraint — regulated traffic, latency-sensitive replication, committed throughput — the answer is dedicated: see private circuits and peering.

What every solution shares

Open source underneath, so the exit path exists on day one. No egress fees. Per-zone storage clusters with triple replication, documented under storage architecture. Private networking by default via VPC and WireGuard. Protection included rather than sold separately — snapshots and backups. And a NOC watching it 24/7, described under status and monitoring.

Not sure which fits? Talk to an engineer — we will map your current stack before recommending anything.

Frequently asked questions

Which MarQi Cloud solution fits my workload?

Hybrid cloud suits teams who already own hardware and want elastic compute beside it. Colocation suits teams who only need rack space, power and connectivity. GPUs for AI/ML is a separate compute pool for training and inference. Private circuits and peering suit workloads that need dedicated point-to-point links into a VPC.

What do all the solutions have in common?

All of them run on the same open source stack, in the same zones, on the same network fabric, with no egress fees and no vendor lock-in clause. Snapshots, backups, VPN, load balancing and monitoring are part of the platform rather than separately metered add-ons.

Can I combine more than one solution?

Yes, and most production setups do. Colocated hardware, KVM virtual machines and a GPU pool can sit in the same zone and the same VPC, with private circuits terminating into it. Because it is one fabric, moving a workload between those shapes does not require re-architecting the network.

Is there a contractual lock-in?

No. The platform is built on open source components — KVM instances, standard image formats, Ceph-based storage — so workloads can be moved off the platform without a rewrite, and there are no egress fees that penalise moving data out.

Related engineering articles

Browse the full archive: Cloud Strategy & Buying Guides (25) · Cloud Infrastructure (209)