Documentation
Getting Started, Networking, Snapshots
Step-by-step guides to launch VMs, connect with WireGuard, configure load balancers, and manage snapshots and backups.
What the documentation covers
The MarQi Cloud documentation is written for engineers who are provisioning and operating infrastructure rather than for a sales evaluation. It covers first provisioning steps, network and VPN setup, storage and volume handling, snapshot and backup workflows, and the operational tasks that come up once a workload is live.
Start here
If this is a new account, getting started is the shortest path from signup to a running virtual machine. From there, networking and VPN explains how to reach private resources, snapshots and backups covers restore points, and templates and images lists the operating system images available at provisioning time.
Platform reference
Documentation on how the platform itself is built lives alongside the product pages: compute platform for the KVM hypervisor layer, storage architecture for how volumes are replicated and where snapshots live, and network fabric for addressing, isolation and upstream connectivity. Because the stack is open source, these describe the actual components in use rather than a proprietary abstraction.
Longer form material
Deeper walkthroughs, architecture comparisons and migration write-ups are published on the engineering blog, which is organised by topic — storage, GPU and AI infrastructure, networking, cost, migration and compliance. If something you need is not documented yet, the engineering team answers directly at support@marqi.cloud.
Frequently asked questions
Where should a new account start?
Getting started is the shortest path from signup to a running virtual machine: create an account, pick a zone, launch a KVM instance, connect over WireGuard, then attach storage and turn on protection.
What does the documentation cover?
First provisioning steps, network and VPN setup, storage and volume handling, snapshot and backup workflows, and the operational tasks that come up once a workload is live. It is written for engineers operating infrastructure, not for a sales evaluation.
Where is the platform architecture documented?
Alongside the product pages: compute platform for the KVM hypervisor layer, storage architecture for how volumes are replicated and where snapshots live, and network fabric for addressing, isolation and upstream connectivity.
What if something is not documented yet?
Write to support@marqi.cloud and it reaches the engineering team directly. Longer walkthroughs, architecture comparisons and migration write-ups are published on the engineering blog, organised by topic.
Related engineering articles
- How Identity and Access Management Prevents Unauthorized Cloud Resource Access
- The IT Security Leader’s Guide to Cloud Compliance Frameworks
- How Encryption at Rest and in Transit Protects Sensitive Data in Cloud Environments
- Why Network Segmentation is the First Line of Defense in Cloud Security
- The Complete Guide to Cloud Firewall Configuration for Enterprise Security
- How to Implement a Zero-Trust Security Architecture on Cloud Infrastructure
- The Complete Guide to Cloud Cost Allocation Tags for Multi-Department Environments
- Why Daily Monitoring of Cloud Spending Prevents Cost Anomalies
Browse the full archive: Cloud Strategy & Buying Guides (25) · Cloud Infrastructure (218)