01
Start with a subnet
Your account starts in its own governed compute domain, ready for nodes, policies, and workloads.
idyl signup
[ Idyl ]
The Open Compute Network.
Idyl organizes existing hardware into governed compute domains that coordinate at internet scale. These domains are called subnets.
01 The network
Organized compute at planetary scale.
02 Your subnet
Your own governed compute domain, from day one.
Every account begins inside its own subnet: a governed compute domain where you can attach machines, deploy workloads, and scale without managing the infrastructure underneath.
02
Attach nodes
Connect Docker hosts, Kubernetes clusters, GPU nodes, private infrastructure, or rented capacity.
idyl node start
03
Deploy workloads
Deploy containers and scale replicas across the nodes in your subnet using a Kubernetes-like workflow.
idyl deploy
03 Control plane
Each subnet defines the operational boundary for its data plane.
IDYL coordinates the subnet while the operator keeps the data-plane boundary explicit for residency, sovereignty, private deployment, HIPAA, SOC 2, audit, and isolation requirements.
Control plane
IDYL control plane
IDYL coordinates identity, policy, scheduling, capacity, and usage across the subnet.
Data plane
Your data plane
The subnet operator chooses the machines, providers, regions, runtime policy, and controls underneath each workload, including when stronger workload isolation is required.
Compliance
Your rules
HIPAA, SOC 2, residency, workload isolation, and audit requirements are defined by the subnet operator and enforced in the data plane.
04 The primitive
A subnet has three defining properties.
Governance
A subnet has a defined operator, a defined audience, and defined rules for participation, placement, and runtime isolation. That is what gives the environment its shape.
OPERATOR · AUDIENCE · RUNTIME POLICY
Participation
Compute can join from cloud capacity, data centers, GPU marketplaces, and private infrastructure under one subnet's terms of participation.
CLOUD · DATA CENTERS · GPU MARKETS
Scale
The model is built so one governed domain can coordinate compute across a vast participation surface in real time.
SUBNET SCOPE · REAL-TIME COORDINATION
05 Products and subnets
Products on Idyl.
Products are the public services and tools built on Idyl. Subnets are the governed compute domains underneath them.
idyl.inference
One endpoint for open-source models on Idyl. OpenAI-compatible and operated as a public service.
VIEW PRODUCTidyl.transcode
An early-access media product for browser-based transcoding on the idyl.transcode subnet.
VIEW PRODUCTYour product.
Build on the same network surface. Explore what is already taking shape on Idyl, then build your own.
START BUILDING 06 Operating model
Three roles. One network.
Idyl is organized around builders, operators, and providers. Each works at a different layer of the same coordinated compute model.
Builders
Build products, agents, and workloads without taking on the machine layer directly. Inference, training, media processing, simulation, or batch.
Operators
Create and govern subnets with clear rules around participation, policy, and workload access.
Providers
Contribute existing hardware into environments that match their economics and purpose.
07 Sandboxes
Create sandboxes for experiments, previews, and agents.
Create temporary environments for experiments, previews, agents, customer workloads, and short-lived deployments.
Each sandbox environment runs under explicit rules for identity, access, placement, capacity, runtime policy, and lifecycle.
08 Research
Built for research shaped by compute.
Some work is not limited first by ideas. It is limited by access to enough compute, enough coordination, and clear enough operating rules to work beyond one institution’s own machines.
Idyl makes it possible to assemble governed environments around research programs, scientific institutions, and public-interest work through a control plane built to coordinate workloads at internet scale.
Research access is available for scientific, medical, and other public-interest work.
09 Shared or dedicated
Choose the control-plane environment that fits the job.
Run a subnet on shared Idyl control-plane infrastructure, or use a dedicated control-plane environment when you need stronger operational separation, predictable performance, or tighter access control.
Shared control planes.
A faster path onto shared Idyl control-plane infrastructure for workloads that fit an operator-managed environment.
SHARED · CONTROL PLANE
Dedicated control planes.
A dedicated control-plane environment for workloads that require stronger operational separation, network control, or a more private operating model.
DEDICATED · CONTROL PLANE
Built for work that needs more than one source of compute.
Idyl gives compute-heavy products, research programs, and institutions a way to keep growing capacity, coordination, and operating clarity beyond their own machines.
10 Where to go next
Built for work shaped by compute.
Routes into the platform, organized around the work you need to do next.
Subnets
See how subnets organize compute around participation, policy, and growth across many sources.
Explore
Browse products and subnets running on the network.
Pricing
See how budgets, bursts, and dedicated control-plane environments fit together.
Contact
Reach the right path for product, enterprise, research access, and company questions.
Trust & security
See how private compute, operating boundaries, and subnet governance fit together.
Documentation
Technical docs, quickstarts, and implementation detail.