Render: One Company's Cloud
Render is the DePIN that actually renders — 76.5M frames, real Hollywood VFX. But "decentralized" describes the GPU supply, not the control: the engine is OTOY's closed-source Octane, OTOY takes 5% of every job, and ~60k of its GPUs are borrowed from another network. Cache256: one company's cloud.
Render is the DePIN that actually renders. Not a whitepaper — 76.5M frames processed, real Hollywood VFX work (it rendered an A$AP Rocky music video), a genuinely used decentralized GPU marketplace. But "decentralized" describes the GPU supply, not the control. The engine everyone renders on — OctaneRender — is closed-source software owned by one for-profit company, OTOY, which sets the roadmap, runs the largest operations, and takes 5% of every job. And the headline GPU number is increasingly borrowed: native nodes sit around 5,600, while a single April 2026 deal bolted on ~60,000 consumer GPUs from another network. Render's supply is decentralized. Its control isn't.
Last update: July 2026 · Render Network / Ecosystem · By Cache256 Intelligence
Render is a decentralized GPU network built by OTOY, the graphics company founded by Jules Urbach. The idea is elegant: creators need expensive GPU rendering; millions of gaming PCs sit idle; a marketplace and a token (RENDER, now on Solana) match the two. Unlike the DePIN projects that ship a token and no demand, Render has real work flowing through it — VFX studios, 3D artists, and a growing slice of AI jobs.
Which makes it a perfect Cache256 subject, because the usage isn't the question — the control is. This analysis reads Render through three: does one company run the "decentralized" network? Whose GPUs is it actually selling? And does the token capture the demand, or just the narrative?
// HISTORY 2017–2026
2017–2020 — Token, then mainnet
OTOY launches the RNDR token (2017 ICO) to turn its OctaneRender engine into a decentralized render farm. Mainnet goes live in 2020; early nodes render 3D/VFX jobs.
2021–2023 — Growth, and a foundation
The network scales to thousands of GPUs and integrates AI tools. In January 2023, OTOY spins out the Render Network Foundation (Cayman Islands), handing it the protocol, brand and governance — while keeping Octane itself.
2024 — Migration to Solana
RNDR becomes RENDER on Solana (1:1), and the network adopts Burn-Mint-Equilibrium (BME): creators burn RENDER to pay, the protocol mints RENDER to reward nodes.
2026 — The AI pivot and a borrowed fleet
Render leans into "AI compute" branding (AI is now 35–40% of jobs). At RenderCon 2026 (Hollywood, April), governance approves RNP-023: the Salad network joins as an exclusive subnet, adding ~60,000 consumer GPUs.
// ONE COMPANY'S STACK
The Render Network Foundation governs the protocol — real on-chain proposals (RNPs), token-holder votes, community grants. But governance and control are not the same thing.
The engine is closed, and it's OTOY's. Everyone on Render renders with OctaneRender — proprietary, commercial software that OTOY builds, licenses, and updates on its own cadence (Octane 2026 shipped this year). OTOY writes the core stack, the plugins (Blender, Cinema 4D, Houdini, Unreal), and the roadmap. The "decentralized network" runs on one company's closed engine.
And OTOY gets paid off the top. Every job carries a 5% protocol fee that goes to OTOY, off-chain — separate from the on-chain token burn. The Foundation holds the brand and the votes; OTOY holds the software, the Hollywood relationships, and a cut of the revenue. It is, functionally, one company's cloud with a governance layer bolted on.
// WHOSE GPUs?
Render's marketing leans on big GPU numbers. The reality is more specific — and more revealing.
Native is small. The network's own node base has hovered around 5,600 GPUs. That's the decentralized hardware Render actually built.
The big number is rented. The jump to "60,000+ GPUs" came almost entirely from one deal: RNP-023 made Salad, a consumer-GPU network, an exclusive subnet. Those ~60,000 machines are Salad's, across 180+ countries; Render routes jobs to them and takes a burn. Increasingly, Render isn't a GPU network — it's an orchestrator of other GPU networks. That's a legitimate way to scale, but it means the "decentralized supply" is largely someone else's, and the dependency runs deep: Salad reportedly projects ~$4.3M of first-year revenue into the system.
// THE CONTROL READ
Three verdicts on where Render's power actually sits.
1 · One company's cloud. OTOY owns the closed-source engine (Octane), builds the tools, drives the roadmap, and takes 5% of every job. The Foundation's governance is real, but the product that matters — the rendering — is a proprietary OTOY stack. "Decentralized" is true of the GPUs and the votes; it is not true of the software or the direction. Compare a genuinely neutral marketplace like Akash, which rents raw compute with no proprietary engine in the middle.
2 · The GPUs are increasingly borrowed. Native nodes ~5,600; the marketed fleet is mostly Salad's ~60,000. Render is becoming an aggregator that sells access to other networks' hardware. Good for elasticity, but it reframes what "Render's network" even means — and concentrates risk on a subnet partner it doesn't own.
3 · The token captures some — not all — of the demand. BME is better than pure emissions: real jobs burn real RENDER (~1.46M burned to date). But two leaks remain — the protocol keeps minting RENDER to pay nodes, and OTOY's 5% exits off-chain in dollars. So RENDER accrues value from usage and dilutes from emissions at the same time; whether it's net-deflationary depends on job growth outrunning the mint. It's a usage token with an asterisk, not a clean demand sink.
// METRICS (July 2026)
RENDER: ~$1.54; market cap ~$801M; rank ~#72; ~518.8M circulating of ~644.2M max (~80% emitted, largely unlocked). ~−89% from the $13.53 ATH (2024). (reconfirm at publish)
Network: ~76.5M frames rendered all-time (Render Foundation dashboard), ~1.5M/month; ~5,600 native GPU nodes + ~60,000 via the Salad subnet (RNP-023, April 2026). AI = 35–40% of jobs (generative/inference), the rest VFX/3D.
Control: OctaneRender proprietary (OTOY); Foundation (Cayman, 2023) governs RNPs + Nation voting; OTOY takes 5%/job off-chain; OTOY's token holdings/voting power are undisclosed.
Token economics: Burn-Mint-Equilibrium on Solana; ~1.46M RENDER burned cumulatively; ongoing mint emissions for node rewards. Net inflation/deflation not publicly broken out.
// COMPETITIVE — DePIN GPU
The honest read: Render is not the leader in raw AI compute — Aethir and io.net move far more GPU volume and enterprise revenue. Render's real moat is narrower and more durable: Octane and the VFX pipeline, the creative workflows Hollywood already uses. Which is exactly why the "AI compute DePIN" rebrand is worth watching — it reaches for a bigger market than the one Render actually owns.
// WHAT WOULD CHANGE THE READ
OTOY loosens its grip. If Octane opened up, or the Foundation gained real technical independence, the "one company's cloud" verdict would weaken.
Native supply grows again. If Render's own node base scaled alongside the subnets — rather than being lapped by borrowed GPUs — the "whose GPUs" critique fades.
AI becomes the majority, for real. If verifiable AI-compute demand (not reclassified rendering) overtakes VFX and burns outrun mints, the token thesis and the AI-compute narrative finally align.
BME turns durably deflationary. If job growth (Salad + new subnets) sustainably burns more than the protocol mints, RENDER becomes a genuine usage sink instead of a usage token with leaks.
// FAQ
Q: Is Render actually decentralized?
A: Partly. The GPU supply is distributed and governance runs through token-holder votes (RNPs). But the core rendering engine (OctaneRender) is closed-source and owned by OTOY, which also sets the roadmap and takes 5% of every job. Decentralized supply, centralized stack.
Q: How many GPUs does Render really have?
A: Its native node base is around 5,600. The widely cited "60,000+" comes mostly from the Salad subnet (RNP-023, April 2026) — a separate consumer-GPU network Render routes jobs to. Render increasingly aggregates other networks' hardware.
Q: What is OTOY's role vs the Foundation?
A: The Render Network Foundation (Cayman, spun out 2023) governs the protocol, brand and RNPs. OTOY builds and owns OctaneRender and the tooling, provides engineering, and collects the 5% fee. Governance sits with the Foundation; the product sits with OTOY.
Q: What is Burn-Mint-Equilibrium (BME)?
A: Creators pay for jobs by burning RENDER; the protocol mints new RENDER to reward the node operators who did the work. It ties supply to usage — but ongoing mints plus OTOY's off-chain fee mean the token isn't a pure deflationary sink.
Q: Is Render an AI company now?
A: AI is 35–40% of job volume (generative/inference), and the branding leans hard into "AI compute." But the majority of usage and the durable moat remain VFX/3D rendering via Octane. The AI pivot is real but partial.
Q: Why is RENDER down ~89%?
A: A 2024 bull-market peak of $13.53, broad altcoin drawdown, ongoing emissions, and a token whose value capture is partial. The network's usage kept growing; the token did not follow.
// RELATED READING
Decentralized GPU compute with no proprietary engine in the middle — the contrast to Render.
The network winning the raw AI-compute volume Render's rebrand reaches for.
Trust-minimized decentralized compute — a different answer to "whose GPUs, and can you trust them?"
Where Render, Akash, io.net and Aethir sit in the decentralized-compute map.
// EXTERNAL REFERENCES
• CoinGecko — RENDER price/mcap/supply & Render Foundation — network dashboard (frames, burns, nodes) (accessed 2026-07-10)
• RNP-023 — Salad exclusive subnet (proposal text) & Salad — joining the Render Network (accessed 2026-07-10)
• DefiLlama — Render BME (5% fee, burns) & Render Knowledge Base — Burn-Mint-Equilibrium (accessed 2026-07-10)
• OTOY — OctaneRender (proprietary engine) & Render — announcing the Foundation (2023 spin-out) (accessed 2026-07-10)
Network figures are from the Render Foundation dashboard unless independently sourced. Volatile metrics flagged "reconfirm at publish."