[ PLATFORM ]

A platform built around purpose.

Subnets define participation and policy. Capacity grows beyond the footprint of any single fleet.

01 The shift

A better place for the demanding part of the stack.

Most teams do not want a new infrastructure program. They want a better place to run the part of the stack that has become demanding to operate, coordinate, or scale.

Idyl organizes existing hardware into governed compute environments, so that demanding layer can move beyond one team's own machines without changing the operating model.

Idyl organizes existing hardware into governed compute environments.

02 Subnets

Subnets are the platform primitive.

A subnet gives an environment a defined governing party, a defined audience, and defined rules. That is how fragmented hardware becomes a governed compute domain instead of a generic machine list.

Governance

One governed domain.

The operator defines audience, rules, and operating policy. That keeps the environment coherent as it grows beyond the footprint of any single fleet.

Roles

Builders Build products, agents, and workloads through the subnet’s access model rather than managing the machine layer directly.
Operators Define the audience, policy, and rules that give the environment its shape.
Providers Contribute hardware under the subnet’s terms of participation, economics, and purpose.

OPERATOR · AUDIENCE · RULES · PARTICIPATION

03 Trust

Trust depends on clear operating boundaries.

Control-plane tenancy, workload isolation, access, and environment lifecycle are separate choices inside the same subnet model.

Sandbox environments.

Create bounded environments for experiments, previews, agents, customer workloads, and short-lived deployments.

EXPERIMENTS · PREVIEWS · AGENTS

Workload isolation.

Choose the runtime boundary for deployed code, from standard containers to microVM-backed isolation where stronger separation is needed.

CONTAINERS · MICROVM

Control-plane tenancy.

Run a subnet on shared Idyl control-plane infrastructure, or use a dedicated control-plane environment for stronger operational separation and reduced noisy-neighbour risk.

SHARED · DEDICATED

Controlled access.

Define who can deploy workloads, who can provide capacity, and which operating rules apply.

PUBLIC · PRIVATE · INVITE ONLY

04 Participation

Participation across many environments.

A subnet can grow across many capacity sources without losing its audience, access model, or operating policy.

Cloud

Cloud capacity can participate under the subnet’s admission, placement, and operating policy.

Data centers

Managed racks and clusters can add sustained capacity to the same governed environment.

GPU marketplaces

External GPU supply can participate through the same admission, runtime policy, and operating model.

Private infrastructure

Existing private fleets and institutional hardware can join while staying inside the subnet’s operating boundaries.

05 Where to go next

Choose your next path.

Explore the network surface, pricing model, technical material, or contact routes.