Peerd
A browser extension that turns Chrome/Firefox into a private, local AI agent workstation.
A technically impressive, privacy-first agent harness that rethinks the runtime from the browser up. It's best for developers and tinkerers who want local control and understand trade-offs—it's early-stage, requires technical comfort, and lacks a polished UI. Consider BrowserUse or Playwright if you need a more mature automation framework; use Claude Code for terminal-based coding. Peerd's unique value is its browser-native architecture and zero cloud dependency.
- Developers who want a local, private AI agent that can control their browser with real session state.
- Power users needing agent-driven automation without data leaving their machine.
- Privacy-conscious individuals avoiding cloud-based agent services.
- Tinkerers exploring browser-native agent architectures and P2P agent coordination.
- Non-technical users seeking a plug-and-play AI assistant.
- Teams needing multi-user collaboration or cloud-hosted access.
- Enterprises requiring centralized management, audit trails, or compliance.
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Peerd if you need a polished, one-click AI assistant or a cloud-hosted automation service with team collaboration and enterprise management.
You must provide your own API keys for cloud models (Anthropic, OpenRouter) if you don't use local Ollama—those have their own usage costs.
Peerd is open source and completely free—no tiers, no upsells. If you need a browser-based agent and are willing to provide your own API keys, it's the cheapest option possible. Managed cloud alternatives like Browserbase or Playwright MCP charge per execution or monthly; Peerd costs only your compute resources.
In short
Peerd — A browser extension that turns Chrome/Firefox into a private, local AI agent workstation. Best for Developers who want a local, private AI agent that can control their browser with real session state., Power users needing agent-driven automation without data leaving their machine., Privacy-conscious individuals avoiding cloud-based agent services.. Free to use.
Viability Score
How likely is Peerd to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →Key Features
- Browser extension for Chrome and Firefox
- Mediated browser tool access (tabs, sessions, pages)
- Bring your own model key (Anthropic, OpenRouter)
- Local model support (Ollama, Web LLM upcoming)
- Local voice transcription via WebGPU (Moonshine)
- JS notebooks running in sealed Web Workers
- WebAssembly Linux VMs (CheerpX, full Debian)
- Agent memory, planning, subagents with budgets
- Peer-to-peer agent-to-agent via WebRTC
- Ed25519 identity and Kademlia DHT discovery
- Create and share local artifacts and apps
- No background process or cloud server
- No telemetry, data stays on client machine
- Uses browser security model (V8 isolates, SpiderMonkey Realms)
- Open source under Apache 2.0, uncompiled JavaScript
About Peerd
Peerd is an open-source browser extension that transforms your existing browser into a full-fledged AI agent workstation—no background processes, no cloud servers, and no telemetry. It runs entirely client-side, using your browser's own security model (V8 isolates, SpiderMonkey Realms) to give an AI agent mediated control over your tabs, sessions, and pages. You bring your own model keys (Anthropic, OpenRouter) or run local models via Ollama. The extension provides five primitives: Act (browser control), Think (model routing, subagents, memory), Compute (JS notebooks, WebAssembly Linux VMs), Build (artifacts, apps), and Share (P2P agent-to-agent via WebRTC). Unlike AI browsers like Comet or cloud automation services like Playwright, Peerd adds agent capability to the browser you already use, sharing real session state. It's built for developers, power users, and privacy-conscious individuals who want local, private agent automation. Currently pre-release, installable as an unpacked extension from GitHub; Chrome Web Store and Firefox AMO submissions are pending.
Behind the Verdict
Peerd is one of the most architecturally interesting AI agent projects right now. It makes a strong bet: the browser itself—already running on billions of devices with hardened sandboxes, crypto stacks, and network protocols—is the ideal runtime for AI agents. Instead of bolting on a separate service, Peerd lives entirely in a Chrome or Firefox extension, sharing a process with your real browser session. This means it can see what you see, use your logins, fill forms, and run computations in isolated V8 workers or even a full Debian VM compiled to WebAssembly. There's no external process, no cloud middleman, no telemetry. You bring your own API key for Anthropic or OpenRouter, or run local models via Ollama. Its five-module architecture—Act, Think, Compute, Build, Share—is well thought out. The P2P agent-to-agent protocol over WebRTC with Ed25519 identity and Kademlia DHT is genuinely novel, enabling distributed agent coordination without any central server. The security model is also a standout: Peerd writes zero lines of crypto, sandboxing, or process-isolation code, inheriting everything from the browser's decades of hardening. However, Peerd is not for everyone. It's clearly aimed at developers and tinkerers. The extension is pre-release; there's no one-click install from web stores yet—you need to clone the repo and load it unpacked. The UI is minimal, documentation is thin, and there's no built-in multi-user or team support. Non-technical users will find the setup barrier too high. Performance is also tied entirely to your machine, so heavy local model inference or many concurrent VMs can be sluggish. Where Peerd shines is for a specific niche: developers who want a local, private agent that can automate web workflows using their real browser session. If you're already comfortable with command-line tools and want to experiment with browser-native agent architectures, Peerd is fascinating. If you just want to automate a task quickly, existing cloud services or frameworks like Puppeteer are more mature.
Researching Peerd? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Peerd actually fits — and what changes day-one when you adopt it.
You need to fill a web form with data from a local CSV. With Peerd, you open the side panel, tell the agent to read the CSV (via JS notebook or local file), then instruct it to navigate to the form, fill each field, and submit—all using your real logged-in session.
Outcome: The agent completes the data entry in minutes without you touching the keyboard, and all data stays local.
You want to scrape a list of product prices from an e-commerce site without sending any data to a cloud service. You install Peerd, provide no API key (use local Ollama), and instruct the agent to open the site, extract prices into a notebook, and save the output as a local JSON file.
Outcome: You get the scraped data with zero data leaving your machine, using local inference only.
You want to experiment with two AI agents communicating directly. You install Peerd on two machines, generate an Ed25519 keypair on each, and use the Share primitive to discover and connect them via WebRTC. The agents exchange messages and coordinate a task (e.g., one agent fills a form, the other checks the result).
Outcome: You have a working prototype of peer-to-peer agent collaboration without any cloud infrastructure.
Use Cases
- Automate web workflows using your own browser session and logged-in accounts.
- Run local data analysis by spawning JS notebooks or Linux VMs in your browser.
- Build a personal AI assistant that can fill forms, browse, and act on your behalf privately.
- Prototype agent-to-agent communication using WebRTC between two Peerd instances.
Models Under the Hood
as of 2026-07-06
Limitations
- Peerd is a pre-release browser extension, so it depends on your browser's capabilities and permissions.
- It does not provide a hosted API or cloud backend; all computation is local, so performance is tied to your machine.
- There is no built-in multi-user support.
- The project is early-stage and may have limited documentation.
- Installation currently requires cloning the repo and loading an unpacked extension—no one-click store install yet.
- The UI is minimal and developer-focused.
as of 2026-07-06
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Peerd tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0
Ideal for
Developers and privacy-conscious users who want a free, local AI agent with no limitations.
What this tier adds
Starting tier: free, open source, all features included, no paid upgrades.
Where the pricing makes sense
The company stage and team size where Peerd's pricing actually pencils out — and where peers do it cheaper.
Peerd is open source and completely free—no tiers, no upsells. If you need a browser-based agent and are willing to provide your own API keys, it's the cheapest option possible. Managed cloud alternatives like Browserbase or Playwright MCP charge per execution or monthly; Peerd costs only your compute resources.
Setup time & first value
How long it actually takes to get something useful out of Peerd — broken out by persona, not the marketing-page minute.
For developers: about 10 minutes to clone the repo, load the unpacked extension, enroll a passkey, and add an API key. Non-technical users may take 30+ minutes due to lack of one-click install. First task (e.g., reading a page) is immediate after setup.
Resources & Guides
Official links
Tools that pair well with Peerd
Common stack mates teams adopt alongside Peerd, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Alternatives to Peerd
View all
Presto Voice
Drive-thru voice AI automation for QSR chains to boost revenue and efficiency.
Popular in Developer Infrastructure
Temporal AI
Durable execution platform for building reliable AI agents and workflows.
Frequently Asked Questions
Used Peerd? Help shape our editorial sentiment research.