Security

Account access

Members sign in with KolaOS or your identity provider. Roles and workspace membership are checked on every request.

Workstation access

Browser, SSH and preview connections are authorized outside the workstation.

Workstation isolation

Each member's workstation is a dedicated virtual machine with hardware isolation.

AI provider credentials

Organization AI provider keys never enter a workstation.

Organization roles and workspace membership determine access. The API checks membership on each request, and personal access tokens have scopes, expiry and optional resource restrictions.

Connections start from single-use links, and KolaOS keeps checking open connections. Revoking access closes a member's open connections within a minute.

Offboarding revokes a member's credentials before stopping or deleting their workstations.

Workstations accept connections only through KolaOS. They can't reach each other or cloud metadata services, and the rules that stop them are enforced on the host, outside the workstation.

Developers have full control inside their workstation. Access, organization credentials and the audit log are controlled outside it, where a developer can't change them.

Whoever operates the hosts can reach the workstation data on them. On KolaOS Cloud, that is KolaOS. Run KolaOS on your AWS account or your own servers to keep host operation inside your organization.

KolaOS adds organization AI provider keys outside the workstation and sends those requests only to the providers your organization configures.

Prompts and responses sent through KolaOS are recorded, and recording can't be turned off. Only organization admins can read prompt records, every read is audited, and admins choose how long records are kept. On KolaOS Cloud and your AWS account, records are stored in KolaOS-managed storage in your region. On your own servers, prompt text stays on your servers until an admin opens a record.

Customer content can pass through hosted services for the features you use. Review the privacy policy before sending sensitive content.

Admins can review audit events for access, connections and administrative changes. Reading a prompt record creates an audit event.

Standard customer telemetry contains allowed operational metadata and excludes code, prompts and session transcripts. Organization admins control sharing.

See telemetry for the collection settings and storage limits.

Contact hello@usekolaos.com to discuss deployment boundaries, security questionnaires, subprocessors, retention and contractual service commitments. Review the data processing addendumfor processing terms and deployment schedules.

Confirm any required certification, independent audit report, data residency guarantee or service level in writing before procurement. A product page is not evidence of a certification or a contractual commitment.

The documentation provides technical details for your review.

Email hello@usekolaos.com with the affected component, steps to reproduce and expected impact. Share only the minimum information needed, and ask for a secure transfer method before sending sensitive material.

Do not include credentials or customer content in an initial report. Coordinate testing with us before accessing other customers' resources or disrupting the service.