RentGPU.eu

Trust and verification

GPU rental in Europe needs proof before scale.

RentGPU starts as a reviewed private beta, not an anonymous open marketplace. The goal is to connect paying clients with European GPU capacity while making partner identity, hardware proof, payment status, and API maturity explicit.

Partner verification

A five-level path from application to production.

L1

Application review

Capacity partner submits operator type, EU location, GPU model, network capacity, tax country, and contact details. This is the minimum level for private beta intake.

L2

Identity and business check

Company or individual identity is reviewed, and VAT or tax information is recorded when available. No public listing should advance without a clear accountable operator.

L3

Hardware proof

Capacity partner shares verifiable GPU evidence such as the read-only RentGPU diagnostic report, nvidia-smi output, driver version, CUDA capability, benchmark sample, and timestamped screenshots.

L4

Network and access pilot

A supervised test session checks that access can be provided safely, reliably, and without exposing the host directly to the public internet.

L5

Production host agent

Future level for capacity partners running the RentGPU host agent with heartbeat, session status, metering, and policy-controlled access.

Marketplace tiers

Three badges explain what kind of partner is behind a slot.

Tier badges are routing signals for private beta review. They are not final legal certifications, and every real workload still goes through manual confirmation before access.

Community

Community reviewed

Operator and hardware claims are reviewed manually. Best for experiments, benchmarks, and non-sensitive work.

Typical partners
Home labs, indie operators, small GPU rigs
Best fit
Experiments, benchmarks, non-sensitive workloads
Checks
Operator contact, location, GPU proof, manual approval

Verified

Verified partner

Partner identity and hardware evidence are reviewed before matching. Suitable for controlled private-beta pilots.

Typical partners
Research groups, consultancies, reviewed operators
Best fit
Private-beta pilots with accountable counterparties
Checks
Identity/business review, hardware evidence, access model review

Tier-3 EU

Tier-3 EU facility

Capacity is associated with a reviewed EU datacenter-style environment or Tier-3/Tier-4 facility claim.

Typical partners
EU datacenter or Tier-3/Tier-4 style facilities
Best fit
Compliance-sensitive workloads that need stronger operational controls
Checks
Facility claim review, access boundaries, network and availability checks

Private beta boundaries

What RentGPU will not pretend.

Clear boundaries matter more than polished promises. The first version is designed to learn from real capacity partner and client conversations without overstating automation that is not live yet.

No anonymous self-serve supply in Phase 0.
Phase 0: manual matching, no automated billing.
No host-agent install or open inbound ports required in Phase 0.
No custody of private keys or seed phrases.
No automatic escrow until the smart contract path is implemented and reviewed.
No public access to partner machines without manual approval.
No claim that every GPU listing is instantly available.
No fake success responses from preview agent APIs.

Access model

Partners stay in control of access.

Phase 0 is manual brokerage, not instant cloud provisioning. RentGPU learns which access model is safe for each capacity partner before any client is introduced.

Provider-managed workspace
JupyterHub, SSH bastion, Slurm login node, temporary account, or another workflow the partner already controls.
Provider-run batch job
The client packages the workload and the partner runs it when direct external access is not appropriate.
Dedicated VM or container
Only for partners that already support safe isolation, teardown, and account lifecycle management.
Future host agent
Parked for Phase 2. Not required for the current private beta and never installed without explicit agreement.

Payments

Manual settlement first. Escrow only after proof.

During validation, clients and capacity partners coordinate direct USDC transfers on Base L2 under manual supervision. RentGPU records settlement evidence, but does not custody funds or run automatic escrow in Phase 0.

Phase 0
Manual USDC settlement on Base L2. Pavel supervises introductions and records evidence. Platform fee is 0% during validation.
Phase 1
Planned smart-contract escrow with a clear split between partner payout and platform fee. Target only after manual rentals prove demand.
Phase 2
Planned fiat paths such as SEPA or card payments for teams that cannot use USDC directly.

Agent API status

Agent-readable does not mean production-ready.

RentGPU is being shaped for agents and automated workloads. The current API surface is intentionally marked as preview until real host allocation, metering, payment, and session lifecycle controls are implemented.

/skill.md
Live instruction page for agents and automation builders.
/api/v1/heartbeat
Preview endpoint. Honest status until the host-agent exists.
/api/v1/sessions/rent
Preview endpoint. No fake allocation before real booking and payment infrastructure exists.
/api/v1/mcp
Preview endpoint for the future agent control surface.

Data and jurisdiction

EU-first, GDPR-aware, legal review pending.

The product is designed around European supply and an EU-hosted database. Formal legal documents are still part of the pre-commercial launch checklist, so the site avoids claiming final certification too early.

Supabase project is hosted in eu-west-1, Ireland.
Waitlist and capacity partner application data are used for matching supply and demand.
Partner tax and payout fields are collected for pilot record keeping and future DAC7/VAT readiness.
Private keys, wallet seed phrases, and cloud credentials must never be submitted to RentGPU.
Formal Terms, Privacy Policy, and Provider Agreement still require legal review before broad commercial launch.

Decision gates

The next phase only starts after evidence.

Partner review UI
3+ serious capacity partner applications in the queue or at least one known partner ready for a pilot listing.
Phase 1 escrow work
5 completed manual rentals through Telegram handshake plus satisfaction score of 7/10 or higher from both sides.
Broad promotion
3+ serious capacity partner applications or one real pilot partner with a manually verified access path. Internal HOMEPC testing does not count.