DEFAULT PROFILEUNTOUCHED
Your existing browser
Chrome / Edge · current profilecookieshistorysaved logins
WINDOWS-FIRST · OPEN SOURCE · IN DEVELOPMENT
Keep browser statein a Silo of its own.
VeriSilo launches Chrome or Edge with a separate, managed data directory for every Silo. Cookies, storage, cache, service workers, permissions, and history stay in that environment—not in your default browser profile.
Public development build. No signed installer is available yet.
MANAGED DATA DIRECTORY
SILO 01ACTIVE
Work.silo
…/silos/{id}/browser-datacookiesstoragecacheworkers
SILO 02READY
Research.silo
…/silos/{id}/browser-dataLaunch evidence
--user-data-dir=<managed path>✓STATESeparate by directoryNot a cookie switcher
DEFAULT PROFILENever selectedNot imported or mutated
EVIDENCEFacts before scoresApplied is not yet verified
THE ISOLATION PATH
One boundary, three explicit steps.
A Silo is a browser-owned data directory plus the settings and evidence needed to explain how it was launched.
- CREATE
Define a Silo locally
The desktop app records the Silo metadata, browser choice, and explicit network profile. Its encrypted vault protects VeriSilo metadata and seed material—not the browser’s entire profile.
Local vault · no cloud account - LAUNCH
Start a separate browser directory
Chrome or Edge receives a dedicated user-data directory through an argument-array launch. The existing default profile is never selected, copied, or modified.
Browser-owned state · separate path - VERIFY
Inspect what can be proven
The optional Companion observes browser-context signals, explains capability limits, and creates local redacted reports. A Silo works without the extension.
Optional extension · evidence on demand
THE EVIDENCE MODEL
“Protected” is a result, not a marketing adjective.
VeriSilo separates what it can control from what it can only observe—and what a normal browser launcher or extension cannot change at all.
Read the capability modelA control earns its state
- CONFIGURED
- APPLIED
- VERIFIED
Separate browser data directory
Created and launched by the desktop core, with direct path and process evidence.
WebRTC preference and page signals
Useful observations with browser, page, timing, permission, and context limits kept visible.
TLS, QUIC, hardware identity
Outside the honest boundary of a normal Chrome or Edge extension and launcher.
LOCAL BY DESIGN
The isolation core stays on your machine.
The desktop app owns the boundary. Chrome or Edge owns the browser files. The Companion adds explanations and user-triggered checks without becoming the isolation mechanism.
Open the architecture notesTauri desktop
Creates Silos, discovers browsers, launches safely, and keeps one active Silo in V0.1.
Browser data
Cookies, LocalStorage, IndexedDB, cache, service workers, permissions, and history remain browser-owned.
MV3 Companion
Observes page context, verifies supported controls, and exports local redacted reports after confirmation.
Reports are not synced to a VeriSilo service. User-triggered network checks contact disclosed third-party endpoints and reveal the request IP to those providers.
THE HONEST BOUNDARY
What VeriSilo refuses to pretend.
Transparent limits are part of the product. Browser-state separation is useful without inventing claims the implementation cannot prove.
No device impersonation
It does not turn one physical machine into a different device.
No fraud or policy bypass
It is not built to evade account controls, restrictions, or site security.
No network-stack rewrite
It does not control TLS, HTTP/2, HTTP/3, QUIC, or every DNS path.
No “undetectable” promise
Page observations and best-effort settings always retain their limits.
SOURCE AVAILABLE NOW
Inspect the claim before you trust it.
VeriSilo is being built in public under MPL-2.0. The source, product boundaries, tests, and release gates are open for review while the first signed Windows build is prepared.