Bor: Open-source centralized policy management system for Linux desktops

What it does

Bor is an open-source system for managing policies across Linux desktop fleets from a central location. It uses a lightweight Go agent installed on client machines and a central server that streams policy changes via mTLS and gRPC in real time, without polling. The system can enforce policies for Firefox, Chrome, Thunderbird, Microsoft Edge, KDE, dconf, polkit, firewall rules, and package management. Version 0.8 added support for Thunderbird, Edge for Business, and firewall zone management.

Who it is for

Bor targets organizations running Linux desktops that need centralized configuration management. IT teams managing multiple machines can use it to enforce consistent browser settings, desktop environments, firewall zones, and application policies across their fleet. The system applies to both corporate deployments using standard packages and containerized installations like Flatpak.

Pricing

The site does not show prices.

How it stands out

Bor uses push-based policy delivery over gRPC instead of polling, which reduces latency and server load. Managed files are protected against tampering—external edits are detected and automatically restored. The system includes a web UI with policy editors that provide validation, previews, and protection against destructive changes. Per-action role-based access control allows granular delegation of admin duties. Polkit rules support variable conditions, enabling rules that match specific action parameters rather than blanket permissions. The interface meets WCAG 2.2 AA accessibility standards and includes features like deep linking, browser history support, and server-side pagination for scalability.

What a founder should check

A founder considering a competing product should verify what alternatives already exist in the Linux desktop management space, particularly what established tools like Landscape, Foreman, or Ansible cover and where gaps remain. Switching costs matter significantly here—check how difficult it would be for an existing fleet using another system to migrate policies, agents, and configurations to a new platform. Finally, examine the moat: determine whether the real value lies in the push-based architecture, the specific policy coverage breadth, the UI usability, or community lock-in through open source adoption, since each suggests different competitive vulnerabilities.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.