Enterprise
A browser fleet your platform team can govern
Panes inherits the L1fe platform's tenancy, entitlements, and metering — so adopting cloud browsers doesn't mean adopting a new security model.
Org → project → workspace
Tenancy isn't a label, it's the request path. Every session, action, and credential mint is scoped to a workspace inside a project inside your org.
Humans and agents, one model
Engineers use the console; agents use MCP tools. Both resolve to the same Keystone permissions, so access reviews cover everything that can touch a browser.
Metering through Garden
Usage flows into the platform ledger as panes.session.started events. Chargeback by project comes from the same data your finance stack already trusts.
Entitlement enforcement
Cloud mode delegates entitlement checks per request — concurrency limits and plan gates are enforced at the platform, not in client code.
Placement policy
Pin workloads to regions (iad1, sfo1, fra1 today) or talk to us about custom placement for data-residency requirements.
Operational visibility
Health endpoint, diagnostics panel, and live stage reporting from Omega — your SRE team sees what we see.
The console at scale
Built for the team, not the trial
Scope switching between orgs, projects, and workspaces is built into the topbar. Principals, session expiry, and live stage data are always visible — the console is an operations surface, not a demo.
Tell us about your workload
Concurrency targets, regions, compliance posture — we'll map Panes onto your requirements and be honest about what we don't do yet.