Permanently funded compute

Software that
outlives its owners.

corpusAI builds your service from its GitHub repository, redeploys it on every push, and funds it from one USDC deposit. The deposit becomes a position: principal that is never spent, and a buffer beside it. Yield on the position pays the monthly compute bill.

Illustrative position
To fund
$20,014
One USDC deposit: principal plus buffer
Priced at
7.24%
The yearly rate positions are credited
Monthly cost
$105/mo
$1,260 per year
Coverage
1.15×
Break-even at 6.3% yield

Use cases

What is worth endowing.

Anything with a small, predictable, indefinite bill and no natural owner to keep paying it.

Keepers and liquidation bots

Critical to a protocol, funded out of somebody’s discretionary budget, and quietly the first thing cut.

Monthly cost$45
To fund$8,577

Autonomous agents

An agent with a monthly inference budget becomes a permanent participant instead of a demo with a runway.

Monthly cost$200
To fund$38,122

RPC nodes and indexers

Public read infrastructure that everyone depends on and nobody has a business model for.

Monthly cost$350
To fund$66,713

Oracles and price feeds

Feeds whose value comes entirely from never stopping, which is exactly what recurring funding cannot promise. One we run: corpusAI Cloud Pricing, cloud and GPU prices sold per request over x402 →

Monthly cost$120
To fund$22,873

Archives and static sites

Documentation, datasets, and records that should outlive the person who published them.

Monthly cost$15
To fund$2,859

Public-goods infrastructure

Anything currently living grant cycle to grant cycle, converted into a position that does not need renewing.

Monthly cost$600
To fund$114,365

How it works

How an endowment funds compute.

Four steps. The first two happen once; the last two repeat every month for as long as the position is open.

[ 01 ]

Price

We model the workload’s compute cost and its variance against expected net yield, then size the principal with a buffer that absorbs both moving against you.

[ 02 ]

Fund

You deposit the price once, in USDC on Ethereum mainnet. corpusAI records it as a position in two parts: principal, which is locked and never spent on compute, and a buffer, which can be.

[ 03 ]

Accrue

Deposits are swept to corpusAI’s treasury, a Safe the operator controls, and the operator deploys them to yield venues. Yield accrues to the position on corpusAI’s ledger, on principal and buffer together.

[ 04 ]

Pay

Each month the ledger moves the position’s yield into its buffer and pays the machine’s monthly cost out of the buffer. No entry spends principal on compute.

The model

The whole product is one equation and a buffer.

A workload that costs C per year needs a principal that throws off C per year, and a buffer alongside it with enough headroom to survive a bad stretch of yield.

P = k · C / r
Price to fund
coverage = P · r / C
Coverage ratio
CAnnual compute cost
rYearly rate positions are priced and credited at: 7.24% today
kBuffer multiplier for yield and price variance
PPrice to fund

At k = 1 the coverage ratio is exactly 1.0, which means no headroom against a single bad quarter. Every figure quoted on this page uses k = 1.15.

The treasury today

8.85%
Treasury yield, trailing 30 days
4.69%
Ethena sUSDe · 13% of the treasury
9.47%
infiniFi 13-week notes · 87% of the treasury

Measured on-chain from each venue’s share value, Aug 28 to Sep 27, 2026, and updated daily. Each position’s principal sits in infiniFi and its buffer in sUSDe, and the blend weights them by that split. Positions are priced at 7.24% and credited that rate whatever the treasury earns.

Price to fund at k = 1.15, by monthly cost and rate r
Monthly cost4%6%8%12%
$15$5,175$3,450$2,588$1,725
$30$10,350$6,900$5,175$3,450
$75$25,875$17,250$12,938$8,625
$150$51,750$34,500$25,875$17,250
$500$172,500$115,000$86,250$57,500
$1,500$517,500$345,000$258,750$172,500

FAQ

Questions worth asking.

A serious buyer will ask all of this before they email. It is better answered here.

Funding is USDC on Ethereum mainnet.

Each checkout gets its own deposit address, a forwarder contract that can only send its balance to corpusAI’s treasury. Card payments are not available.

The position is on corpusAI’s ledger.

Your deposit is a public Ethereum transaction. The position it funds, its principal, its buffer and every monthly settlement, is recorded on corpusAI’s ledger, not on-chain. The machine’s funding tab shows the principal and the current buffer.

The operator holds the keys.

Deposits are swept to a treasury Safe controlled by corpusAI’s operator, who deploys it to yield venues and sends every withdrawal. That is custody, and we name it rather than soften it: today you rely on corpusAI to hold and run the treasury.

Principal and buffer sit in different venues.

Each position’s principal goes into infiniFi’s 13-week locked notes and its buffer into Ethena’s staked USDe (sUSDe), about 87% and 13% of the treasury at k = 1.15. The notes take 13 weeks to unbond, which is why a withdrawal gives 91 days’ notice. sUSDe exits after a cooldown of about 7 days, and the buffer it holds covers about two years of a machine’s bills. Most of the treasury sits in one protocol, so a failure at infiniFi would reach the principal behind every position.

Venues can lose money.

Both are on-chain protocols with smart-contract risk. infiniFi’s locked notes pay more because they absorb losses first: in a bad-debt event they are cut before other holders lose anything. sUSDe’s yield comes from Ethena’s hedged positions and falls when funding rates do. A loss at either venue would reduce the capital behind positions. The ledger does not model one, and nothing insures against it.

Positions are credited at the priced rate.

Today every position is credited 7.24% a year on its principal and buffer, the rate it was priced at, whatever the treasury earns. When the treasury earns more, the excess stays in the treasury. When it earns less, as the trailing figure in the model section shows it can, corpusAI makes up the difference. That is how the ledger works today, not a promise about what the venues will pay, and it is one more way a position depends on corpusAI.

Compute prices can rise.

The buffer is sized against price drift as well as yield variance, and the monthly cost is fixed on the position when it is funded. A structural repricing of the workload is a re-underwriting: adding principal by the same equation quoted above. We would rather quote that than pretend otherwise.

Withdrawal takes notice, and a request is final.

Ask from the funding tab and you get back the principal plus the buffer balance on payout day, in USDC, 91 days after the request. The machine runs until the payout is sent, then stops. A request cannot be canceled, and the 91 days is a floor: a venue’s redemption queue can add to it.

Today a position depends on corpusAI.

The treasury, the ledger and the hosting bill are all run by corpusAI, so a position lasts as long as corpusAI operates it. Roadmap, not built: an on-chain endowment that anyone can read, with a permissionless harvester, so a position no longer depends on the company that set it up.

Get started

Fund something that does not need funding again.

corpusAI is in private beta. Tell us the workload and its monthly bill, and we will send an invite with a principal, a buffer and the stressed case in writing.