---
sidebar_position: 2
---

# VDC Use Cases

Virtual Data Centers give you flexible building blocks for many types of workloads. This page highlights some of the most relevant patterns.

## 1. Enterprise Kubernetes

Run production workloads with full control and no hyperscaler lock‑in:

- Multi‑service applications and APIs.  
- Internal tools, back‑office systems, and shared services.  
- Microservice architectures using standard Kubernetes, Helm, and operators.  
- Policy‑driven placement to keep data in specific regions or jurisdictions.

**Why use a VDC here?**

- Control over where clusters run and how they’re connected.  
- Encrypted overlay networking via Mycelium instead of exposed public IPs.  
- Compatibility with existing Kubernetes tooling and CI/CD chains.

## 2. AI & Machine Learning

Run training and inference close to your data while keeping it private.

- GPU‑accelerated training on dedicated clusters.  
- Model serving endpoints behind Mycelium Network.  
- Pipelines that combine **QSFS** (quantum‑safe storage) with compute.  
- Future‑ready environments for **Mycelium Agents**.

**Key benefits**

- Data stays on hardware you or your partners select.  
- Secure east‑west traffic via Mycelium overlays.  
- Ability to burst across multiple nodes or sites.

## 3. Edge & IoT

Leverage the grid’s geographic spread to deploy workloads closer to users, sensors, and devices.

- Run latency‑sensitive services near where events occur.  
- Ingest, process, and filter data at the edge before sending summaries upstream.  
- Coordinate fleets of devices and gateways over Mycelium Network.

**Examples**

- Local analytics near industrial sites.  
- Regional micro‑datacenters serving communities or campuses.  
- Smart‑city workloads combining many distributed nodes.

## 4. Personal & Team Clouds

VDCs can back **personal sovereign environments** where your apps and data live entirely on infrastructure you choose.

- Self‑hosted collaboration suites (documents, chat, mail, files).  
- Private developer environments and CI runners.  
- Long‑term personal archives on QSFS.

The **Digital Me** blueprint (see below) is one concrete example of this pattern.

## 5. Hybrid & Migration Scenarios

Move workloads from traditional cloud or on‑prem into a VDC, or straddle both worlds.

- Gradual migration from centralized providers.  
- Burst or spill‑over capacity into the grid.  
- Disaster‑recovery clusters that can be spun up on demand.

## Example: Digital Me on Mycelium

The *Digital Me* concept shows what a personal sovereign cloud workspace can look like:

- **Cryptpad** – Encrypted document collaboration.  
- **Elements (Matrix)** – Secure chat and communication.  
- **Stallwart** – Mail, calendar, and contacts.  
- **Gitea** – Git hosting and code collaboration.  
- **Nextcloud** – File storage and sync.  
- **LiveKit / Jitsi** – Video conferencing integrated with chat / files.  
- **SSO** (future) – Single Sign‑On across the stack.

All of this can be orchestrated inside a VDC and surfaced via Mycelium networking.

---

## Related Documentation

- **[VDC Overview](/vdc)** – Concepts and architecture.  
- **[Blueprints & Example Environments](/vdc/blueprints)** – How to assemble real‑world stacks.  
- **[Mycelium Cloud for Developers](/cloud/for-developers)** – Deeper dive into the underlying platform.