We don't wrap Chrome in a skin. We modify Chromium at the source level — custom rendering pipelines, enterprise policy engines, embedded browser shells, and purpose-built browsers for industries where off-the-shelf isn't an option. Chromium development services for teams that need a browser as a product, not as a dependency.
Why Entalogics for Chromium
Chromium has 35 million lines of code. Most teams that fork it can't keep their fork rebased past two upstream releases. We've maintained production Chromium forks across dozens of upstream updates — the discipline isn't in the initial modification, it's in the merge strategy that keeps it alive.
A default Chromium build includes sync, translate, extensions, and dozens of services your product doesn't use. We strip unused components at the GN flag level — smaller binary, less memory, faster cold start on the hardware that actually runs it.
CEF for embedding a browser into a desktop app. WebView2 for Windows-native browser embedding. Chrome Extensions for surface-level customisation. Source-level modification only when the API layers genuinely can't do what you need. We pick the lightest approach that solves the problem.
Every Chromium modification is a maintenance commitment. We structure patches as isolated, rebased changesets against upstream milestones. When Chrome ships a security fix, your fork gets it in days — not months of manual conflict resolution.
Mojo IPC for inter-process communication. `base::` types instead of STL where Chromium expects them. Memory safety via `raw_ptr`, `base::SafeRef`, and Chrome's clang plugins. Building inside Chromium means following Chromium's rules — not fighting them.
When Chromium, when not
Forking Chromium is easy. Maintaining that fork is where teams fail. We'll tell you on the first call if a source fork is justified — or if CEF, WebView2, or an extension gets you there without the maintenance cost.
FORK CHROMIUM WHEN
USE CEF OR WEBVIEW2 WHEN
WE SAY NO WHEN
What we build in Chromium
The shapes of Chromium development work we deliver most. Each built to survive upstream updates — not just the initial build.
Locked-down browsers with policy-enforced restrictions — no downloads, no dev tools, no URL bar, SSO-integrated, MDM-compatible. Built for regulated industries.
Single-purpose browsers for retail, hospitality, and healthcare kiosks. Locked to approved URLs, auto-restart on crash, remote configuration, touch-optimised.
Chromium rendering inside a C++, .NET, or Java desktop application via CEF. Browser functionality without building a full browser — reporting dashboards, HTML-based UIs, embedded documentation viewers.
Stripped telemetry, integrated VPN, built-in ad blocking at the network level, custom certificate handling. Chromium rebuilt for privacy as a product feature.
Browser shells on Linux-based embedded devices — automotive infotainment, smart displays, industrial panels. Chromium compiled for ARM, stripped to minimum footprint.
Inherited a Chromium fork that's 15 milestones behind? We rebase your patches, resolve conflicts, update to the latest stable, and establish a repeatable merge workflow.
The playbook
Chromium patterns from maintained production forks — not one-off builds that rot.
P01
Every modification is an isolated, documented patch against upstream. Clean rebase on each milestone update. No monolithic diffs that become unmergeable.
P02
Disable unused features at the build system level — sync, translate, safe browsing, extension system — before they add binary size and attack surface.
P03
Chrome's enterprise policy infrastructure used for product-level controls — URL allowlists, download restrictions, proxy configuration, authentication enforcement. Policy, not preferences.
P04
New browser services wired through Chromium's Mojo IPC layer — the same way Chrome's own services communicate. No bolted-on IPC that breaks on the next upstream merge.
P05
Automated builds and tests triggered on every new Chromium milestone release. Merge conflicts detected in CI — not three months later when a security patch is urgent.
P06
Upstream security fixes applied within 72 hours of Chromium stable release. Your fork stays within one milestone of upstream at all times. No drifting behind while CVEs accumulate.
Signature case
An enterprise privacy browser forked from Chromium 108 — 14 milestones behind upstream, 340+ merge conflicts blocking the rebase, integrated VPN that broke on every update, and three known Chromium CVEs unfixed. Rebased to Chromium 128, restructured all patches as isolated changesets, and established a milestone-per-sprint merge workflow in 10 weeks. CVEs resolved. VPN integration stable. Fork maintainable going forward.
Before
Chromium 108 · 14 milestones behind · 340+ conflicts · 3 unpatched CVEs · VPN broken on update
After
Chromium 128 · current milestone · isolated patches · 0 CVEs · VPN stable across updates
Engagement shape
A typical Chromium development engagement. We build or rebase milestone by milestone — the current product keeps shipping while we work.
Two senior Chromium engineers. Fork delta analysis, patch inventory, build system audit, upstream gap assessment. A ranked, dollarized RFC.
Build system configured, GN flags stripped, first milestone rebase completed, CI pipeline running against upstream. Real build on target platforms.
Patches rebased, features integrated, tests passing on each milestone. Your product keeps shipping on the current fork while the new one catches up.
Production build on current upstream milestone. Merge workflow documented. Runbook handed to your team — or we stay on retainer.
Stack
Our default Chromium development stack — picked for real fork maintenance.
Engagement
No hourly retainer that bills for "thinking time." Pick a lane that matches your stage; everything is fixed-quote or transparently rated.
A defined scope, a fixed price, a senior-only team. From RFC to production build in 10–16 weeks.
$15k–$30k
FIXED SCOPE
Embedded engineers in your Slack, your Jira, your standups. Senior C++ engineers who work inside Chromium's codebase daily. Pause, resize, end with 30 days' notice.
$5k / eng / mo
PER ENGINEER
A long-term partner for organisations maintaining Chromium forks — upstream sync, security patching, feature development, hiring help.
custom
PROCUREMENT-FRIENDLY
Founder-direct
Thirty minutes with the founder. We'll bring a senior Chromium engineer, the relevant playbook, and a candid read on whether a source fork is the right call — or whether CEF, WebView2, or an extension solves your problem at a fraction of the cost.
