Dedicated silicon
A rented GPU is passed through whole — no MIG slices, no time-sharing, no co-tenants on the die. CPU cores, RAM and disk quotas are reserved, not oversubscribed.
Security
GPU cloud security posture, stated precisely
No vague "bank-grade" claims: this page lists exactly how tenancy, data, network and accounts are protected — and what we deliberately do not collect, which is most of what could leak.
Workload isolation
Container hardening
Non-privileged containers under a hardened runtime: user namespaces, seccomp and cgroup walls, read-only host surfaces. Your image's processes see your instance and nothing else.
VM boundary on demand
Full VMs add KVM hardware virtualisation with VFIO passthrough — kernel-level isolation for compliance-sensitive workloads, at the same price sheet.
Data protection
- At rest — instance disks and volumes encrypted (AES-256-XTS) with per-resource keys; destroy = key discard = cryptographic erasure.
- In transit — TLS 1.2+ on the console, API and every HTTP-exposed port; instance-to-instance traffic stays on the private fabric per region.
- Secrets — deploy-time env vars stored encrypted, masked in logs and UI; registry credentials likewise.
- No sneak backups — we never snapshot customer disks on our own initiative; what you do not snapshot does not exist twice.
Account security
- Passwords hashed with Argon2id; sessions are httpOnly, SameSite, server-revocable.
- API keys stored as SHA-256 hashes, shown once, revocable in seconds — key docs.
- Password change signs out every other session; bot traffic is filtered without fingerprinting humans.
Facilities
Every machine lives in an established colocation facility — never residential hosts, never "a rig in a spare room":
- Tier-III (or equivalent) design: redundant power, cooling and carriers;
- ISO 27001 / SOC 2 attested operations, 24/7 physical access control;
- per-site compliance documentation available under NDA for enterprise reservations.
What we do not collect
The cheapest data breach is the one that cannot happen:
- No IP address retention — not in logs, not in the database;
- no payment PII — crypto settlement carries no card, name or address;
- no third-party trackers, no analytics scripts, no ad pixels — check the page source;
- no sale or sharing of usage data, full stop — policy.
Disclosure & questions
Vulnerability reports: console ticket titled Security — routed straight to engineers, answered within 24 h, rewarded when it is real.
Is my workload isolated from other customers?
Yes — GPUs are dedicated (no MIG sharing, no time-slicing), containers run under hardened runtimes with their own namespaces and cgroups, and VMs add full KVM hardware virtualisation with VFIO GPU passthrough. Reserved capacity is single-tenant down to the chassis.
What happens to my data when I destroy an instance?
The disk is cryptographically erased: instance disks are encrypted at rest with per-instance keys, and destroy discards the key before the blocks are recycled. Volumes follow the same model when deleted.
How do I report a vulnerability?
Open a console ticket titled "Security" (any account, free) — it routes to the security engineers directly, first response inside 24 h. Good-faith research on your own resources is explicitly welcomed in our acceptable use policy; bounties are paid in crypto, naturally.