DigitalOcean projects remaining performance obligations above $800 million for the second quarter, compared with $243 million on March 31. The increase is at least $557 million. The company also disclosed multiple nine-figure annual customer commitments and 20 megawatts of additional capacity expected only in late 2027 or early 2028. [1]
The disclosure gives an operating-company version of Thursday's warning that three enormous planned IPOs could leave ordinary venture liquidity unrepaired. Large aggregate values attract attention. They still need a route into cash. DigitalOcean's route runs through contracts, capacity, delivery and recognized revenue.
RPO is not cash in the bank. It measures contracted obligations expected to become revenue as the company performs. Timing, cancellation terms, service delivery and customer use determine how that balance matures. The fetched report does not disclose the customers, the exact number behind the word "multiple," or the value and duration of each commitment. [1]
The capacity calendar makes the distinction harder to ignore. DigitalOcean says the extra 20 megawatts will take its footprint to 155 megawatts, but the increment arrives in late 2027 or early 2028. [1] Commitments announced now may therefore depend on existing capacity, staged deployment or infrastructure that has not yet arrived. The report does not identify the location of the new power.
That gap does not invalidate the contracts. It defines the execution test. A cloud provider can sign demand before installing every server needed to satisfy it, just as other infrastructure businesses book work before completing a plant. Investors must then ask what capital is required, when service begins and whether margins survive the buildout.
Company and mainstream messaging emphasize accelerating AI demand and lower total cost. Cloud discourse reads nine-figure commitments as proof that a challenger has broken through. No verified topical X post surfaced for this disclosure, so that conclusion remains unquoted. DCD's figures support a narrower claim: obligations rose sharply, while customer identities and later capacity remain undisclosed. [1]
The reported 29 percent projected quarterly revenue growth supplies another useful measure, but it is not interchangeable with the RPO increase. [1] Revenue belongs to a period; RPO belongs to future performance. Adding or comparing them without their definitions would create a growth rate neither number carries.
DigitalOcean has placed three items on the public ledger: more than $800 million of projected RPO, multiple large commitments and 20 megawatts expected years later. The next receipts are customer disclosure, contract duration, capex, energization and revenue conversion. Until then, the backlog is real as an obligation and incomplete as a cash story.
-- THEO KAPLAN, San Francisco