GPU solutions forevery workload.
Build, train, and deploy across compute, storage, networking, and serving without the lock-in.
The problem
GPU access is broken. We fixed the market.
Compute is the scarcest resource in AI, yet most of the world's GPUs sit idle. Kracht connects both sides and sets a fair price in real time.
FIG 01 routing
job · model + region
The request: a GPU model and a region, both catalogue codes, never a machine. Where it lands is placement's decision.
Renting GPUs today
- H100s sold out, with waitlists before you can train
- Hyperscaler rates above the silicon's worth, with long lock-ins
- Egress fees and opaque minimums you only find on the invoice
- Quota requests and sales calls just to get started
- No idea which step of a pipeline is holding the expensive card
- You find the waste on the invoice, a month after it happened
- Your own GPUs sit idle, depreciating, earning nothing
A two-sided compute market
- Listed GPUs you can launch on now, running in under 20 secondsclaim: asserted by us, with nothing behind it yet
- Market-set prices, 53% to 68% under list for the exact same card
- Per-second billing, no egress, no minimums, no lock-in
- Sign up and kracht launch, with no tickets or gatekeeping
- Each workflow step holds its own card, and an idle step holds none
- The metering behind your invoice, read back as where it leaked
- List unused GPUs and turn idle hardware into income
One platform, three layers
Rent the metal. Build on the rest.
Compute is live today. Studio and Autopilot stack on top of it, same account, same meter. Click a layer to open it.
Compute
LiveRent GPUs by the second from idle hardware, or earn from the cards you own. Priced at match, settled in euro.
Explore ComputeThe comparison
The honest math on a rental.
The same card, priced by the market instead of a margin. The 15% we keep is the same number on every page and in the ledger.
Renting elsewhere
Kracht
The same H100
Billing
Egress and minimums
Time to start
Your runtime
Where the money goes
- A 7m job on an H100: €0.34 per second, €2.89 billed hourly.
- A 20m job on an H100: €0.96 per second, €2.89 billed hourly.
- A 41m job on an H100: €1.97 per second, €2.89 billed hourly.
- A 52m job on an H100: €2.50 per second, €2.89 billed hourly.
- A 1h10 job on an H100: €3.37 per second, €5.78 billed hourly.
- A 1h34 job on an H100: €4.53 per second, €5.78 billed hourly.
- A 2h04 job on an H100: €5.97 per second, €8.67 billed hourly.
- A 2h30 job on an H100: €7.22 per second, €8.67 billed hourly.
- A 2h52 job on an H100: €8.28 per second, €8.67 billed hourly.
illustrative · list rate × job length, from the one price list · 1 square is 10 minutes of the card
Use cases
Built for the way your team works.
One market, four ways in. Pick the seat that is yours to see what Kracht does for it.
Researchers
Experiments that end when you do.
Per-second capacity with transparent per-team billing, so you never pay for an idle card.
Startups
Skip procurement, keep the runway.
No quota forms, no sales calls, no lock-in, on GPUs 53% to 68% under a hyperscaler's list price.
Teams
Endpoints that scale to zero.
Traffic-following endpoints that cost nothing while idle and stop the meter when demand does.
Providers
Idle GPUs become income.
List spare hardware and earn 85% of what it makes, paid per second onto an append-only ledger.
One CLI, every surface
One command. Every surface.
Describe the job once and launch it from the CLI, the API, the dashboard or your pipeline. Same meter, same ledger, wherever it starts.
$ kracht launch --gpu 1 --region eu-central \ --image pytorch/pytorch \ --command python train.py
Waiting for it to finish provisioning...
root@3f9a1c2b7d4e:~#
{ gpu_count: 1 }
200 · billed / sec
pick an image →
Launch · billed per second
--command ./train.sh
✓ ends when it exits
Rented 8fa2c1d0 on h100-node-02 (eu-central) at 2.890000 EUR/hr Billing has started. Stop it with: kracht stop 8fa2c1d0
Trust and security
Security your team can sign off on.
Every rental carries the same guarantees, so legal, finance and security can evaluate Kracht without a call.
the fence · isolated by default
The rental has its own session subnet. The host's sshd has a route toward it, drawn here as the grey wire, and that route ends at the fence.
Frequently
asked questions
No. You rent a whole host, launch it with one command, and tear it down when the job is done. There is no cluster to babysit and nothing to provision ahead of time.
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