BlitzOS security

BlitzOS gives each workspace an isolated virtual machine. Google OAuth handles sign-in. 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, with its own disk and its own durable volume.

How does sign-in work?

You sign in with Google OAuth. BlitzOS uses the Google identity returned by that flow to give you access to your account. BlitzOS requires a verified email address on the Google account.

How is browser traffic protected?

BlitzOS uses HTTPS for its public web pages, account flow, workspace interface, and team 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.