Launch a subnet on idyl. Define who provides compute, who deploys workloads, and how the network grows.
Vision
Every subnet begins with a reason to exist. The mission attracts the people. The people bring the compute.
Solve problems that matter.
Launch a subnet around a scientific mission. People join because they believe in the work. They contribute GPUs. You run experiments at global scale.
Turn users into infrastructure.
Build a product on a subnet. Your community contributes the compute that runs it. Usage becomes supply. Your plan stretches further as adoption grows.
Own your compute layer.
Create a private subnet for your team. Control who joins, what runs, and how it scales. Cloud-grade reliability on your own terms.
Control
You decide everything. Who provides compute. Who deploys workloads. What the network exists to do. Total control, zero ambiguity.
Open to anyone, or invite-only. Require verification. Set hardware minimums. Your subnet, your rules.
Let the world deploy, or restrict to your team. Control access at the subnet level. No surprises.
Define the purpose. Shape the culture. The mission is what attracts the right people and repels the wrong ones.
Growth
More demand attracts more providers. More providers increase capacity. More capacity means your plan goes further. More people join. The cycle compounds.
Real workloads attract real providers. Your subnet doesn't need to buy compute — it earns it through usage.
The people who care about your mission bring the machines. Your community isn't just using the product — they're powering it.
As supply grows, each plan buys more compute. At scale, the network that powers your product is funded by the people who use it. That changes everything.
Platform
Operators don't rent infrastructure. They build it. The network gives you the tools to create something that outlasts any single cloud provider.
Launch on shared global compute. No approval process to get started. Your subnet goes live and providers can join immediately.
Lock it down. Verified providers only. Restricted deployments. Full isolation. The boundary is yours to draw.
GPUs, CPUs, ARM, x86, edge, cloud. The network treats all hardware as capacity. Use what fits the work.
You're not building on rented land. You're building a network that belongs to its community. That's how you change things.