Skip to main content
Skip to content
AI

Akash vs io.net vs Render: What Does a Finished Compute Job Cost?

Compare completed-job compute costs across Akash, io.net, Render and an AWS Spot scenario, including retries, recovery, output checks and uncertain delivery.

A metal compute cube above an orange illuminated platform, illustrating the total cost of an accepted compute job.
Reading options: audio, text size & sections

What Matters

A cheap GPU quote is useful only if the job finishes, meets its acceptance test and leaves you with the output. Akash, io.net and Render sell different services with different billing and recovery rules. Compare their cost per accepted workload, including failed attempts and operator time, before letting an agent choose infrastructure from an hourly price alone.

DN Evidence Block

Prepared for Decentralised News · Editorial by Heath Muchena · Primary-source review and original DN instrument; independent field testing is disclosed only where performed.

Last reviewed
11 November 2026. This is a current-documentation review, not a prediction presented as a completed 2027 deployment.
Scope
Akash deployments and provider operations; io.net VM, credit, PAYG and Agent Cloud documentation; Render pricing and rendering documentation. Google Cloud Spot documentation supplies a reference for interruption risk.
DN workload sample
Zero paid GPU deployments or provider performance tests in this edition. No independent uptime, successful-job rate or latency ranking is published.
Original instrument
DN Compute Completion Cost Model: local scenario arithmetic comparing cash, retries and active human effort for an equivalent accepted output.
Decisive finding
Resource price, billing rules, output acceptance and recovery are separate evidence questions. Product documentation can establish a rule; it cannot establish how reliably your workload will finish.

The Signal: buy a completed workload

The useful question for an AI team is straightforward: what will it cost to obtain an acceptable result under the team’s constraints? A rented accelerator, an available container and a completed render are different answers. Putting all three into a single H100 price table creates a comparison that looks precise while leaving the actual purchasing decision unresolved.

DN’s decision rule is to qualify the service first, reconstruct its bill second and measure completion third. Start with the required model or renderer, memory, region, data handling, deadline and output test. Then compare eligible offers. A bargain that fails one mandatory requirement has no place at the top of the shortlist.

This also changes the agent’s job. “Find the lowest rate” is a search task. “Buy enough suitable compute, preserve state, stay within the budget and return accepted output” is an operational responsibility. The latter needs evidence that a price screenshot cannot provide.

What are you actually buying?

ServiceDocumented purchaseFirst comparison questionEvidence still needed
AkashProviders bid on resource requirements; an accepted bid becomes a lease. [1]Does this provider meet the exact deployment specification?Actual startup, throughput, output validation, support and recovery behavior.
io.net VM / PAYGChoose a hardware configuration and supplier; PAYG bookings consume credits under product-specific billing rules. [4] [5]Which configuration, billing mode and price-change rules apply?Observed job cost, refund outcome, effective throughput and continuity.
RenderRendering work priced through OctaneBench-hour tiers, with a separate bandwidth charge. [8]Is this a supported rendering task with matching scene and quality settings?Final accepted-frame cost and delivery time for the actual scene.

These are service descriptions, not a ranking. Render’s rendering product should not receive a synthetic general-purpose H100 rental price. Conversely, a GPU VM quote is not the price of a finished animation unless the renderer, licensing, setup and output checks are included.

Claim versus evidence: five numbers to challenge

ClaimWhat would substantiate it?Current DN treatment
“Cheaper compute”Matched eligible offers followed by bills and accepted outputs.Possible advantage; no universal savings percentage.
“99.x% uptime”Defined service, interval, probes, exclusions and contract remedy.No unsupported network-wide uptime figure.
“Verified hardware”Specified verification mechanism, fresh evidence and validation scope.Evidence about an identified property, not automatic output correctness.
“Instant deployment”Timestamped request-to-ready observations, including failures.Vendor capability or claim until measured.
“Autonomous spot auctions”Actual procurement traces showing bidding, repricing and accepted executions.Agent access is documented; market-wide autonomous activity is unmeasured.

Akash: a provider bid becomes a lease

Akash’s deployment documentation describes a request, provider bids and a lease that locks pricing and reserves resources. The deployment continues until closure or exhausted escrow. That supports a competitive procurement model; it does not establish a continuously repriced micro-auction for an already running job. [1]

Provider selection can use location, hardware and feature attributes. Akash also documents restricting deployments to audited providers with signedBy. Treat these as selection evidence: inspect what the audit covers and which provider supplies the required resources. A network-level label cannot replace the deployment’s own acceptance test. [2]

