Every major AI model, running in your real Chrome. No third-party subscriptions.
A browser agent that drives the Chrome you’re already logged into — and lets you choose Claude, GPT, Gemini, Grok, Llama, or Mistral on a per-task basis. We deliver the model, the agent runtime, and the MCP context layer through one LiteLLM gateway. Hosted in Helsinki, built on the open stack — every layer on GitHub under MIT or Apache‑2, every byte in EU-only data residency. No Anthropic Pro / Max sub per user. No eight-vendor inference bill. No US data plane.
You and the agent, watching the same Chrome.
Other agents work in a sandbox you can't see into. SiteBridge runs in your real Chrome — every screenshot, every click, every keystroke shows up in a live trace you can read, intervene on, or hand off to a colleague. Pick a workflow below and press play.
Press ▶ run agent and you'll see every step in plain English — what it read, what it clicked, what it screenshotted. You and the agent watch the same trace.
Built and hosted in EU. On the open stack.
Every visible competitor has a US opaque-box runtime at the bottom. We built the opposite — every layer open-source, every byte in EU data residency, your security review can reach all of it. Anthropic can spin up a Frankfurt subsidiary; their data plane still terminates in us-east-1.
One product — every model that matters.
Claude beats GPT at one thing. GPT beats Claude at another. Gemini wins on long context. Grok wins on speed. Llama is the only thing that runs in your VPC. With SiteBridge through LiteLLM, you don’t pick one — you get them all, route per task, and try the new release the day it ships.
Browser navigation: find-button-and-click. Doesn't need reasoning. Route to the cheapest fast model — that's most of agent traffic.
Plus any new model added to LiteLLM the day it lands. Customers don’t sign a new contract or wait for procurement — we add the deployment, they benefit silently.
Primitives are commodity. The operations layer isn’t.
Five field leaders, same five verbs: navigate, click, fill, read, screenshot. The primitive layer plateaus in twelve months. Value moves up the stack — to the layer that takes eighteen months of incident data to build.
What none of them ship:
- Pre-click expectation guards — refuse if dialog text doesn’t match the agent’s intent.
- Undo snapshot ring buffer — answer “what did the agent do?” after the fact.
- Cross-session selector learning — don’t rediscover the same button on day forty-seven.
- Compound wait-aware tools — one round-trip instead of three.
- Model-agnostic via LiteLLM — route to any provider, route by complexity, route to self-hosted.
- Real domain integrations — Smartling, n8n, Confluence, Google Docs, Jira.
Pre-click expectation guard, live in your hands.
Type what the agent intends. Type (or pick) the dialog the page shows. Watch the guard accept, refuse, or escalate. Same logic that gates every click in production.
The pre-click guard compares the agent's stated intent to the dialog actually shown. Hidden swaps, prompt-injected destructive verbs, and ambiguous confirms get caught here — before the click goes through.
Save changes to comment? Your draft will be preserved.
For the tools you actually use.
Generic browser agents see a page of pixels. SiteBridge ships domain modules that know each tool’s shape, vocabulary, and quirks — and surface only when you’re on that tool. No toolbar clutter, no wrong suggestions, no “please describe your workflow” onboarding.
Atlassian — Jira, Confluence, Bitbucket
Smartling — translator’s cockpit
n8n — workflow co-pilot
Google Docs — long-form fluency
WordPress — content, not curl
Chrome — the hardened foundation
Roadmap is open: customer asks for tool X, we ship a domain module for tool X. The same week, usually.
Gets smarter every day. Keeps your data off the wire.
The three questions every serious team asks of an agent: does it learn? where does my data go? can other tenants see anything? SiteBridge has an opinionated answer to all three — wired into the runtime, not bolted on.
Self-improving with every conversation
Patterns up · data down
Secrets stay on your machine
Your users don’t need a Claude Code sub. We deliver the whole stack.
Claude for Chrome ships the agent — and the bill. Every user needs Anthropic Pro, Max, Team, or Enterprise. Every team needs Anthropic billing in their procurement. SiteBridge through Agiliton’s LiteLLM gateway collapses that into one vendor relationship and one inference bill — and gives you cost, privacy, and failover knobs Anthropic-direct doesn’t.
One bill, one vendor
Cost: complexity-routed
Failover built in
Privacy: route to on-prem
The capabilities modern teams actually ask about.
Six rows from the full matrix. Tap through to see all seventeen.
| Capability | SiteBridge | ClaudeforChrome | PlaywrightMCP | BrowserMCP | DevToolsMCP |
|---|---|---|---|---|---|
| Bundled with model + agent runtime (no third-party sub) | ● | ● | ● | ● | ● |
| Runs inside your real logged-in Chrome | ● | ● | ● | ● | ◐1 |
| Works with any LLM provider (no model lock-in) | ● | ●2 | ● | ● | ● |
| Local-only data path possible | ● | ●3 | ● | ● | ● |
| Pre-click safety guards (expectedTarget, viewport check) | ● | ● | ● | ● | ● |
| Undo log + DOM snapshot ring buffer | ● | ● | ● | ● | ● |
Pick the angle that closes your room.
The stack →
Open-source end-to-end, EU-hosted, auditable. Architecture diagram, request flow, cost math, twelve concrete benefits.
Features →
17 capabilities, 5 vendors, 6 footnotes. The killer slide.
Numbers worth memorizing →
Six stats, every one sourced. 11.2%, 114k → 27k, 500+50, 30+, 5, ~10×.
Objections →
Four “yes but…” answers, sourced. Anti-FUD.