Volspan Compute is designed for teams that take security seriously. Here is how we protect your data and your GPU runs.
Your GPU run code is sent directly to the compute instance and executed. We store only a SHA-256 hash of the code for audit purposes. The code itself is never persisted in our database.
API keys are hashed with Argon2id before storage. We store only a 12-character prefix for display purposes. Full keys are shown once at creation and cannot be retrieved afterward.
BYO RunPod API keys and Slack webhook URLs are encrypted with AES-256-GCM before storage. Encryption keys are managed via environment variables and never committed to source control.
Each GPU run executes in an isolated container on RunPod infrastructure. Containers are destroyed after execution. stdout and stderr are stored in R2 and accessible only to the run owner.
All workspace events are logged to an immutable audit trail: member changes, project modifications, GPU budget updates, and anomaly detections. Available to workspace admins.
Questions about security? Contact [email protected]