Architecture

Architecture

Richmack Browser keeps upstream Chromium intact rather than maintaining a full browser-engine fork.

High-level architecture

Chromium
   |
   +-- Richmack Core
   +-- Extract
   +-- Images
   +-- Email
   +-- Media
   +-- Feed
   +-- Pick
   +-- Automate
          |
          v
   127.0.0.1:8765
          |
   Richmack Services
          |
        Docker

Why not fork Chromium?

A full Chromium fork would require continuous maintenance for:

• security patches
• rendering engine changes
• browser APIs
• operating-system compatibility
• build-system changes
• upstream merges

Richmack instead focuses on browser behavior and tools.

Browser layer

The browser layer provides:

• dedicated Richmack Chromium profile
• dark configuration
• new-tab customization
• toolbar tools
• keyboard mode
• workspaces
• bookmark metadata

Extension layer

Tools are separated into individual extensions so the browser toolbar stays compact and modular.

Each extension receives only the permissions it requires.

Services layer

Heavy or privileged operations are moved outside webpage JavaScript.

Examples:

• RSS feed storage
• media processing
• document processing
• backend utilities

The default backend address is:

http://127.0.0.1:8765

Security boundary

A webpage does not directly gain shell or Docker access.

The intended path is:

Website
   |
   X direct privileged access
   |
Extension
   |
permission / user action
   |
Local service