LoginSchedule demo
cedana / blog · field reports & engineering deep-dives

Writing from the
cedana team.

Engineering notes, benchmarks, and field reports covering how we build the automation layer for AI factories.
Featured
Blueprint schematic of an eight-GPU node accumulating session state, with a state gauge rising toward the VRAM capacity lineBlueprint schematic of an eight-GPU node accumulating session state, with a state gauge rising toward the VRAM capacity line
FeaturedEngineering

The Era of Stateful Inference: How to Improve Cost per Token.

We are entering the stateful inference era, driven by frontier models with longer context windows, longer in-flight sessions, and single instances spanning 8, 16, or more GPUs.

Updated · Cedana Editorial
read →
All posts · 98

insights from the team.

Field reports, engineering deep-dives, and benchmarks from the Cedana team.

TopicGPU costs

Cedana. Blueprint of two fractions. On the left, marked cost per token, a receipt icon sits over a line with a row of twelve blue dots beneath. On the right, marked revenue per megawatt, the same row of blue dots sits over a line with a lightning icon beneath. A blue dashed curve joins the two rows of dots, marked tokens delivered.
· Cedana Editorial

Cost per token and revenue per megawatt are the same number

Calculate cost per delivered token from fleet costs and serving logs, then see how cold starts, failures and stranded capacity also affect revenue per megawatt.

read →
Cedana. Blueprint of a fraction. Above the line, twenty-four small outlined boxes marked four dollars per GPU-hour, twenty-four hours billed, the first eight and last four hatched grey and two of the middle ones capped dark. Below the line, columns of blue ticked squares marked tasks finished stand under the middle boxes only.
· Cedana Editorial

Tasks per dollar: the economics of running your own coding models

Compare coding APIs and self-hosted GPUs using cost per completed task. Account for idle node hours, model swaps and task completion on your own traffic.

read →
Cedana. Blueprint of a power line running flat, stepping down at a bolt-shaped signal, holding a lower level with the reduction hatched beneath the original line, then stepping back up. Under it a grey band runs unbroken across the whole width, and beneath that three blue bars stop at the signal, three saved-state icons sit in the gap, and the bars resume at the return.
· Cedana Editorial

Demand response for GPU fleets: what the programs require

Review two GPU demand response trials, the workloads they could flex, and why deeper power cuts require saved job state. Separate trial results from design targets.

read →
Cedana. Blueprint of a conveyor belt with rollers running from a cloud outline on the left to a tall rack on the right. Four crates ride the belt, each with a small glyph on its face: a heartbeat line, three stacked bars, three coins, a ticked page. The first three carry a small grey tag on their lids; a grey dashed arrow above the belt points toward the rack.
· Cedana Editorial

Sovereignty has a bill: the transferred duties and the availability math

Size the availability responsibilities of running inference on your own hardware, including spare capacity, recovery time and a single node's outage allowance.

read →
Cedana. Blueprint of one long grey bar marked one gpu-year with a thin blue slice at its left end. A leader drops from the slice to the words the fee, and beneath them five point seven points to break even.
· Cedana Editorial

How much utilization improvement do you need to break even on GPU checkpointing?

Calculate the utilization gain needed to cover a GPU checkpointing fee using your operating cost, paid hours, restore cost and recoverable work.

read →
Cedana. Blueprint of a month as thirty outlined squares in a grid, each one a billed day; inside most of them a blue block rises to a different height, the share of that day's hours that produced finished work, and a few squares stand empty.
· Cedana Editorial

Which utilization number goes into your own-versus-rent calculation?

Compare owning GPUs, renting nodes and paying per token using delivered GPU-hours, operating costs and utilization instead of demand forecasts alone.

read →
Cedana. Blueprint of one wide rectangle, a month's GPU bill: the left two fifths hatched grey for hours nothing ran on, the rest grey for hours the dashboard called busy, and inside that busy part a dark sliver and a red-hatched sliver at its left edge, hours spent loading and recomputing, before a solid blue block for the hours that produced work kept. A single ruled rate line runs under the whole width.
· Cedana Editorial

How to put a dollar figure on the GPU-hours that produced nothing

Calculate the cost of idle GPUs, cold starts and recompute using your own hourly rate. Separate paid busy time from work your fleet actually keeps.

read →

Showing 7 of 7 posts