io.net

About io.net (IO)

What Is io.net (IO)?

io.net is a decentralized computing network that pools GPUs and CPUs from independent data centers, crypto mining farms and individual hardware owners, then rents that capacity out to machine learning engineers and other compute buyers. Buyers deploy distributed clusters through a product called IO Cloud, hardware owners connect machines through IO Worker, and bookings, payments and treasury activity settle on Solana. The project describes itself as a way to reach scalable distributed clusters at a small fraction of the cost of comparable centralized cloud services. IO is the network's native coin and the unit all payments are ultimately converted into.

Official resources:

• Website: https://io.net
• Documentation: https://io.net/docs
• Token economics: https://io.net/docs/guides/coin/io-tokenomics
• Proof of Work verification: https://io.net/docs/guides/workers/proof-of-work
• X account: https://x.com/ionet

Who Founded io.net? (History)

io.net was co-founded by Ahmad Shadid and Tory Green. The company's own documentation describes an unusual origin: before June 2022 the team was building institutional-grade quantitative trading systems for the US stock market and for crypto, running near high frequency strategies that had to monitor tick data for more than 1,000 stocks and 150 cryptocurrencies while serving over 30,000 client accounts. Building that backend led the team to Ray, the open source distributed computing library, which the documentation says cut its infrastructure build time from more than six months to under 60 days. The remaining obstacle was cost. The docs cite NVIDIA A100 capacity priced at over 80 US dollars per card per day from on demand cloud providers, which put a serious bill in front of a self funded team. That cost problem is what the network was built to attack.

Ahmad Shadid stepped down as chief executive in June 2024, days before the IO token launch, and Tory Green, the co-founder and then chief operating officer, took over as chief executive.

How io.net Works

Supply comes from operators who attach hardware to the network through IO Worker. Demand comes from users who configure and deploy GPU or CPU clusters through IO Cloud, then run jobs on them using familiar tooling such as Jupyter Notebook and Visual Studio Code, with Ray handling distribution of the workload across workers.

Two networking layers make geographically scattered consumer and data center hardware usable as a cluster. IO Tunnels uses reverse tunnels to reach machines sitting behind firewalls and NAT. IO Network applies mesh VPN techniques so that nodes in a cluster can address each other reliably. Orchestration is handled with standard infrastructure tooling including Kubernetes, Prefect and Apache Airflow.

Because suppliers are anonymous and self reported, the network runs an hourly Proof of Work check against connected devices. The challenge is a hash puzzle in the style used by Bitcoin and by Ethereum before its Proof of Stake upgrade, combined with a check that the device actually has the VRAM it claims. The documentation states the process is intended to occupy no more than about 15 minutes per hour on a device, and that hardware which is not fully available while listed may be disqualified from rewards and from being hired.

Financial flows moved on chain with a system the project calls TNE On Chain, built on Solana. Bookings, payments, refunds and IO repurchases are recorded on chain, and funds are held in escrow by smart contracts during a cluster reservation.

Key Ecosystem Components

• IO Cloud, the buyer facing portal for creating, configuring, deploying and monitoring GPU and CPU clusters, including bare metal and Kubernetes clusters.
• IO Worker, the supplier portal covering device onboarding, real time earnings, utilization and fault monitoring.
• IO Explorer, a public statistics layer with pages for workers, clusters, inferences, block rewards, staking and a network map showing where hardware sits geographically.
• IO ID, a unified account dashboard covering usage, credits, billing, deployed clusters and IO Intelligence plans.
• Confidential compute attestation, which uses Trusted Execution Environments and GPU verification for workloads that need hardware backed guarantees.

IO Token Utility

IO is the settlement asset of the network. Buyers may pay in fiat, USDC or other supported assets, but payments are converted to IO behind the scenes, and suppliers can choose to be paid in IO or to convert earnings to USDC. The fee schedule is deliberately tilted toward the token: a 2 percent payment fee applies to USDC settled payments for both buyers and suppliers, while payments made fully in IO carry no payment fee. A 0.25 percent reservation fee applies to the total compute reservation cost on both sides.

IO also secures supply. A minimum amount must be staked as collateral to operate a node and earn idle rewards, with an additional staking allowance per node for holders who want exposure to rewards. Staking rewards are not auto compounded and unstaking runs through a fourteen day cooldown, during which the cooling coins do not count toward the staking requirement.

