Three verbs, both halves
Oculus runs the same three verbs across both halves of the build. Sourced. Delivered. Financed. Power to the site. Compute into the hall. Capital structured around the asset so nothing waits on a balance sheet.
- Sourced: generation and hardware procured against your timeline.
- Delivered: power to the site, compute into the hall, on a compressed schedule.
- Financed: institutional capital structured around the asset, opex or owned.
Why one counterparty matters
Sourcing, delivery, and financing under a single relationship instead of three.
When one party carries both lanes, the timeline is set once and the seams disappear. The site holds a single relationship. The power schedule and the compute schedule are planned against each other instead of negotiated across a table. And the capital for both can be structured together, around the same asset and the same revenue.
This is not a bundle for its own sake. It is the recognition that power and compute are not two projects. They are one build, and the fastest way to deliver it is to carry it as one.
What it looks like in practice
A developer with a powered site brings us the deployment. An operator with a constrained site brings us the gap. In both cases the work is the same: scope it, source it, deliver it, and finance it, under one counterparty, until the site is live.
Where power meets compute, there should be one party accountable for both. That is the company Oculus is built to be.