A new open-source browser named Yab has appeared on GitHub, positioning itself as a lightweight, native option for macOS users who value speed, privacy, and minimal interface clutter. Developed independently and currently in early stages, Yab runs on macOS 15.4 or later and includes an iPhone companion app. Its design philosophy centres on removing distractions—tabs, a unified address and search field, and core tools are accessible with minimal input, appealing to users fatigued by feature-heavy browsers.
Dual rendering engines for flexibility and compatibility
Yab distinguishes itself by supporting two rendering engines: WebKit by default, and Chromium on Apple silicon Macs. This dual-engine approach allows users to switch per tab or per site, enabling better compatibility with web apps that rely on Chrome-specific behaviours. Chromium tabs support Chrome extensions, Chrome DevTools, and access to the Chrome Web Store—features typically unavailable in WebKit-only browsers due to Apple’s restrictions. This hybrid model could reduce dependency on Google Chrome while maintaining access to its ecosystem where needed, particularly beneficial for developers and power users in the UK, UAE, and Kazakhstan who balance compliance, performance, and tooling requirements.
Built-in privacy and data control from the ground up
Privacy is embedded in Yab’s architecture. The address bar only sends queries upon pressing Return, using local history for autocomplete without external calls. Ad blocking occurs at the engine level, pre-empting requests rather than filtering content after loading. Users can permanently hide page elements with ⇧⌘H, and private tabs are isolated from AI agents—which can run in their own tabs but never access private content without explicit user permission. Passwords integrate with the system keychain or third-party managers, avoiding vendor lock-in. Notably, cross-device sync is optional and end-to-end encrypted, ensuring data remains unreadable in transit—a critical advantage over cloud-dependent browsers, especially for businesses in regulated sectors.
Open-source model invites scrutiny and collaboration
Yab is developed transparently on GitHub, with documentation covering architecture, privacy practices, and contribution guidelines. The project welcomes help, particularly on bug reports and fixes, with labels like ‘good first issue’ and ‘help wanted’ to onboard contributors. Security vulnerabilities must be reported privately per SECURITY.md, reflecting responsible disclosure practices. Development builds can be compiled locally using Xcode 26 or later, with a script that creates an isolated instance (Yab Dev) to avoid conflicts. This openness supports trust and auditability, aligning with UK and EU software transparency trends and offering IT teams in Kazakhstan and the UAE greater control over dependencies.
What it means
For businesses and technical leaders, Yab represents a potential shift toward modular, auditable browser tools that reduce reliance on dominant vendors. Its dual-engine design mitigates risks of WebKit-only limitations on Apple platforms, while end-to-end sync and local data handling strengthen data sovereignty—especially relevant under GDPR, UAE data laws, and Kazakhstan’s evolving digital regulations. However, the project’s early stage means limited testing at scale, few contributors, and unverified resilience against real-world threats. Founders should monitor its evolution rather than adopt it immediately.
Organisations seeking to limit exposure to US-based browser ecosystems may find Yab’s model instructive, even if not yet production-ready. The ability to run Chromium selectively without defaulting to Chrome could reduce bandwidth, memory use, and tracking exposure. For now, the browser serves best as a proof of concept and a testbed for privacy-first, open design principles in a space long dominated by a few players.