Supply is capped at 800 million IO. 500 million was distributed at launch and the remaining 300 million is emitted as rewards to suppliers and their stakers over 20 years on a disinflationary schedule that starts near 8 percent annual inflation in the first year and steps down over time. The documentation also describes a programmatic burn in which network revenue is used to buy and burn IO.

What Makes io.net Unique?

The distinctive choice is that io.net treats Ray, an orchestration library already used for large scale machine learning training, as the native clustering primitive rather than inventing a bespoke scheduler. That makes the network legible to engineers who already write distributed Python. The second distinctive choice is verification discipline: hourly Proof of Work plus VRAM checks target the specific failure mode of a permissionless hardware marketplace, which is suppliers overstating what they actually have. The third is that reservations, payments and buybacks were pushed on chain, so the network's commercial activity is publicly auditable rather than reported only through a dashboard.

How io.net Differs from Similar Projects

io.net sits in the decentralized physical infrastructure category alongside networks such as Akash Network, Render, Aethir and Nosana. All of them route idle or underused hardware to buyers, and comparisons between them are best made on what each documents rather than on marketing. io.net's documented emphasis is on distributed machine learning clusters specifically, with Ray as the execution model, bare metal and Kubernetes deployment paths, confidential compute attestation for sensitive workloads, and Solana as the settlement layer. Networks that grew out of rendering, container hosting or inference queues optimize for different job shapes and expose different developer surfaces, so the practical question for a buyer is usually which network can hold the cluster topology their job needs.

Use Cases of io.net

• Renting distributed GPU clusters for training and fine tuning machine learning models.
• Serving inference workloads, including serverless inference through applications hosted on the network.
• Batch and parallel compute jobs that fan out across many workers via Ray.
• Rendering, simulation and pixel streaming workloads that need short bursts of GPU capacity.
• Monetizing idle hardware for data centers, mining farms and independent operators.

How io.net Is Secured

Security here has two separate meanings. The token and its financial flows are secured by Solana, where the SPL token lives and where escrow, payments and repurchases are recorded. The compute network is secured by an economic and verification layer instead: node operators must post IO collateral to participate and earn, hourly Proof of Work challenges test that advertised hardware is real and performing, and devices that restrict their capacity while listed can lose eligibility for rewards and hires. Access controls, firewalling and a modular design are described in the IO Cloud architecture documentation, and confidential compute attestation is offered for workloads that require hardware level isolation.

Risks and Considerations

io.net is a marketplace for a commodity with heavy, well capitalized incumbents. Its pricing advantage depends on the supply of underused GPUs remaining plentiful, which is not guaranteed across hardware cycles. Verification reduces but does not eliminate supplier fraud, and a permissionless hardware pool cannot offer the uptime and support guarantees of a single operator data center. Token economics carry ongoing emissions to suppliers and stakers for two decades, so demand for compute has to grow to absorb them, and the burn mechanism depends on real network revenue rather than being automatic. The project also went through a leadership change immediately before its token launch, which is a governance history worth reading directly. Staked IO is subject to a fourteen day unstaking cooldown, so positions are not instantly liquid.

Why io.net Matters

Access to accelerated compute is one of the real constraints on machine learning work, and the gap between what large cloud providers charge and what idle hardware costs its owner is wide enough to support a market. io.net is one of the more concrete attempts to close that gap with tooling engineers already use, and its choice to publish bookings and payments on chain makes it easier to check whether a decentralized compute network is actually transacting rather than merely enrolling hardware.

Where Can You Buy io.net (IO)?

IO is available on a range of centralized exchanges and, because it is an SPL token, on Solana decentralized exchanges and aggregators. Before trading on chain, confirm the token mint address against the official io.net website or the explorer link published there, since Solana token symbols are not unique and copycat mints are common.

Storage Options After Purchase

IO is a Solana SPL token, so any Solana compatible wallet can hold it, including browser and mobile wallets such as Phantom and Solflare. For larger balances, a hardware wallet paired with a Solana interface keeps signing keys offline. Staking IO against a node or for rewards is done through the io.net application with a connected wallet, and it is worth remembering that coins entering the unstaking cooldown stop counting toward node staking requirements until the cooldown completes. Leaving tokens on an exchange means the exchange controls the keys.

Related Coins

• Akash Network (AKT)
• Render (RENDER)
• Aethir (ATH)
• Nosana (NOS)
• Bittensor (TAO)