Skip to main content
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.

Projects

Separate environments, teams, or customers, each with its own browsers, profiles, credentials, and limits.

API keys

Create, scope, rotate, and delete the keys your code and agents use.

Spending caps

Set a monthly spending guardrail for your organization, a project, or both.

Audit logs

A year of API request history across your organization, searchable and exportable on Start-Up and Enterprise.

Firewall allowlist

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 per customer. Each project has its own browsers, profiles, credentials, proxies, and deployments.
  • A project-scoped API key per customer workload. A project-scoped key can only reach resources in its project.
  • A spending cap and a concurrency limit per project. One customer’s usage can’t exhaust your budget or your organization’s browser limit.
  • One profile per end user. Each user’s logins and browser state stay separate, inside their customer’s project.