> ## Documentation Index
> Fetch the complete documentation index at: https://docs.krait.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

> Krait is organized around 'workspaces'. A workspace represents an isolated security boundary where scans, integrations, users, and billing are managed together.
This model allows a single client to manage multiple independent environments which allows multiple teams, products, or business units to work under one Krait account.

## What Is a Workspace?

A **workspace** is a logical container that includes:

* Connected repositories
* Security findings and compliance reports
* Team members and access roles
* Subscription limits and billing

All scans, results, and compliance reports are **scoped to a specific workspace**.

## Multiple Workspaces per Client

Each client can create **multiple workspaces** within their Krait account.

This is useful when you want to:

* Separate production and non-production environments
* Isolate different teams or departments
* Manage multiple products or customer environments
* Apply different subscription tiers to different workloads

Each workspace operates independently, even if owned by the same client.

## Subscription and Limits per Workspace

Subscriptions are applied **per workspace**, not per account.

The selected workspace tier determines limits such as:

* Number of repositories that can be connected
* DeepScan credits
* Number of team members
* Availability of advanced features (e.g. developer insights, custom scheduling, SLA alerts)

This means:

* One client may run a **Premium workspace** for production
* And a **Basic or Playground workspace** for testing or internal use

## Billing Model

Billing in Krait is **workspace-based**.

* Each workspace has its own subscription plan
* Charges apply per workspace on a monthly basis (except free tiers)
* Upgrading or downgrading a workspace affects only that workspace

This provides predictable costs and clear separation of spend across teams or projects.

## Team Members and Access

Clients can invite team members into a workspace.

Key points:

* Members are added **per workspace**
* Access is limited to the workspace they are invited to
* Different workspaces can have different team compositions

This enables fine-grained access control and prevents accidental cross-environment access.

***

## Why Krait Uses a Workspace Model

The workspace model allows Krait to deliver:

* Clear isolation of security data
* Flexible subscription management
* Scalable usage across teams and environments
* Cleaner audit and compliance boundaries
* Enterprise-friendly billing and access control

Workspaces are the foundation of how Krait scales security and compliance across organizations.