An independent browser project exploring a more private, local-first and user-controlled way to access the web—without simply placing another interface on top of Chromium.
Ferricks Browser is a research-led software project. Its purpose is to explore what a modern browser could look like when privacy, local storage and user ownership are treated as core design decisions rather than optional settings.
Ferricks Browser is intended to be developed as a standalone browser rather than being built as another branded layer on top of Chromium. The long-term aim is to control the browser architecture, privacy model and user experience from the ground up.
Browsing information, settings and personal data should remain on the user’s own device wherever practical.
The project aims for a calmer browser experience with clear controls, fewer distractions and less pressure to turn every interaction into an account, feed or recommendation system.
Ferricks Browser is presented honestly as an independent research project. Concepts, features and technical direction may evolve substantially before any production release is considered.
Chromium has enabled many browsers to launch quickly, but shared foundations can also lead to shared technical assumptions, shared limitations and less genuine diversity across the web.
A Chromium-based browser can change its appearance, features and privacy settings, but the underlying engine remains part of a wider shared ecosystem.
Ferricks Browser is intended to investigate a standalone approach so that future decisions about rendering, storage, permissions and privacy are not limited by another browser project’s architecture.
The goal is an independently developed browser foundation rather than a Chromium skin.
Personal browser data should remain on the device unless the user explicitly chooses otherwise.
Independent browser engines can help prevent the web from becoming dependent on a single technical foundation.
Ferricks Browser is guided by a small number of principles that shape the project before decisions are made about features, distribution or commercial models.
Keep browser information on the user’s device wherever possible rather than sending it elsewhere by default.
Make site access to location, camera, microphone and files easy to understand and control.
Reduce unnecessary tracking and avoid building the browser around behavioural profiling.
Let users decide which search service they prefer instead of forcing one default ecosystem.
Explore simple ways for people to move bookmarks and settings without becoming trapped in one platform.
Build a browser with its own technical direction rather than competing only through branding and appearance.
Ferricks Browser is an experimental project under the Ferricks name. Ferricks Limited is winding down its original commercial operations, while Ferricks.com continues as a home for software ideas, technical research and independent digital projects.