A persistent identity for every agent
Keep cookies, local storage and authenticated sessions safely attached to an isolated profile.
R
research-euCreated 42 days ago
● ReadyCookies84Sessions12RegionNL
The browser platform your agents can come back to.
Run, identify and network every browser agent from one control plane. Persistent profiles, residential connectivity and MCP access are built in.
Explore platform plans $3 / GB · 15% off from 50 GB Built for MCP Residential network included
WorkspaceBrowser profiles
Profiles12+3 this week
Live sessions04● Healthy
Browser hours186Current cycle
ProfileRegionStatus
Rresearch-euResearch agent
Amsterdam ReadyOops-usOps agent
New York ActiveQqa-sandboxQA agent
London ReadySession restoredresearch-eu
Agent connectedvia MCP
One browser layer for the tools your agents already use
ClaudeCursorOpenAILangGraphZapiern8n
One browser platform
Browsers shouldn't forget everything between runs.
Agents are useful when they can continue a job—not start from a blank session every time.
Ready when your agent is
Launch clean, isolated Chromium instances in seconds. Pause them without losing their state.
Stable regional networking
Route each profile through managed regional egress, including residential connectivity where needed.
Terminal
$ npx @locus/mcp connect --key $LOCUS_KEY
Locus connected · 8 browser tools available
$ claude
› Open my research profile and continue the vendor review.
Restoring profile “research-eu”...
MCP-native
One line between your agent and a real browser.
No browser fleet to operate. No profile persistence to build. Connect Locus to your MCP client and start using browser tools immediately.
- Remote MCP over HTTP
- Scoped keys per agent or team
- Residential network built into every profile
How it works
From zero to stateful browsing in minutes.
The browser layer stays out of your way until your agent needs it.
01
Connect
Add the remote MCP server to your agent with a scoped workspace key.
02
Create a profile
Choose a region and give the profile to a single agent or workflow.
03
Let it work
Your agent browses, returns later and continues with the same digital context.
Platform pricing
Pay for the traffic your agents actually use.
Every plan includes persistent browser profiles, MCP access and managed residential connectivity. Browser compute is included during beta.
StarterFor one production workflow
$30/ month
10 GBresidential traffic included
- 5 persistent profiles
- Unlimited agent connections
- Regional residential egress
15% volume discount
ScaleFor multi-agent operations
50 GB$2.55/GB · residential traffic included
- 30 persistent profiles
- Workspace access controls
- Multi-region residential egress
CustomChoose your expected volume
$255/ month
GB · volume pricing
15% discount is applied automatically from 50 GB. - Flexible profile limits
- Volume planning support
- Selectable residential regions
Choose a traffic plan to request a beta workspace.
Questions, answered
The browser layer, without the browser ops.
Persistent identity, networking and browser execution are managed as one platform.
A persistent browser environment for one agent or workflow. Cookies, local storage, sessions and preferences survive between runs, so your agent can pick up where it left off.
Locus exposes a remote MCP server designed for clients that support HTTP transport. Connect it once, assign a profile, and the browser tools become available to your agent.
Each profile can use managed regional egress, including residential routes where appropriate. The goal is stable, representative connectivity for legitimate agent workflows—not bypassing site protections.
Profiles are isolated per workspace and encrypted at rest. Scoped API keys control which agents can launch or reuse each profile. Detailed retention controls are on the roadmap.
Private beta
Your agents are ready.
Their browser should be too.
Choose the capacity you would put into production.
Compare platform plans