The browser where your AI workforce actually runs.
On your machine. Not ours. Never your password.
Buffer, HubSpot, Zapier — they all need your passwords sitting on their servers. We refuse to. Solace Browser is a Chromium fork you download once and leave running, like Slack. Your AI workforce executes inside your already-logged-in Gmail, LinkedIn, GBP, Facebook, Substack. Cookies stay on your machine. OAuth3 vault, revocable in 1 click.
Why I built my own browser.
Every AI tool I tried required typing my passwords into someone else's server. Chrome extensions can't hold OAuth sessions cleanly across tabs. None of them respected revocation. So I forked Chromium. Solace Browser is what I wished existed: my AI workforce runs INSIDE my browser, on my machine, with my session — and I can pull any worker's access in 1 click. No one else's server holds my passwords. Ever.
— Phuc Vinh Truong, founder
Sherri at Kumon Quincy installed it on her audit call with Phuc. The next morning, new-mover postcards started shipping — without her ever typing her Mailchimp password into a SaaS dashboard.
How it works
Three steps. You do them once. Then it runs in the background while you do other things.
1 · Install + log in
Download Solace Browser after signup. Launch it. It opens automatically to a 6-step login wizard — starting with solaceagi.com (auto-issues your API key) then your channels: Gmail, LinkedIn, GBP, Facebook, and any other platforms your bundle uses.
2 · Leave it running
Solace Browser stays open in the background like Slack. The yinyang sidebar polls solaceagi.com every ~30 seconds for activities your AI workers have queued for you. You see the queue per-domain.
3 · Click Run (or auto-run)
When activities are ready, click Run all (or enable auto-run for low-risk activities). Solace Browser executes them in your native sessions — posts a LinkedIn, replies to a GBP review, sends a newsletter — and posts the result back with a screenshot for evidence.
OAuth3 — what Buffer, HubSpot, and Zapier can't do
Those tools need your passwords sitting on their servers. OAuth3 is our extension of OAuth2 with three additions that make delegated access honest — and that none of them implement:
Scoped + time-bounded
Instead of 'allow Solace to access my LinkedIn forever,' OAuth3 says 'allow Solace to publish to my LinkedIn page during business hours, with monthly review.' Tight, expirable, explicit.
Customer-revocable in 1 click
Go to /dashboard/connections, click Revoke, and that channel's session is invalidated across all your devices instantly. Solace can no longer act on that channel until you re-grant.
Sessions stay native
Because Solace Browser runs on YOUR machine, your cookies + session tokens never leave your computer. Compare to Buffer or HubSpot, which require you to type credentials into THEIR server. We never see them.
What we see — and what we don't
Honest line-by-line. Our home Solace Hubs do what only a server can do. Your browser does what only YOU can do — with your sessions, your cookies, your machine.
On Phuc's home Solace Hubs
• LLM content generation (Scribe drafts posts in your voice) • Image rendering (Pixel designs postcards + tiles) • Voice + video generation (Echo + Reel) • Planning + scheduling (Conductor recipes) • KR refresh + alerts (Pulse + Mira) • Stripe billing, email queues, postcard mailing via Lob API • Activity queueing for your browser to pick up
On YOUR Solace Browser
• Publishing posts to LinkedIn / Facebook / Instagram / X • Replying to Google + Yelp + social DMs • Anything that touches an OAuth3-protected platform • Holds your API key in OS keychain • Sidebar shows pending activities + override controls • Saves a screenshot + tamper-proof record of every action it takes
Why we built our own browser
Extensions can't hold OAuth3 sessions cleanly
Chrome restricts what extensions can do with cookies + sessions across tabs. A custom browser owns the full browser session lifecycle — clean separation between your data and ours.
The yinyang sidebar needs space
Right-side panel that lives ALONGSIDE your tabs — not a popup, not a sidebar that fights with Chrome's UI. Pinned + persistent + domain-aware.
Source-available + auditable
Solace Browser ships under the Functional Source License (FSL) — readable by anyone, convertable to OSS after 4 years. The 6 custom files are about 300 lines on top of vanilla Chromium. Audit the diff yourself.
No phone-home telemetry
Standard Chromium has Google telemetry + auto-update. Solace Browser strips both. Updates are opt-in. No background reports to anyone.
See it in action
Four moments from a real Solace Browser session: the login wizard, the yinyang sidebar holding pending activities, execution mid-flight, and the receipt log every action writes.
System requirements
Linux
Ubuntu 22+ or Debian-based. ~500 MB disk. ~200 MB RAM. .deb package, ~150 MB.
macOS
macOS 12+ (Apple Silicon or Intel). ~500 MB disk. .dmg installer, ~160 MB.
Windows
Windows 10+. ~500 MB disk. .exe installer, ~170 MB.
All three builds share the same Chromium fork + Solace overrides. Updates ship as in-app prompts (opt-in; never forced). No telemetry leaves your machine.
Honest answers
Do I have to install Solace Browser?
Yes — that's how your AI workforce executes work without ever holding your passwords. Customers who skip the install will see queued activities accumulate but nothing publishes to their channels until they install + log in.
What if I leave the browser closed?
Activities queue up. When you next open Solace Browser, the sidebar shows everything pending and you can Run-all in one click. We recommend leaving the browser open in the background — like Slack — so your AI workforce can ship 24/7 without delay.
Can I use my regular Chrome too?
Absolutely. Solace Browser is purpose-built for the AI-workforce queue; you keep using Chrome / Safari / Firefox for everything else. They coexist on your machine.
What data does Solace see?
Just the screenshot + a tamper-proof record of what YOUR browser did on YOUR behalf (stored in your private tenant repo on GitHub). We do NOT see your passwords, login cookies, or any channel-side data that isn't a direct result of the action we just took.
How do I revoke access?
Two ways. (1) /dashboard/connections → click Revoke on a specific channel → that channel's OAuth3 scope is invalidated. (2) Uninstall Solace Browser → everything stops; your queued activities don't ship until you reinstall.
What if a channel logs me out?
Solace Browser's sidebar polls each channel nightly. If a session expires, we surface an alert on your dashboard + send you an email + ping you via Twin chat. One-click re-login restores everything.
Do my teammates each need their own?
Only the people who own the channel sessions. If your social manager owns LinkedIn + GBP, she installs Solace Browser and logs in once per channel. The rest of the team uses your dashboard on Chrome/Safari/Firefox — viewing the queue, approving drafts, reading receipts. No per-seat pricing; we bill per worker, not per chair.
Stop typing your passwords into other people's servers.
Book a 30-min audit with Phuc. On that call, your 1-year plan gets built on a real calendar. Then download Solace Browser, log in once per channel, and watch your AI workforce ship in the background — same budget, up to 10× more output.
Book your audit call with Phuc → See pricing → Calculate your savings →Your first 30 days include:
- 30-min audit call with Phuc (not a BDR) — $500 value
- Your 1-year plan, built live on that call — $5,000 consulting value
- Solace Browser activated on your machine — $499–$999 setup, waived during launch
- 5–15 AI workers shipping the plan, Phuc on call — your monthly tier
- Revoke any worker's access in 1 click — OAuth3 included
Total value: $7,000+. Today: $0. Cancel any month — keep the 1-year plan even if you walk.
Source-available under FSL · 4-year OSS conversion · No telemetry · Sessions stay native · 1-click revoke · Phuc personally onboards every operator.