Reclaim by obligation

Stop paying for work that's already done.

You pay to keep resources ready - then keep paying long after the work they were ready for is done. Codrexi reconciles every system that knows when that work has cleared, and reclaims the instant it's provably safe.

Reconcile, not aggregate. Observe, not orchestrate. Reclaim, not wait on timers.

The leak

The bill is the distance between done and noticed.

Most of what a resource costs, you spend after its work is done. It stays on the bill for one reason - an obligation still gates it - and the proof that the obligation has cleared lives in another system, so the spend runs on a timer nobody revisits.

Dashboards aggregate and leave you to referee - they tell you how much, never whether it's safe to stop. Timers just guess.

The primitive

This is a Twin - one canonical record per hot resource.

Every field carries its sources, the value each one reported, a conflict flag, and a confidence score. Codrexi resolves the disagreement to one answer, receipts attached.

app.codrexi.com / twins / gpu-pool-7c4
reconciling sources resolver auto · receipts on jk select · r flash verdict

Interactive demo - click a resource on the left. Figures here are illustrative.

Three principles

A position on truth, scope, and timing.

Most tooling reports cost after the fact. Codrexi takes a position on each, and acts while there's still spend to stop.

01

Reconcile, not aggregate

One answer with receipts beats six panels and a judgment call.

02

Observe, not orchestrate

We don't run your operation; we tell it the truth about itself.

03

Reclaim, not wait on timers

A clock can't know when an obligation is met; a field-level record can.

A Twin is the unit. Multiply by your stack.

Anything you pay to keep ready becomes a Twin. Whatever decides when it's safe to let go becomes its gates. Describe them once, and the savings compound across everything you run.

compute
reserved GPU between renders
reclaim-safe0.97
failover
replica kept warm for a failover that already happened
reclaim-safe0.95
license
idle license seats
reclaim-safe0.94
storage
dataset past its deletion clock
holding · 1 gate0.78
environment
staging fleet awaiting sign-off
holding · 1 gate0.83
+ your vertical

Each is its own Twin, its own reclaim - the same machinery behind every one.

Pays for itself

One Twin pays for the watch; a stack of them is the return.

You stop renting capacity you no longer owe anything to.

Reclaiming sooner and reclaiming safely are the same move.

The record that says "let it go" is the record that proves why - so every release is defensible before anyone asks. A timer guesses: too early, it breaks something you still owe; too late, you pay the gap. The Twin acts when the obligation clears, receipts in hand - so the spend stops at the clear, not at the next sweep.

Private beta

Bring the obligations. Keep the receipts.

If you're paying to keep resources ready long after their reason has passed, let's talk. We're onboarding a small group of teams - request access, and we'll map your first vertical together.