Security at GlassPalace

GlassPalace is built around an intentionally powerful agent. Our architecture treats that runtime as untrusted to the host and isolates it from provider secrets and other workspaces.

Workspace isolation

Every workspace receives a separate gVisor-sandboxed pod and persistent volume. Tenant namespaces use deny-by-default networking, admission controls, resource limits, and no direct public ingress.

Credential boundary

OAuth refresh tokens, API keys, managed model keys, and BYOK credentials remain encrypted in central services. The agent sees stable aliases and a short-lived workspace identity, not upstream secrets.

Authorization and approvals

Ory Kratos authenticates identities. PostgreSQL membership and role checks authorize every workspace path. High-impact provider actions pause with an immutable payload for explicit approval and are written to an audit trail.

Responsible disclosure

Please send security reports to security@glasspalace.uno. Include reproduction steps and avoid accessing data that is not yours.

Beta limitation

The public beta does not yet include off-node backups. Storage loss can permanently remove agent state; this limitation is distinct from our controls against cross-tenant access.