Origin
The idle-GPU problem
Compute is scarce for builders while useful hardware sits idle elsewhere, so we started building the market we wanted to rent from.
Two-sided since day one
market for compute.
Two people in Europe building the compute market we wanted to rent from: idle hardware earning its keep, renters paying by the second, and both sides reading the same ledger.
2
people, so far
2 paths
rent or list
per sec
metering
85%
to the provider
Two sides, one market
The marketplace we wanted to rent from
Rent by the second. Earn from idle hardware.
Live
Compute is live
The working half, today. Per-second, in EUR.
Explore computeEarly
Studio and Autopilot
Two more surfaces on top, still early.
What we are building
Compute should be easier to find and safer to share
What we do
Teams rent by the second; providers list GPUs they own. We handle the middle: matching, isolation, metering, payout.
- Renters pay per second, in EUR, with no minimum and no reservation
- Providers list the cards they own and keep 85% of every rental
- One ledger, and both sides read the same entries
Our story
From idle silicon to a compute market
30 July 2026
Launch, meter, settle
The first rental ran end to end on real hardware: launched, metered per second, and settled at the 85/15 split. Then the connect hop, reading files out of the running container.
3 August 2026
A renter's own shell
The first SSH login into a rental, one card scoped to it and the host's own sshd blocked from inside. Snapshot and restore proven the same day.
Trust layer
Isolation and teardown
Each rental on its own session network, single-tenant, its container destroyed at teardown. The provider bootstrap runs unattended from one command.
Next
Payments, then payouts
No real money has moved yet: every balance is credit granted by hand. The ledger arithmetic is proven; the rail is next.
The flywheel
A marketplace that compounds
More idle GPUs get listed
Owners turn dormant hardware into income.
Prices fall
More supply on the market pushes the going rate down.
More teams rent
Cheaper compute pulls in more builders and bigger runs.
Demand rewards owners
Higher utilisation makes listing even more worth it.
One market, three jobs
Compute makes GPU capacity available. Studio is the planned workflow surface above it. Autopilot is the planned approval layer that reads what the work costs.
Compute
Rent GPUs by the second from idle hardware, or earn from the cards you own. Priced at match, settled in euro.
Manage
plannedDraw the workflow and attach hardware to each step, then read a finished run back step by step.
Optimise
plannedSee what the work costs and where it's leaking. Simulates a change against what you already paid, applies nothing until you approve.
What we stand for
The promises we already gave up breaking
The parts that matter are written into the schema, where changing our minds later is a migration and a broken test, not a quiet edit.
How the rest is enforcedThe split stays 85/15
Providers keep 85% of everything their hardware earns. Not a launch offer, and not a number that quietly moves once there is enough hardware here to move it.
How it holds
- One number sets the rate, in one place, for the whole site
- The ledger divides at exact integers, so no cent goes missing in a rounding
- A test fails the build if the site and the ledger ever disagree
A price cannot change under a running job
The rate you agreed is the rate you pay, for as long as the machine runs. A provider putting their prices up cannot reach a job that is already going.
How it holds
- The rate is copied onto the rental the moment it is matched
- Billing reads that copy, never whatever the listing says today
- A rental that has started cannot exist without one
Every euro traces to a row
There is no balance field for anyone to edit. Ask why a number is what it is and the answer is the list of things that made it, not somebody's recollection.
How it holds
- Every charge and every credit is its own line, added and never rewritten
- A balance is the sum of those lines, not a figure stored beside them
- Any total can be taken apart into the rows it came from
Money is exact, and it is in euro
Per-second billing multiplies a rounding error by every tick, so there is no rounding to multiply. One currency, six decimal places, and the two halves of every split are required to add back to the whole.
How it holds
- An amount is never a floating-point number, anywhere between the meter and the ledger
- Payments are EU-native by design: iDEAL and SEPA through a European processor, not a card rail bolted on
- Only money a provider has earned can leave to a bank account; topped-up credit is spent on compute or stays
By the numbers
Small, exact, and honest about it
No dashboard of vanity metrics. Every figure here traces to the code.
01
2
people
the whole company
02
85%
to the provider
of what a card makes
03
3
products
on one market
04
6
decimals
the euro ledger is exact to
Where we actually are
Two people, and a working half of a marketplace
Everything above this is what we are trying to build; this is what is actually running today, and what is not.
Running today
- Real rentals have run end to end on real hardware, connect hop included
- Money settles per second, in euros, with the 85/15 split as integer arithmetic
- Balances are an append-only ledger, so a retried heartbeat cannot bill twice
- A dead host is detected and the rentals stranded on it are released
- Every push runs the full suite against a real Postgres, not a mock
Not yet
- Payouts to a bank account: the payment provider is not connected yet
- Uptime history, because there is no monitoring on the control plane to measure it
- SOC 2, ISO 27001, and a signed Data Processing Agreement
- A staging environment that does not point at the production database
- Any way to prove a host's firmware is what it claims before work lands on it
The team
The founding team
Kracht is two people. That is the whole company.
Ali
Edition 001
Co-founderBuy side
The side you buy from
Owns the product and everything a customer sees: the marketplace, the pricing, and the claims.
Austin
Edition 002
Co-founderRun side
The side that runs it
Owns the machinery: placement, the provider agent, and the settlement that moves the money.
Two sides, one marketplace
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