Projects
Separate environments, teams, or customers, each with its own browsers, profiles, credentials, and limits.
Workload identity federation
Let CI jobs and cloud services authenticate with short-lived tokens instead of stored API keys.
API keys
Create, scope, rotate, and delete keys for local development and workloads that can’t federate.
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 federation rule or a project-scoped API key per customer workload. Each one can only reach resources in its project. Prefer a federation rule where the workload has an identity provider, so there’s no key to store.
- 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.