Production-grade custom browsers — enterprise internal browsers, kiosk shells, white-label products, crypto wallets. Not Electron wrappers that break on the next Chrome release.
The reasons clients pick us, in their own words. Each one is something most agencies will swear they do — and most don't.
Expertise01
Chromium engineers, not web generalists.
Browser internals require C++, IPC, and sandboxing knowledge. Not React developers who learned Electron last week.
Speed02
Fork it in two weeks.
We have a working Chromium base ready. You don't start from zero — you start from running.
Security03
Enterprise privacy by design.
Full network-stack control, built-in proxy support, certificate management. No third-party telemetry unless you put it there.
Distribution04
Your fork, your distribution.
Signed builds, auto-update infrastructure, and OS-native installers ready for Windows, macOS, and Linux.
Hard-won lessons
Why most browser projects fail.
Five mistakes we see in every browser project that didn't make it. None of them are visible at kickoff — all of them are fatal by month six.
01
✗
Electron when the project needs a fork.
A wrapper around web tech is the wrong base for a real browser product. Six months in, you hit a wall no plug-in can cover.
02
✗
No upstream-sync plan.
Without a milestone cadence to replay your patches onto new Chromium, your browser falls behind on security in 6 months.
03
✗
No code-signing plan.
The app gets blocked by Windows Defender or macOS Gatekeeper. Real users never see the install screen.
04
✗
No auto-update architecture.
Every patch becomes a manual reinstall. Your CVE-response time is measured in "please update" emails.
05
✗
C++ changes by web developers.
IPC breaks, sandbox escapes, crashes that don't reproduce. Browser internals are not a place to learn on the job.
✓
We've seen each of these on takeovers. None of them happen on our builds — they're scoped, planned, and budgeted from day one.
The receipts
Browser features we've shipped.
Not case studies. A raw list of specific browser features that only someone who has built browsers would know to ship. If it's on this list, we've done it in production.
F01✓Custom tab management & session isolation
F02✓Built-in password manager · OS credential store
F03✓Custom extension API · allowlist / blocklist enforcement
F04✓Hardware-accelerated video with DRM support
F05✓Proxy & VPN integration at the network-stack level
F06✓Custom certificate authority & SSL inspection
F07✓Kiosk mode · input filtering · crash recovery
F08✓Native OS notifications, system tray, auto-launch
F09✓Delta update system with rollback support
F10✓Per-tenant policy engine · 47+ controls
F11✓Hardened runtime · sandboxed renderer pinning
F12✓Telemetry pipeline you own, not Google's
Product types
Six browser types, one engineering bench.
The shapes of browser work we've shipped most often — each with the integrations we reach for first.
#
TYPE
WHAT IT IS
FEATURES
01
Enterprise internal browser
Locked-down, policy-managed, SSO-integrated browser for internal teams. Replaces Chrome on managed fleets.
POLICYSSOMDM
02
Kiosk & single-site browser
Full-screen locked browser for retail, hospitality, or public terminals. One URL, no escape hatches.
KIOSKLOCK-DOWN
03
Crypto & Web3 browser
Built-in wallet, dApp support, custom RPC management. Hardware-key support where the contract requires it.
WALLETRPCHW-KEY
04
Kids & parental control browser
Content filtering, screen-time, safe browsing built into the shell. Not a Chrome extension that can be disabled.
FILTERSAFE-BROWSE
05
White-label browser for SaaS
Embed a branded browser inside your product or desktop app. Your tabs, your shortcuts, your brand.
BRANDEDEMBED
06
Developer-tools browser
Custom devtools, debugging overlays, network inspection built for engineering teams. Chromium with the gloves off.
DEVTOOLSOVERLAY
Version strategy
The Chromium version question.
The question every serious buyer has and nobody answers publicly. Five answers, in writing.
We default to the latest Chromium stable channel at kickoff. For long-lived enterprise builds we ship on Chromium ESR-equivalent (an LTS branch we maintain), with a documented upgrade window every six months. The decision is made in week 1 of discovery and written into the contract.
Platforms
Platforms we ship for.
Desktop and mobile by default. Signed, notarized, and packaged for the way real users actually install software — including the enterprise IT teams behind them.
Windows● SHIPPED
Windows 10 · 11 · Server 2019+
MSIXMSIEXE installer
SIGNING
Authenticode · EV cert
EXTRAS
Group Policy ADMX templates · MDM-ready
macOS● SHIPPED
macOS 12 Monterey and above
DMGPKGauto-mount installer
SIGNING
Apple Developer ID · notarized
EXTRAS
Hardened Runtime · sandbox entitlements
Linux● SHIPPED
Debian / Ubuntu · Fedora · Arch
.deb.rpmFlatpakAppImage
SIGNING
GPG signed repos
EXTRAS
systemd integration · XDG-portal compliant
Android● SHIPPED
Android 10+ · API 29 and above
APKAABPlay bundle
SIGNING
Play App Signing · upload key
EXTRAS
Play Integrity · in-app updates · MDM-ready
iOS● SHIPPED
iOS 15+ · iPadOS
IPATestFlightApp Store
SIGNING
Apple Developer · distribution cert
EXTRAS
ATS hardened · enterprise MDM · OTA updates
Engagement shape
From idea to ARR in four phases.
A typical browser engagement, end-to-end. Code signing and upstream sync get scoped at week one — not bolted on after launch.
W01–02
Discovery & architecture
Define browser type, target OS, Electron vs CEF vs Chromium fork decision, distribution strategy, upstream-sync plan. Fixed quote at end of week 2.
W03–08
Core build
Shell, navigation, tabs, extensions API, custom UI, OS integration. Working beta on staging by week 6; first signed installer by week 8.
W09–11
Harden & distribute
Code signing (EV, Apple Dev ID, GPG), auto-update pipeline, crash reporting, notarization, installer build, default-browser handler, telemetry.
W12+
Maintain & evolve
Upstream Chromium sync every milestone, security patches, feature iteration, enterprise policy updates. Long-term retainer with the team that built it.
Stack
Browser stack. Battle-tested.
Each row below has been load-tested across 14+ real browser shipments. Predictable, hireable, debuggable.
No hourly retainer that bills for 'thinking time.' Pick a lane that matches your stage; everything is fixed-quote or transparently rated.
Browser MVP buildShip fast
Browser in 8–12 weeks.
For founders shipping their first custom browser
For teams who need a working production browser — not an Electron wrapper. Fixed scope, fixed quote, senior-only team. Code signing and auto-update pipeline included from day one.
·Chromium fork or Electron architecture from line one
8–12 weeks for a Chromium-fork MVP on Win/macOS/Linux with signed installers. Add 2–4 weeks for enterprise policy engines, self-hosted update servers, or built-in wallets. Electron-based products usually land in 6–10.
Yes. We've built on Brave (the Omni Browser is a Brave fork) and we can fork Edge as long as Microsoft's licensing terms are clear for your distribution. We pick the base on the discovery call — not by reflex.
Every milestone (~6 weeks), we replay your patches onto the new Chromium release, resolve conflicts, run the build matrix, and ship a signed update. CVEs get hotfix branches. You stay current without owning a Chromium team.
All five by default: Windows, macOS, and Linux on desktop; Android and iOS for Chromium-based mobile. Signed and notarized — Authenticode + EV on Windows, Apple Developer ID + notarization on macOS, GPG repos on Linux, Play App Signing on Android, and App Store distribution on iOS.
Yes — we've shipped all three. VPN inside Omni Browser, Omni Crypto Wallet inside the address bar, AI side-panels inside Brave-based forks. The hard part is doing it without breaking upstream sync; that's the job.
EV cert + Authenticode on Windows, Apple Developer ID + hardened runtime + notarization on macOS, GPG-signed packages on Linux. Auto-update via Squirrel/Sparkle or our custom delta updater — including a self-hosted update server when the contract requires it.
Founder-direct
Plan a browser buildthis quarter.
Free 30-minute architecture call with a senior Chromium engineer. By the end you'll have an engine recommendation, a distribution plan, and a realistic ship date — whether you hire us or not.