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

# Manage

> Organize, secure, and govern how your team uses KERNEL

Management settings apply across your organization rather than to a single browser: how resources are split between teams and environments, who and what can call the API, what happened and when, and how much you spend.

> [card] [Projects](https://www.kernel.sh/docs/info/projects.md)
>
> Separate environments, teams, or customers, each with its own browsers, profiles, credentials, and limits.

> [card] [API keys](https://www.kernel.sh/docs/info/api-keys.md)
>
> Create, scope, rotate, and delete the keys your code and agents use.

> [card] [Spending caps](https://www.kernel.sh/docs/info/spending-caps.md)
>
> Set a monthly spending guardrail for your organization, a project, or both.

> [card] [Audit logs](https://www.kernel.sh/docs/info/audit-logs.md)
>
> A year of API request history across your organization, searchable and exportable on Start-Up and Enterprise.

> [card] [Firewall allowlist](https://www.kernel.sh/docs/info/network-access.md)
>
> The KERNEL domains and ports to allow if your firewall restricts outbound traffic.

## Multi-tenant setups

If you run KERNEL on behalf of your own customers, combine these pieces so each customer is isolated and capped:

* **One [project](https://www.kernel.sh/docs/info/projects.md) per customer.** Each project has its own browsers, profiles, credentials, proxies, and deployments.
* **A [project-scoped API key](https://www.kernel.sh/docs/info/api-keys.md) per customer workload.** A project-scoped key can only reach resources in its project.
* **A [spending cap](https://www.kernel.sh/docs/info/spending-caps.md) and a [concurrency limit](https://www.kernel.sh/docs/info/projects.md#concurrency-limits) per project.** One customer's usage can't exhaust your budget or your organization's browser limit.
* **One [profile](https://www.kernel.sh/docs/browsers/profiles.md) per end user.** Each user's logins and browser state stay separate, inside their customer's project.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.