State deserves a separate line in the purchasing decision. Akash says persistent storage is local to the provider and does not survive lease termination or migration to another provider. A cheaper replacement lease therefore needs a plan for the data that makes the workload valuable. Preserve a usable checkpoint outside the departing deployment before treating a move as a saving. [3]

io.net: read the billing mode before automating it

io.net’s VM documentation exposes supplier, location, VRAM, storage and other configuration details, including interconnect information. Two offers carrying the same GPU family name can therefore represent different environments. Keep those fields in the comparison record rather than reducing the offer to one rate. [4]

The current PAYG documentation states that the first hour is charged at deployment. Subsequent charges occur in small prepaid increments; supplier price changes can affect the next charge. Customer-stopped prepaid time is not refunded, while provider-side failure has a stated refund treatment. Credit exhaustion terminates bookings, with newer bookings terminated first when several share a low balance. [5]

The practical implication is that useful runtime and billable runtime may differ. Enter the amount charged for the attempt, including its minimum, rather than multiplying productive minutes by a headline hourly rate. Check the applicable rule again at deployment; a general marketing FAQ or a different booking mode may describe different terms.

IO Credits are documented as prepaid USD-equivalent credits. Keep credit purchases separate from compute consumption: funding an account is not itself proof that a job cost that entire deposit. Reconcile consumed credits, credited refunds and any remaining balance. [6]

Render: compare the rendering work unit

On the reviewed pricing page, Render lists Economy at €0.60, Standard at €1.20 and Performance at €2.40 per 400 OctaneBench-hours. Enterprise is marked unreleased. It also lists bandwidth at 0.09 credits per GB of scene assets transferred to nodes, charged for successfully rendered frames. These are vendor-published terms observed on 11 November, not DN execution prices or guaranteed job totals. [8]

Record the scene, renderer, frame count, quality target, selected tier and asset distribution. Sending assets to multiple nodes can make transferred data materially different from the original scene size. Do not silently convert a charge in credits into euros without the applicable conversion.

An older Render knowledge page still describes the earlier Trusted, Priority and Economy structure. For this review, the current pricing page supplies the rate snapshot; the discrepancy is a reason to retain dated evidence rather than mix old and new tables. Confirm the checkout estimate before committing a production job. [9]

Use the DN Compute Completion Cost Model

The model compares two routes for the same accepted output. It does not fetch live quotes, deploy hardware or estimate a provider’s failure rate. Enter your own scenario assumptions. Include the actual billing basis in successful- and failed-attempt cash costs; a failed attempt can still consume prepaid time, storage, transfer charges and operator effort.

DN Compute Completion Cost Model

Scenario calculator, not a provider benchmark. No live prices or reliability observations are loaded. Work in one currency and compare the same accepted result. The model assumes independent attempts with a constant success probability and eventual retries until success.

Cash per attempt must already include billing minimums, nonrefundable prepaid time and other attributable charges. Human minutes mean active effort, not unattended runtime. Separate one-off setup from work repeated on each attempt.

Use a non-sensitive task description. Do not enter credentials or private workload data.

Probability example: 0.80 means 80%. It must be greater than zero and at most one. This is your assumption, not a supplied provider failure rate.

Route A: scenario inputs
Route B: scenario inputs

Enter two scenarios or load the clearly labelled illustrative example.

Machine-readable output and privacy

The JSON export uses dn.compute-completion-cost.v1, calculation version 1.0.0. It records scenario inputs, arithmetic outputs, assumptions, source context and record creation time. It does not contain provider measurements. Creation time is not an observation timestamp. The calculator makes no external requests and sends no entered data to DN or a provider.

How the arithmetic works

Let p be the assumed probability that one attempt succeeds. Under an intentionally simplified model of independent attempts with a constant success probability, expected failed attempts before one success are (1 − p) / p. The model then adds one successful attempt, the expected failed attempts and any one-off setup.

Expected cash = one-off cash + successful-attempt cash + expected failures × failed-attempt cash

Expected human minutes = one-off minutes + successful-attempt minutes + expected failures × failed-attempt minutes

Economic cost = expected cash + expected human minutes × hourly time value / 60

Cash and time valuation remain visible separately. A salary allocation is not necessarily a new cash payment. A credit refund is not necessarily immediately withdrawable cash. Use one currency, avoid counting a charge twice and leave unknown inputs unresolved rather than calling them zero.

A worked scenario: the cheaper successful run loses

