BlitzOS security

BlitzOS gives each workspace an isolated virtual machine. GitHub OAuth handles sign-in. Stripe handles payment, so BlitzOS never sees your card number. Browser traffic uses HTTPS. This page states only those observable boundaries. BlitzOS does not claim a compliance certification, formal audit, or security control that is not listed here.

How is a workspace separated?

Each workspace runs in its own isolated VM. The workspace has 80 GB of disk and a separate 50 GB durable volume.

How does sign-in work?

You sign in with GitHub OAuth. BlitzOS uses the GitHub identity returned by that flow to give you access to your account.

Who handles card details?

Stripe handles checkout and payment. BlitzOS does not receive or store your full card number.

How is browser traffic protected?

BlitzOS uses HTTPS for its public web pages, account flow, workspace interface, and public preview URLs.

What does BlitzOS not claim?

No compliance certification or third-party security audit is claimed on this page. This is a short description of product boundaries, not a security guarantee.