> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/learn-the-platform/module-1-architecture-fundamentals/01-architecture.md).

# Overview

Understand the VergeOS platform architecture, deployment models, storage, networking, and cluster concepts.

## Learning Objectives

By the end of this module, you will be able to:

* **Describe what VergeOS is** and how its unified operating system approach differs from traditional 3-tier infrastructure and other HCI platforms
* **Compare HCI and UCI deployment models** and recommend the right topology for a given use case
* **Explain VergeFS (vSAN) storage** including tier architecture, data distribution, and redundancy mechanisms
* **Describe the core fabric network** and how inter-node communication, vSAN replication, and VM live migration traffic flow
* **Identify VergeOS node types and cluster concepts** including controller nodes, scale-out nodes, compute-only, and storage-only roles

## Prerequisites

None -- this is the first module in the training program. No prior VergeOS experience is required.

## Estimated Time

**2 hours** (1.5 hours reading + 0.5 hours lab)

## Topics

* [**What is VergeOS?**](/learn-the-platform/module-1-architecture-fundamentals/01-vergeos-overview.md) — The unified ultraconverged operating system: VergeHV (compute), VergeFS (storage), and VergeFabric (networking) in a single platform. How it compares to VMware, Nutanix, and traditional infrastructure.
* [**HCI vs UCI**](/learn-the-platform/module-1-architecture-fundamentals/02-hci-vs-uci.md) — Two deployment models for different scaling needs. Hyperconverged (HCI) scales compute and storage together; Ultra Converged (UCI) scales them independently with specialized node types.
* [**vSAN & VergeFS Storage**](/learn-the-platform/module-1-architecture-fundamentals/03-vsan-vergefs.md) — Software-defined distributed storage with tiered drives (Tier 0 for metadata, Tiers 1–5 for workload data), global deduplication, and self-healing redundancy.
* [**Core Fabric & Networking**](/learn-the-platform/module-1-architecture-fundamentals/04-core-fabric.md) — The private inter-node mesh that carries vSAN replication, cluster coordination, and live migration traffic. Dual-switch redundancy and jumbo frame requirements.
* [**Clusters & Node Types**](/learn-the-platform/module-1-architecture-fundamentals/05-clusters-nodes.md) — How VergeOS organizes nodes into clusters with distinct roles: controller, scale-out, compute-only, and storage-only.
* [**Lab: Explore the Architecture**](/learn-the-platform/module-1-architecture-fundamentals/lab.md) — Hands-on exploration of the VergeOS Terraform playground to trace deployment topologies, examine infrastructure-as-code patterns, and design a deployment for a customer scenario.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/learn-the-platform/module-1-architecture-fundamentals/01-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.