Illustrative assumptions, not provider measurements. Route A has a $4 successful-attempt bill and a $3.50 failed-attempt bill, with an assumed 80% success probability. It needs 10 setup minutes, 12 minutes around a successful attempt and eight around a failure. Route B has bills of $8 and $6, an assumed 95% success probability, and five minutes in each of those three effort categories. Both have zero separate one-off cash cost.

Model outputRoute ARoute B
Expected failed attempts0.250.0526
Expected cash cost$4.88$8.32
Expected active human effort24.00 minutes10.26 minutes
Economic cost at $60/hour$28.88$18.58

A is cheaper on cash under these assumptions; B has the lower combined burden when operator time is valued at $60 per hour. Changing that valuation can reverse the decision. The model provides a threshold to investigate, not evidence that any named network performs like either route.

The formula assumes retries continue until success. It does not model a deadline, a retry cap, permanent incompatibility, correlated provider outages or lost business. If those constraints matter, first reject ineligible routes or run a separate bounded recovery test. A small modelled average cannot guarantee delivery.

AWS Spot or a decentralized GPU: compare the interrupted job, not just the hour

Additional scope reviewed 12 November 2026. AWS Spot belongs in this comparison only after the workload and hardware requirements have been matched. A GPU family name is not a sufficient specification: retain usable memory, interconnect, CPU, storage, software, region, data handling and the output acceptance test. Render's rendering service is not automatically an interchangeable training VM.

AWS documents Spot interruption notices on a best-effort basis. The usual two-minute warning for stop or termination does not apply in the same way to hibernation, which starts immediately. Its preparation guidance recommends preserving important data and designing recovery rather than treating notice delivery as guaranteed. These are documented service boundaries, not a DN-measured interruption frequency. AWS interruption notices · AWS interruption preparation.

The purchasing question is therefore whether the chosen job can recover under its actual deadline and budget. A restartable batch with external checkpoints has a different requirement from a stateful job that cannot reproduce an interrupted step. Apply the same recovery standard to a centralized and a decentralized supplier; ownership architecture alone is not an uptime guarantee.

Use the existing DN Compute Completion Cost Model above for a matched pair of scenarios. The cost of a failed attempt should include the charged runtime and other attributable charges after any applicable refund, not simply the minutes that produced useful output. Preserve active operator effort separately. The success probability remains an assumption until supported by an appropriately defined workload sample.

Synthetic sensitivity example: ignoring one-off setup and human time, a route costing 4 units on success and 3 on failure with an assumed 0.5 success probability has expected cash cost 4 + ((1 − 0.5) / 0.5) × 3 = 7 units per eventual accepted output. A second route costing 6 on success and 5 on failure at assumed 0.9 success probability costs about 6.56. The cheaper successful attempt is not the cheaper modeled completed job. These are invented values, not AWS, Akash, io.net or Render prices or reliability observations.

Do not use this eventual-success calculation to promise a deadline. A capped retry budget, correlated outage or permanent incompatibility violates important parts of its simplified model. For a hard deadline, first establish capacity and recovery eligibility, then use cost arithmetic among the remaining routes. A rejected route should remain in the evidence record rather than vanish from the trial results.

Evidence and change log: this addition addresses outline 111 without creating a duplicate compute-comparison URL or repeating a generic provider ranking. No paid deployment, live quote capture or provider performance test was conducted. The original 11 November pricing and documentation observations retain their dates. A future measured comparison needs matched configurations, timestamps, complete bills, every failed attempt and independently checked accepted output.

Recovery and verification belong in the cost record

Test what is preserved when an attempt fails: input, checkpoint, logs, output and access to the replacement environment. “Persistent” must be interpreted under the service’s actual lifecycle. A checkpoint that exists only on an inaccessible machine cannot establish recoverability.

Interruption risk also exists in conventional cloud products. Google Cloud documents that Spot VMs can be preempted and are excluded from its Compute Engine SLA. That makes a useful comparison principle: price the selected product’s contract and recovery behavior, rather than assuming one ownership model guarantees continuity. [11]

For sensitive work, ask what the security evidence establishes. io.net publishes an attestation process for its confidential-compute VMs covering hardware identity and configuration properties. That is a narrower claim than proving the scientific validity of a model output or the commercial accuracy of an agent’s answer. DN’s interpretation is to keep infrastructure verification and result acceptance as separate controls. [10]

What changes when an agent buys the compute?

io.net’s Agent Cloud documentation describes an MCP interface with tools for browsing hardware, estimating configurations, deploying and destroying resources, and checking credit status. Agent-accessible provisioning is therefore a documented capability. DN did not connect a spending account or test these actions for this review. [7]

