Provider at a glance
- Category
- Decentralised Compute
- Entity
- Not verified
- Official website
- io.net
Independent rankingchecked How it works
Details
Scored 62 out of 100 under methodology 2026.10.18, from the evidence read in September 2026.
io.net
GPU aggregator on Solana
Decentralised Compute
#3 Overall
Ranked #3 of 7 decentralised compute in the published ranking
62
ChainChoice Score
The ChainChoice Score, shown against 100: published scores run from 41 to 99.- High evidence confidence
Is io.net right for you?
Look elsewhere if these come first
- Fetchable Price Per GPU-Hour5/10 here; the category best is 8
- Verified vs Self-Reported Supply4/10 here; the category best is 7
- Published Utilisation and Live Availability4/10 here; the category best is 9
- Recourse When a Provider Vanishes Mid-Job2/10 here; Aethir scores 4
Not yet tested for your country. Markets it lists: Global.
to test where you can use it.
The rank above is the published one, the same for every reader. Find my best compute network shows where it lands for you.
What will io.net cost you?
Not priced on this basis
- Usage per month
- 10
How safe is io.net?
- Evidence: verified4 of 4 criteria rest on quoted, sourced receipts. Read September 2026.
- LicenceMiCA (EU): no register record on file here.
Alternatives to io.net
Compare all 4- 4Fluence3 points below · stronger on dc failure recourse (3 against 2)59
- 5Aethir7 points below · stronger on dc failure recourse (4 against 2)55
- 6Golem Network9 points below · stronger on dc failure recourse (3 against 2)53
For your setup
Find out if io.net fits you
The rank above is the published one — the same for every visitor. Answer the category's questions and this section shows where io.net lands for you, which criteria your answers weight up, and which stated needs the record does or does not meet. The published rank stays beside it.
- A few questions
- No account required
- Ranking-blind: no commercial input
- Personalised in under 60 seconds
Find my best compute networkNothing is inferred from clicks, popularity or commercial value.
Why this rank
Why io.net ranks #3
Each strength is read from evidence on a 0–10 ladder and weighted as the published methodology states. The 32 objective points these produce (12.5 here) sit inside the score; availability, friction, trust record and measured data add the rest.
4 published criteria · Σ weight 100
CriterionWeightStrength · 0–10ScoreContrib.MedianBestRankEvidence
305+4.805.08#3/7Loading evidence…
304+3.843.07#3/7Loading evidence…
204+2.563.09#3/7Loading evidence…
202+1.283.04#6/7Loading evidence…
Hairline = best in this ranking · tick = its median · a missing bar is "not scored", never zero
Margin−13behind Nosana, #2
RobustnessHoldsacross a one-point change to each of its 4 criterion scores, the re-run scores 60–64 and stays #3
Evidence4 of 4 scored4 quoted, 4 with a source link
What would move the rank
Each line is the ranking run again with one of io.net’s criterion scores changed and every other value held: the smallest whole-point change on that criterion that moves its rank, and where the re-run puts it. Up to 4 climbs and 3 falls are listed, smallest change first. Nothing here is a forecast.
Fetchable Price Per GPU-Hour 5 → 3 on its ladder · Fluence passes it−258#3 → #4
Verified vs Self-Reported Supply 4 → 2 on its ladder · Fluence passes it−258#3 → #4
Published Utilisation and Live Availability 4 → 1 on its ladder · Fluence passes it−358#3 → #4
Strengths
0 from the score dataWhere it leads
No scored criterion is at or within one point of the category best, so no strength can be stated from the data.
Tradeoffs
4 from the score dataWhere it trails
Not for readers who put first
- Fetchable Price Per GPU-Hour — 5/10 against a category best of 8/10
- Verified vs Self-Reported Supply — 4/10 against a category best of 7/10
- Published Utilisation and Live Availability — 4/10 against a category best of 9/10
- Recourse When a Provider Vanishes Mid-Job — 2/10 against a category best of 4/10
Record watch-outs
- io.net's own pages disagree on the H100 floor: $1.19/hr on the explorer and the /cloud widget, $1.80-2.50/hr in the pricing guide and $2.19/hr on the homepage, and the guide's per-minute billing sits against the terms' 'non-refundable one-hour minimum' on cluster orders. The explorer counts 1,078 collateralised GPUs and CPUs together, while the homepage markets 'thousands of secure, fully orchestrated global GPU clusters'.
Competitive position
Where io.net leads and where it trails
Rank on every objective dimension among the rows scored on it. A criterion in the top third of its pool is listed as a lead, the bottom third as a trail; the middle is neither. Popularity, size and commercial terms are not dimensions.
Availability#1 / 714.0 of 20 · constant here
Published criteria#3 / 79.4 of 30 · best 15.8
Friction#1 / 72.7 of 10 · constant here
Trust record#1 / 73.2 of 8 · constant here
Measured data#1 / 78.3 of 18 · constant here
Where io.net leads
- Fetchable Price Per GPU-Hour#3 / 7
- Verified vs Self-Reported Supply#3 / 7
- Published Utilisation and Live Availability#3 / 7
Where it trails
- Recourse When a Provider Vanishes Mid-Job#6 / 7
Closest alternatives
The 3 nearest rows by score
Nearest by published score in either direction. Each card states the criteria on which the two rows differ and the cost difference under the same scenario inputs; the compare arithmetic below shows why the higher one ranks higher.
Fluence#4 of 7 · score 59 · 3.0 points behind
io.net leads on
- Verified vs Self-Reported Supply4 vs 3
- Published Utilisation and Live Availability4 vs 2
Fluence leads on
- Recourse When a Provider Vanishes Mid-Job3 vs 2
Largest single reason io.net is ahead: published criteria (+3.1 display points).Scenario cost: Fluence has no verified pricing for this scenario.
Aethir#5 of 7 · score 55 · 7.0 points behind
io.net leads on
- Fetchable Price Per GPU-Hour5 vs 4
- Verified vs Self-Reported Supply4 vs 2
- Published Utilisation and Live Availability4 vs 1
Aethir leads on
- Recourse When a Provider Vanishes Mid-Job4 vs 2
Largest single reason io.net is ahead: published criteria (+7.0 display points).Scenario cost: Aethir has no verified pricing for this scenario.
Golem Network#6 of 7 · score 53 · 9.0 points behind
io.net leads on
- Fetchable Price Per GPU-Hour5 vs 1
- Verified vs Self-Reported Supply4 vs 3
- Published Utilisation and Live Availability4 vs 3
Golem Network leads on
- Recourse When a Provider Vanishes Mid-Job3 vs 2
Largest single reason io.net is ahead: published criteria (+9.4 display points).Scenario cost: Golem Network has no verified pricing for this scenario.
Against the leader
79 vs 62 · gap 17.0Why Akash Network ranks above io.net
The compare workspace's arithmetic applied to these two rows. Each dimension's share of the gap is its weight × the difference, on the displayed scale — it reproduces the displayed gap of 17.0 to within rounding.
DimensionThisAkash NetworkGap share
Availability · 23% weight · constant here14.014.0same
Published criteria · 35% weight9.415.8−16.6, worse
Friction · 12% weight · constant here2.72.7same
Trust record · 9% weight · constant here3.23.2same
Measured data · 21% weight · constant here8.38.3same
Published criterionThisAkash NetworkPoints
Fetchable Price Per GPU-Hour · w3057−1.92, worse
Verified vs Self-Reported Supply · w3047−2.88, worse
Published Utilisation and Live Availability · w2049−3.20, worse
Recourse When a Provider Vanishes Mid-Job · w2023−0.64, worse
Net6279−17.0
Your scenario
io.net is not priced for this scenario
Metered usage beyond whatever the plan includes, for a year. Excludes egress, support tiers and enterprise minimums. Change an input and every figure recomputes from the published rate; the published rank does not move.
your cost/yr · default scenario — set your own
Usage per month · your input10
Rate read from the provider’s published pricing ↗ on 15 September 2026.
your cost/yrCost is stated as your cost/yr in USD; it is never a yield, never annualised, and it does not enter the score.
Not priced on this basis
Under the default inputs · USDCategory medianNot priced0 of 7 rows priced
Cheapest pricedNone pricedDifference not stated · availability not applied — set your country to filter
7 of 7 rows in this ranking have no verified rate for this scenario and are absent from the median, not counted as free.
Evidence
Evidence read 15 September 2026
One row per published criterion: the page each strength was read from, its source type by domain, the reading date and whether the file and the published table agree. Open a row for the quote and the receipt.
4 of 4 cells scored
Score evidenceVerified4 of 4 criteria reconstruct from receipts
4 of 4 criteria reconstruct from a quoted, sourced receipt equal to the published strength.Public receiptsReading…4 quoted with a source URL
The receipt file has not been read yet.Evidence confidenceHighcoverage and corroboration, never freshness
4/4 criteria scored, with 4 dated sources quoted.RobustnessHoldsrank #3 across every one-point re-run
Whether the position holds when one criterion score is changed by one point and the ranking is run again. It is always a re-run of the ranking, never an estimate.The newest evidence read on the platform is 3 November 2026; this category's reading is older. The scores stand as read on 15 September 2026.
Reading the evidence ledger…
CriterionSourceTypeReadFreshnessStatusReceipt
Fetchable Price Per GPU-Hourstrength 5 · weight 30Report an error—15 September 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Verified vs Self-Reported Supplystrength 4 · weight 30Report an error—15 September 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Published Utilisation and Live Availabilitystrength 4 · weight 20Report an error—15 September 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.Recourse When a Provider Vanishes Mid-Jobstrength 2 · weight 20Report an error—15 September 2026*
Unknown
No reading date is recorded for this cell or its category.No receipt
A strength is published but no quote or source page is on file for it.How you can lose money here, and what the ranking scores
- Execution failure (io.net 2/10): you get a worse price, later, or nothing.Scored by Recourse When a Provider Vanishes Mid-Job · 20%
- Information failure (io.net 4/10): the number is wrong or bought, or your data leaks.Scored by Verified vs Self-Reported Supply · 30%
Not assessed by this ranking: Liveness failure, Exit failure. A high place says nothing about these; the Methodology tab says what each means. Also scored, as cost, quality or a summary of several families: Fetchable Price Per GPU-Hour (30%), Published Utilisation and Live Availability (20%).
Facts
facts, not scoresWhat the record publishes
- Pricing
- io.net's own pricing guide (fetched 15 Sep 2026; table dated 'February 2026'): H100 80GB '$1.80-2.50/hr' (auction, per-minute billing); A100 80GB '$0.80-1.40/hr'; RTX 4090 '$0.20-0.35/hr'; L40S '$0.90-1.30/hr'; AWS $6.88/hr, Azure $6.98/hr, GCP $5.62/hr for H100; '55-70% savings over hyperscalers'. io.net's other pages disagree with it: the homepage says 'H100s from $2.19/hr vs AWS at $12.29/hr'; the public explorer lists H100 80GB HBM3 at $1.19/hr (Ray), $2.09/hr (Container), $1.79/hr (Baremetal), $1.99/hr (VM); the /cloud comparison widget shows 'Cheapest: H100 $1.19 / hr' (it showed $0.74 earlier the same day). Terms (effective 1 June 2026): cluster orders carry 'a non-refundable one-hour minimum'; 'one (1) IO Credit equals USD $1'; IO Credits expire twelve months after purchase.io.net — GPU cloud pricing guide ↗ · 15 September 2026
- Prices published in
- USDio.net — GPU cloud pricing guide ↗ · 15 September 2026
- Licences held
- Not published
- Compliance level
- partial
- Regulatory note
- Not published
- Supported chains
- Multi-chain
- Markets served
- global
- Primary markets
- Not published
- Restricted markets
- Not published
- Operating limits
- Not published
- Availability note
- Terms (effective 1 June 2026) bar anyone on US, EU or UK sanctions lists or located in Afghanistan, Belarus, Central African Republic, Cuba, Eritrea, Iran, Iraq, Lebanon, Libya, mainland China, Myanmar, North Korea, Somalia, Syria, Sudan, and the Crimea, Donetsk and Luhansk regions of Ukraine.
No confirmed legal entity is on file for this record. Nothing is inferred from the brand name.
If something goes wrong with io.net: where to complain, and where to report a scam
Loading the routes for your country.
How this page is reviewed
Reviewed means this product in this category was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
History
What the record carries
Changes to published ranks are recorded in a ledger; every step and its cause is listed on the rank-history page. The entries below begin with the current verified snapshot, then the methodology versions whose changes applied to this category, newest first.
8 methodology entries
- 15 September 2026Current verified snapshot · methodology 2026.10.18Score 62, #3 of 7. 4 of 4 criteria scored. History starts here; earlier values are not interpolated.
- 10 October 2026
2026.10.8When nothing serves your country, the list shown for reference is the published ranking · platform-wide- fixed The reference list shown when nothing serves your country is the published order with the published scores, and a build check now fails any such list out of that order or with a score the ranking does not publish.
- fixed The explorer prints an overall rank only for a row the published ranking holds; a country entrant such as Coinbase Commerce for US merchants shows no overall rank.
- changed Published orders do not move. Country results change only where nothing serves the country: in India bill pay keeps Bitcoin Well first and now shows Strike second, as published; 35 such runs across all categories and countries now match the published list exactly.
- 10 October 2026
2026.10.6A criterion you require re-scores the rows that meet it · platform-wide- changed The explorer sends each criterion you require, at any band, as fit_required with your other answers; region, licence, chain and fact filters stay filters. On /best, a required criterion joins For you as a marked preference does, which needs your country; Overall stays the published ranking, filtered.
- added Every published criterion has a golden case as the explorer sends it (require:<criterion>), so the order a requirement gives is replayed and gated as the published order is, and a change to it needs an entry here.
- 16 September 2026
2026.09.15Dimension scores carry tenths, and eleven more categories are re-read from primary sources · platform-wide- changed Dimension scores resolve to tenths of a point (O-04b), and weightedTotal is rounded to six decimal places before the order is read. 518 published scores move across 107 categories that were not re-read; none of them moves by more than 4 points, and most move by 1.
- fixed 66 published scores change in the eleven re-read categories, against a verbatim source each. The largest moves are Reflexer RAI (−16), Beefy and Unrekt (−11), Aztec (−10) and Golem (+9) — all of them rows whose sources had moved since their last read.
- changed Published order moves in 38 of 119 categories and three #1s change: smart_contract_audits (Zellic → Certora) and travel_rule_compliance (Sumsub Travel Rule → CodeVASP) on the finer resolution, kyc_compliance (Veriff → Sumsub) on the re-read.
- added availabilitySource (O-04g): for a reader who states a country, a row whose availability in that country rests on a region tag its record gives no source for sorts below every sourced row. It is inert in every order published here, which states no country.
Methodology 2026.10.18, the same published run every visitor sees · receipt decentralised_compute:io_net_dcompute:2026.10.18:9c837a03b7fd
Are you io.net? Reply to this verdict, or send evidence, ask for a correction or claim the listing. Every message gets a public ticket number; none of it changes a rank unless a public page or a signed statement supports it.