Rent a whole GPU, by the second.
Whole machines from people who own the cards, launched with your own key and settled in euro to the microeuro.
Compute
- Whole machines, never a slice of one
- Metered per second, in euro, to the microeuro
- The rate is frozen when you match, not when you finish
- Seven GPU models, from a 24GB 4090 to a 141GB H200
The lineup
Power, work, optimise
Three products on one machine. Compute is the power, Studio is the work, and Autopilot optimises it.
A renter asks for a card. Compute matches one from the catalogue, brings it up, and the meter starts counting seconds.
Compute · live
Everything Compute, in one console
Pick a side, pick a card, and the shapes, the fleet, the split and the work it suits all answer together.
Three shapes, one meter
Serverless for spiky inference, GPU Cloud for a box that's yours, Clusters for multi-node runs, all under the same per-second meter.
Scales with the traffic
You never hold a machine: a call lands on whichever card is warm, runs, and releases. Nothing is billed between calls.
Good for
Spiky traffic, demos, and anything that sits idle most of the day.
If you are the one renting
Size it, launch it, stop paying
The Cookbook says which card a model needs and what an hour of it costs. Three commands take that card from nothing to settled.
- kracht v0.1.1 for linux/amd64checksum okinstalled /usr/local/bin/kracht
- Rented 8fa2c1d0 on h100-node-02 (eu-west) at 2.890000 EUR/hrBilling has started. Stop it with: kracht stop 8fa2c1d0
- 8fa2c1d0 is stopping. The provider picks this up on its next heartbeat, so `kracht ls` may still show it running for a few seconds. Billing stops at teardown.
Studio · planned
Studio is a canvas, so we made it one
Load a shape, click a step to inspect the card it holds, then switch to Trace to watch the agent itself: every plan, every tool call, every retry, timed and counted.
each step rents its own card, for exactly as long as it runs
Step
agent
The agent loop: plan, call a tool, read the result, decide again. Runs until it answers or hits its step limit.
Holds one card for the whole loop, however many times it goes round.
Autopilot · planned
Autopilot is a queue you work through
An inbox of findings, each with the metering that proves it, each waiting on you to approve or dismiss. It proposes; you decide.
A card held while waiting on a person
The review step holds an H100 for the whole time a human takes to look at the output. Utilisation is flat zero for that window.
What it costs you today
€37
The metering that proves it
The gate is the product. Autopilot never edits a running workload on its own. It writes a recommendation, attaches the metering it is based on, and waits for you.
The three findings keep costing what they cost.
The idle hold, the oversized card and the box nobody released.
Adds a ceiling per project and auto-release on idle.
A projection is not a promise. The chart starts today, from what you have actually spent. Everything on it is arithmetic on this month’s observed rate, not observation.
Worked example: one small account’s month, with sample daily figures that add up to the €842 the console states. The band is an illustrative range, not a confidence interval we have measured.
Roadmap
Now, next, later. Nothing dressed up.
Three columns, a live count on each, and a status chip on every item. Compute is finished; the other two you can look around today, and we will not pretend otherwise.
Compute, Shipped
Rent a whole GPU by the second, launched with your own key.
live on real hardware
Per-second metering, Shipped
Metered per second and settled in euro, to the microeuro.
real rentals settled
The 85/15 split, Shipped
Providers keep 85% of every second their card is rented.
exact-integer split
EU data residency, Shipped
Hardware and ledger inside the EU, priced in euro.
euro ledger
Studio, In progress
Wire many rentals into one workflow you can read back.
demo you can look around
Agent tracing, In progress
Spans, tool calls and tokens recorded for every run.
observability surface
Evaluation, In progress
Score a prompt set across models in one run.
designed
Autopilot, Planned
Find the spend you are not using, and stop it on approval.
designed, not built
Spend guardrails, Planned
A ceiling per project, and a warning before a run passes it.
designed
Auto-release on idle, Planned
Stop a rental when its job exits, once you have approved it.
designed
Keep reading
Where to go from here
Spin up a GPU, or earn from your own
Rent on-demand compute by the second, or list idle hardware and let it pay for itself. Same marketplace, both directions.
No card required
- 85%
- revenue to providers
- Per-second
- billing, live
- EUR
- metered to the microeuro