Security

#Isolation

Each job runs in its own container under the NVIDIA runtime, rootless, with no host mounts and no access to the host network. GPUs are never shared between jobs: no MIG slicing and no time slicing.

#What is wiped, and when

• GPU memory is cleared when a job leaves the quench stage.
• /scratch is a per job encrypted volume, and its key is destroyed at quench.
• Host memory used by the job is zeroed before the next job is placed.

#Where data lives

In Iceland, in F1, with nightly snapshots to a second building on the same campus. Iceland is in the EEA, so GDPR applies. We do not read your data, sell it or train on it.

#Keys

API keys have scopes: read, run and admin. They are hashed at rest and shown once. Rotating a key keeps the old one valid for 15 minutes so running scripts can switch. Every call is logged with key id and request id, visible to team owners for 90 days.

#Transport

TLS 1.3 for the API, console, job endpoints and feed. SSH for sessions goes through our gateway with your key.

#The building

Badge and biometric entry, cameras on every aisle, staff on site around the clock. Drives leaving the building are shredded on site.

#In one page

Trust and security summarises all of this, lists our subprocessors and says plainly which certifications we do not hold yet.

#Reporting a problem

See Contact. We answer security reports within one business day and do not act against good faith research.