Compute Capital Markets
Shayon Sengupta’s essay on physical delivery, principal desks, and compute financing credits discussions with Epilogue cofounder Kyle Morris.
Read the essay (opens in a new tab)A compute contract is a commitment to what someone can build next. We work with capital partners, operators, and trading desks to put more capacity into use—and give the next wave of builders more room to grow.
Explore the partnerships
Epilogue contracts for its own pool of compute, running inference and serving startups in its network and independent researchers. We take forward positions to provision that pool and trade capacity through our book.
Our team includes founding members of AGI House, a community dedicated to advancing the technological frontier. AGI House housemates have founded companies worth over $1 trillion, including OpenAI, Perplexity, and Lovable.
Our bids and offers, alongside third-party listings for colocation and larger clusters.
Shayon Sengupta’s essay on physical delivery, principal desks, and compute financing credits discussions with Epilogue cofounder Kyle Morris.
Read the essay (opens in a new tab)Behind the AI buildout is a compute market still run by phone calls and private negotiations. Kyle Morris explains what’s broken, why large GPU deals are so hard to close, and what needs to change.
Watch the talk (opens in a new tab)Compute needs capital before it earns revenue. Buyers face deposits; operators need commitments; lenders need to understand the capacity and cash flows behind the paper.
We’re developing financing structures with partners around our own positions and transactions originated by others. Bring an existing compute contract, a lending mandate, or a project seeking offtake.
Fund an upfront deposit or a schedule of compute payments against an identified contract.
What the structure needs to answer: Who owes what, when funds are released, when service starts, and how the lender is repaid.
Pair a capacity commitment with funding for hardware or a deployment. We can assess an offtake already in place or discuss a purchase for our book.
What the structure needs to answer: Delivery milestones, contracted revenue, hardware and capacity rights, and the plan if commissioning slips.
Explore credit for teams whose compute bill arrives before their customer revenue.
What the structure needs to answer: Usage, customer receipts, payment timing, credit support, and the size of the commitment.
Develop contracts that fix a price for future compute revenue, giving an operator more visibility over what its capacity will earn.
What the structure needs to answer: Revenue being hedged, reference price, volume, delivery period, settlement method, and counterparty obligations.
Develop price protection for buyers’ future compute spend and operators’ revenue, including the period after an offtake ends.
What the structure needs to answer: The exposure and reference price, differences from actual compute prices, collateral, settlement, and any premium or fees.
Compare capacity by configuration, location, and term to inform underwriting and the value of remaining commitments.
What the structure needs to answer: Data provenance, comparable transactions, quote versus executed price, and the assumptions behind a valuation.
We have standing orders to purchase compute contracts that meet our pricing, terms, and technical specifications. We build ongoing relationships with suppliers as our inference needs and network grow.
We purchase capacity for our own inference workloads and for the startups and independent researchers in our network. Bring us existing capacity or a new buildout, including edge compute and other novel deployments. We agree the workloads, access arrangements, and onward-use rights directly with you.
Hardware, interconnect, storage, location, availability, and the rights you can offer.
Volume, duration, price, prepayment, service levels, and delivery obligations.
Tests, handover, and remedies agreed for the configuration before capacity is accepted.
We agree the hardware specifications and performance targets before handover. An initial test window is followed by final checks on the full cluster.
We welcome counterparties who buy and sell physical compute, source difficult allocations, or see a price and term that our book can work with.
Yes, we contract for our own clusters. The exception is some listings on the Orderbook from third parties, as we do not purchase colo or large-scale clusters ourselves.
Bring the contract or project. Capital partnerships can concern transactions originated by others as well as our own book. The role, financing availability, and terms depend on review of the specific deal.
Yes, where your agreement permits the proposed use. We need to establish the relevant resale, subletting, or assignment rights and obtain any required provider consent before proceeding.
We can assess a defined subset of nodes or a delivery window. It needs to work operationally and fit the supplier’s permitted allocation and access arrangements.
Our terms are set by our internal pricing models. We are happy to work with brokers that bring us listings that meet those, and can pay a referral fee.

A cluster coming online. A contract that needs capital. A position with room on the other side.