5 docs tagged with "security"

Lium can store the pod's local volume at /root as ciphertext on the provider's disk. Inside the running pod, it looks like a normal filesystem.

Lium strictly prohibits access to its compute from US embargoed countries and by sanctioned parties, and runs thorough checks to ensure that Lium compute is never accessible to anyone in a restricted area. The prohibition covers every Lium service — the lium.io platform, the API, the CLI, the SDK, and any GPU node connected to Lium.

Scam and impersonation attempts against Lium users are becoming more common. This page explains how those scams usually work, what information you must never share, and the safest way to contact Lium support.

Do not upload private keys, seed phrases, API keys, or other secret files to a rented pod. The GPU provider may have access to the pod environment.

This page is the supported way to run a model or a dataset that the GPU provider must not see. You rent a Confidential Computing machine, the pod proves from the inside what machine it is on, and only then does a key service you control release a short-lived key that decrypts your data. Nothing secret is stored in the image, the template or your Lium account.