Katana
Coming soonmacOS first

One browser. Every session.

Katana lets you browse normally and test in isolated sessions side by side — with built-in proxying, session tooling and controlled agent access.

Katana browser window with DAILY and TEST tabs

Daily / Test

Your normal browser and your testing browser are the same browser.

Katana keeps everyday browsing and isolated test sessions side by side in the same window.

Use DAILY tabs for normal work. Use TEST tabs when you need isolated identities, proxy routing and session control.

Katana

Daily

Gmail
GitHub
Docs

direct · signed in

Test

app.target.com — Admin
app.target.com — User
app.target.com — Clean

isolated sessions · proxy aware

Identities

Test the same application as multiple users at the same time.

Open the same target as Admin, User, another tenant or a completely clean session — without signing out, switching profiles or launching another browser.

Each TEST identity has its own isolated session context.

AdminUserTenant BClean session
Katana identity switcher showing Admin, User A and a new clean session

No profile switching. No disposable second browser.

Clean session

Start clean in one click.

Need a fresh state? Open a temporary Clean session for fast reproduction and isolated testing.

When the last Clean tab closes, the session goes away with it.

Workflow

Sessions become something you can work with.

Katana turns browser session state into a first-class testing workflow.

Inspect

See the state of the current session.

Clone

Branch a session before testing.

Snapshot

Save a known authenticated state.

Compare

See what changes between identities.

Katana cookie inspector showing session state for the Admin identity

Cookies, auth state and session context should not live hidden deep inside the browser.

Proxy

Every test session knows where its traffic goes.

Route each test context through Caido, Burp, SOCKS or a custom upstream and always see the effective route of the active tab.

AdminCaido
UserBurp
CleanDirect
Katana proxy menu with Direct, System, Caido, Burp, SOCKS and custom upstreams

Proxying that follows the session.

Agent access

Let your agent use the browser session you already have open.

Most automation launches a separate browser with a separate session.

Katana is designed so tools like Claude Code or Codex can work with the page, session and context you are already using — with explicit permissions.

Allowed / controlled access

  • Page
  • Interact
  • Network

Restricted by default

  • DAILY
  • Other identities
  • Sensitive session data

Who it's for

Built for people who need more than one browser context.

Pentesters

Multi-user testing, authenticated flows, session comparison

QA

Role-based testing and clean-state reproduction

Developers

Multiple accounts, staging, debugging through proxy

Red teams

Controlled identities and operational browser workflows

Blue teams

Investigation and reproducible browser contexts

Why Katana

Testing workflows should be browser primitives.

Typical workflow
Katana
Multiple profiles / incognito
Isolated identities in one window
Proxy extension
Native proxy-aware workflow
Cookie editor extension
Session tooling built in
Logging in and out repeatedly
Side-by-side sessions
Separate automation browser
Controlled access to current session

Technical note

A real browser, not a wrapper.

Katana is built on a modern browser foundation, allowing session isolation, networking, cookies and agent access to integrate directly into the browser experience. Chromium underneath. macOS first.

Katana is coming soon.

We’re building Katana now. The first release will focus on macOS.

Get notified · Follow development