Filecoin's 2026 strategy shifts the question from how much data the network can hold to how much it is paid to store and serve. Revenue Development is the program behind that shift. It funds the pods directly: there is no open call and no public application.
Revenue Development doesn't run an open call. It funds pods, each with a specific product and go-to-market mandate, each accountable for revenue in its slice of the ecosystem. Capital follows their six-month roadmaps and is released as milestones land.
If you see something a pod's roadmap is missing, R&D is the program that funds it. Work aimed at a gap in the network is requested through published RFPs there, and what proves out can become part of a pod's roadmap later.
A pod is a small, mission-focused team with a specific product and go-to-market mandate. Pods own product and revenue for their slice of the ecosystem, and Revenue Development milestones are scoped against their six-month roadmaps.
Developer platform
Filecoin's developer-facing storage platform: warm storage, verifiable retrieval, and proof-gated payments, plus the SDK surface teams build against. Also carries demand from builders at the intersection of AI, DePIN, and Web3.
Enterprise object storage
Enterprise sales into traditional storage buyers: S3-compatible object storage on Filecoin, aimed at the petabyte-scale workloads that move on price, durability, and compliance. Also carries large dataset onboarding.
Below is onchain revenue and the GTM pipelines, followed by each pod's progress against its funding agreement and targets.
Filecoin Pay is where money that settles on Filecoin mainnet shows up, and this section reads the annual run rate straight off those rails rather than off a forecast.
Read it carefully. Annual run rate across every Filecoin Pay rail, read live off the contracts rather than extrapolated from settlements. Run rate is what current rails would pay over a year if nothing changed; it is not cash already collected.
| Pod | What it reports | Latest | Reading |
|---|---|---|---|
| FOC | Filecoin Pay ARR (run rate) | $99K | against a $250K H2 commitment |
| LDO | no revenue line reported | — | the pod carries capacity and retrieval targets, not a revenue target |
| Fil One | cash collected to date | $639 | collected cash, not a run rate — stated ambition is $2-4M ARR |
A run rate, a cash total and no revenue line at all cannot be added into one number. A single cross-pod revenue figure would need the pods to report on the same basis first.
One pod runs an enterprise sales book: each opportunity has a stage, a deal value and a win probability. The other runs a partnership tracker that records neither value nor probability. The two are reported separately below and are not combined. Figures are aggregate only; counterparties are not named on this page.
| Stage | Opportunities | Book | Weighted | Capacity | |
|---|---|---|---|---|---|
| Prospect | 11 | $12.7M | $1.3M | 212 PB | |
| Discovery | 8 | $20.6M | $4.1M | 343 PB | |
| Other open stages † | 5 | $1.8M | $700K | 30 PB |
| Stage | Partnerships | |
|---|---|---|
| Inbound | 3 | |
| Triage | 3 | |
| In Progress | 18 | |
| Existing Partner | 8 | |
| Stale | 10 | |
| Closed/Dead | 13 |
| Pod | What it does | Delivered | |
|---|---|---|---|
| FOC | Filecoin's developer-facing storage platform — warm storage, verifiable retrieval and proof-gated payments, plus the SDK surface teams build against. | 2 of 6 | Learn more → |
| LDO | Large dataset onboarding at pool scale — pooled storage provider capacity, audited allocation, a public dataset directory and paid retrievals. | 3 of 7 | Learn more → |
| Fil One | Enterprise object storage — S3-compatible storage on Filecoin for the petabyte-scale buyers that move on price, durability and compliance. | 2 of 5 | Learn more → |
Filecoin Onchain Cloud (FOC) serves Web3 application developers. It is building a production-grade onchain service layer: programmable warm object storage with cryptographic verification and automated onchain payments, exposed through developer APIs and SDKs. FOC includes warm storage with Filecoin PDP, simple onchain payments with Filecoin Pay and one-click IPFS pinning on the network with Filecoin Pin. The aim is to make Filecoin Onchain Cloud the default onchain payment layer for Web3's decentralized storage, retrieval, and compute needs.
The pod also closed 14 tracked issues in its last 8 reviews.
$99K
Annual run rate across every Filecoin Pay rail, read live off the contracts rather than extrapolated from settlements.
2
Customers spending $500 or more a month, trailing 30 days. The test of whether anyone depends on the service, not just tries it.
1.69 min
Docs to first stored piece, measured end to end in every review. Lower is better, and it has been under the ceiling all year.
| Commitment | Target | Where it stands |
|---|---|---|
| ARR (Filecoin Pay) | $250K H2 | Rate-based ARR across all Filecoin Pay rails. Growth is real but concentrated in a small number of payers. |
| Recurring power users ($500+/mo) | 5 (Q3 contract) / 3 mainnet | Most of the run rate comes from a single payer that is itself funded by this track, rather than from external demand. |
| Beachhead market validated | 1 | None validated yet - the ideal customer profile is still forming around AI agents and IPFS migrants. |
| SP reliability / SLA | endorsed SPs meet 72h SLA | Six approved mainnet storage providers; five at 100% and one at 97.9%, recovered from 0 of 3 in July. |
Large Data Onboarding (LDO) serves the institutions and applications that need large public and scientific datasets onboarded and kept retrievable. It builds Filecoin-native tooling and market mechanisms, including a workflow that pools many data contributors into a single provable storage deal, dataset lifecycle management, and paid retrievals, so that archival, library-level data stays verifiable and available on demand. Its pipeline is live, with hundreds of terabytes onboarded.
The pod also closed 2 tracked issues in its last 8 reviews.
430 TiB
Against a 2.5 PiB commitment. The pool has the room — capacity cleared its own target — but clients have not filled it.
4
Storage providers actually taking pool data. Named the tightest constraint in almost every review.
0%
The product shipped and works. The rate stays at zero because no provider has adopted it yet, which is an adoption problem rather than a reliability one.
| Commitment | Target | Where it stands |
|---|---|---|
| P2PP allocator security audit | passing review by Aug 1 | The audit report was due 19 Aug. Delivery is not evidenced in any review published since. |
| SP recruitment | 10 (14 contacted) | Named as the tightest constraint in nearly every review. |
| Data onboarded | 2.5 PiB | Against a 2,560 TiB target. The pool capacity exists; clients are not filling it. |
| Paid-retrieval success rate | 95% | Deployed and working, awaiting storage-provider adoption. An adoption problem rather than a reliability one. |
Web2 Object Storage (Fil One) serves Web2 developers who just want object storage that works. It offers a self-serve, S3-compatible path that turns familiar upload-and-retrieve usage into recurring, paid, onchain Filecoin deals across multiple ecosystem on-ramps (the services that move data onto Filecoin). The product launched this spring and is converting its first paying customers.
The pod also closed 1 tracked issue in its last 8 reviews.
1,551
Top of the self-serve funnel. Growing steadily, and the only part of the motion that clearly works.
85
Accounts that converted from a trial to a card. No numeric target was committed for this one.
$639.00
Cash actually collected to date — not a run rate. Set against a stated ambition of $2-4M ARR, this is the gap the enterprise pipeline at the foot of this page has to close.
| Commitment | Target | Where it stands |
|---|---|---|
| Revenue | $2-4M ARR | Collected cash, not ARR. The original $100K-by-30-Apr target was retired and replaced by the $2-4M 2026 ARR figure. |
| Enterprise pipeline -> signed deals | convert 1-2 this tranche | A regional design-partner cluster plus 12 or more prospects at roughly 1 PB - still pre-revenue. |
| Acquisition engine | working funnel | Cold outreach produced no intent and was paused to narrow the ICP towards CCTV and neocloud buyers; a partner campaign returned a small number of replies. |
It is rebuilt from the pods' own biweekly business reviews every time it runs, so it moves when they do rather than freezing on a reporting date.
Metrics and shipped work come from the business-review ingestion — FOC to 23 Sep 2026 (30 reports) · LDO to 30 Sep 2026 (17 reports) · Fil One to 24 Sep 2026 (26 reports) . Each pod's figures are read from its own report; where a pod did not state a number in a given period it is shown as missing rather than as zero.
Commitments and their status are a curated ledger reviewed against the signed funding agreements, not a self-report. What each pod does is the pod's own description, supplied by the Filecoin ProPGF team and carried verbatim rather than authored here.
Pipeline figures are published as stage aggregates. Counterparty names, deal values and notes are held back: stages with fewer than three opportunities are combined, and money is rounded, so no single deal can be isolated. Committed amounts are transcribed from signed funding agreements that are not yet machine-readable.
Every figure on this page can be reproduced. It is built entirely
from the public filecoin.filpgf_public dataset, which
anyone with an OSO API key can query. Nothing is read from a private
table. This is a monitoring view published for transparency. It is
decision support, not a decision.
Each pod is funded against a six-month roadmap rather than an annual budget, with payouts released as milestones land. Nothing arrives up front, and a roadmap that stops moving stops drawing down.
Pod scopes the roadmap
Six months of work against a named KPI
Review and allocation
Assessed against the 2026 network objectives
Milestones land
Payouts released as delivery is verified
Published progress
Bi-weekly reports, monthly roll-up
Re-scope
Next roadmap set against results
Revenue Development funds the pods directly, so there's nothing to apply for here. R&D is where outside teams can pick up work that supports them.