The proposed control is a procurement record with an explicit approval boundary. Let the agent assemble eligible configurations and record the offer. Give a separate spending policy responsibility for the permitted supplier, region, maximum bill, top-up limit and termination condition. An agent able to compare prices does not automatically need unrestricted authority to replenish credits.

Require the record to connect the quote, approval, deployment identifier, invoice, output test and shutdown confirmation. Otherwise, the agent may finish the user’s task while leaving billable infrastructure running. Review the account’s aggregate burn rate as well as the individual job: multiple apparently affordable deployments can consume one shared balance.

How We Review at Decentralised News

This edition compares documented purchasing and operating rules. We prioritized current product documentation over broad marketing claims and retained a dated price snapshot only where its unit was explicit. A documentation conflict is recorded as unresolved context rather than blended into a fabricated average.

The cost model is original DN arithmetic. Its default example is synthetic, and any reader-entered observation remains unverified by DN. To publish a future performance comparison, we would need a preregistered workload, fixed acceptance criteria, matched configurations, a declared observation window, complete billing and failure logs, and enough repetitions to show variability. Unfinished and failed jobs must remain in the denominator.

No universal uptime percentages, numerical risk scores or provider execution rankings are asserted here. Commercial relationships do not determine the evidence standard. The best route can change with the workload, region, deadline, price, billing terms or cost of human recovery.

Frequently asked questions

Which of Akash, io.net or Render is cheapest?

This review does not establish a universal winner. Qualify the workload, obtain a dated offer, include billing and recovery costs, and compare accepted outputs. A rendering work unit cannot be treated as an interchangeable VM rental hour.

Does a low advertised hourly price establish the job’s bill?

No. Minimum charges, prepaid increments, unused time, storage, transfer, licensing and human work can change the result. Use the applicable product rules and reconcile the actual bill.

Does the calculator show real provider reliability?

No. Success probabilities are explicit scenario inputs. DN ran no paid workload experiment for this edition, and the calculator does not turn an assumed percentage into observed uptime.

Does hardware attestation guarantee a correct AI answer?

No such conclusion follows from this review. Infrastructure evidence and output validity answer different questions. Define and apply the task’s own acceptance test.

Can I use this for a job with a hard deadline?

Use it as a cost sensitivity exercise only. Its eventual-success assumption does not predict completion time or deadline compliance. A deadline requires separate capacity and recovery evidence.

Source ledger

Primary sources reviewed 11 November 2026. Product rules and available configurations may change; retain the offer and terms that apply to your own deployment.

  1. Akash: Deployments & Lifecycle — bids, lease pricing, lifecycle and escrow.
  2. Akash: Providers & Leases — attributes, audited-provider filtering and operational responsibilities.
  3. Akash: Persistent Storage — provider-local persistence and termination boundaries.
  4. io.net: Deploy VM on Demand — supplier, location and hardware configuration.
  5. io.net: Pay-As-You-Go — first charge, repricing, credits and termination.
  6. io.net: IO Credits — funding and usage records.
  7. io.net: Agent Cloud — documented agent provisioning interface.
  8. Render: Pricing — current tier and bandwidth snapshot.
  9. Render: Pricing of Compute Work — older tier documentation; retained to disclose the discrepancy.
  10. io.net: Confidential Compute Attestation — stated verification scope.
  11. Google Cloud: Spot VMs — interruption and SLA boundaries for the reference product.

Organize the workload record

If your team needs software to coordinate job requests, approvals and follow-up tasks, Make and Taskade are optional workflow products to evaluate. Check the integrations, permissions and plan limits needed for your own process before buying. This review has not tested either product as a compute-provisioning integration.

Affiliate disclosure: DN may earn a commission through these two links. They are separate from the provider comparison and do not affect the calculator. The products’ current official sites were reviewed on 11 November 2026.

Continue the decision

For application-level economics, read The Real Cost of an Agent Buying an API Call. For interruption handling, use the DN Runtime Recovery Test. For model-level cost context, see the DN Compute Cost Index.

Change log and corrections

11 November 2026: substantive refresh of this existing article. Replaced unsupported network-wide uptime, fixed H100 price comparisons and numerical risk scores with current product-specific evidence and explicit unknowns. Added billing distinctions, recovery analysis and the DN Compute Completion Cost Model. The existing URL is preserved.

Send a correction with the relevant product page, configuration and date to press@decentralised.news. Do not send credentials, private keys or private workload data.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.