> ## Documentation Index
> Fetch the complete documentation index at: https://docs.idyl.network/llms.txt
> Use this file to discover all available pages before exploring further.

# What is IDYL?

> IDYL is a platform for running workloads on governed compute environments called subnets.

A subnet is an operating boundary for compute. It has an operator, an intended audience, and rules for who can deploy workloads, what can run there, and how capacity can be added.

Builders use IDYL to deploy applications without managing machines directly. Operators create and manage subnets. Providers add compute capacity to subnets that match their resources and participation requirements.

IDYL is useful when a workload needs more capacity, clearer operating boundaries, or more flexible participation than a single fleet of machines can provide.

## How people use IDYL

<Columns cols={2}>
  <Card title="Build" href="/build">
    Deploy and manage applications and jobs on IDYL.
  </Card>

  <Card title="Operate" href="/operate">
    Create and manage subnets for a workload, team, institution, or customer base.
  </Card>

  <Card title="Provide" href="/provide">
    Add compute capacity to subnets that match your resources and participation requirements.
  </Card>

  <Card title="Resources" href="/resources">
    Learn the IDYL resource model, including applications, workloads, subnets, and namespaces.
  </Card>
</Columns>

## Core ideas

| Concept            | Meaning                                                                                             |
| ------------------ | --------------------------------------------------------------------------------------------------- |
| Subnet             | An operating boundary where workloads run.                                                          |
| Application        | Software that you run on IDYL.                                                                      |
| Workload           | A runnable unit managed by IDYL.                                                                    |
| Sandbox            | A temporary environment for previews, agents, experiments, demos, or customer-specific deployments. |
| Workload isolation | The runtime boundary for a workload, from standard container execution to microVM-backed execution. |
| Namespace          | A way to organize related resources.                                                                |

## Start here

Use [Getting started](/) to install the CLI, authenticate, and choose a workflow.