Developer Business OS 2026
Obrivo
A local command centre for developers. It links projects, Git, Docker, planning, clients, sales and finances in one app that runs on your own machine.
The project
Obrivo brings the technical and commercial sides of a developer's work into one local web application. It discovers the projects in the workspace folder, reads each one's Git history, detects its technology and Docker configuration, and connects all of that to delivery, focus, finances and sales.
Each project has overview, tasks, milestones, Git, finance, technical, timeline and notes pages, with a preview captured from the running site. Around that sit task boards, daily, weekly and monthly planning, payment and maintenance tracking, and a sales pipeline with contacts, offers, message templates and versioned proposals.
The core needs no cloud account, GitHub connection or API key. Project data, Git statistics and thumbnails are stored locally.
Visual direction.
The interface follows Apple's design guidance: system typography, a rem-based type scale, translucent bars and panels, card surfaces and interruptible springs for transitions. It ships dark (default), light and system themes on an olive green base, with validated chart colours. The interface respects reduced motion and reduced transparency preferences.
Typography
- SF Pro
- SF Mono
Colours
- #161C0D
- #C7D59F
- #40531A
- #FAFCF3
Under the hood.
-
01
It is a single Laravel 13 repository with Inertia 3 pages in Vue 3.5 and TypeScript, with no separate frontend service or public REST API. Business logic lives in single-concern services, and controllers validate through Form Requests.
-
02
It runs as five Docker services: nginx, PHP-FPM, queue, scheduler and PostgreSQL 18. Queue, cache and sessions use Laravel's database drivers, with no Redis. The web port binds to 127.0.0.1 only and the database is not exposed.
-
03
Git analysis uses local data only and never fetches. Commands go through Symfony Process with argument arrays, read-only, with hooks, fsmonitor, pagers and credential helpers disabled. History is cached in the database, and a scheduler checks a fingerprint of each repository every minute.
-
04
The workspace is mounted read-only and treated as untrusted input: paths are canonicalised and must stay inside the root, .env files are never read, and no code from scanned projects is executed during analysis.
-
05
Site thumbnails are captured at 1440 × 900 by Chromium with puppeteer-core inside the queue service. A Python launcher on the host starts each project's Compose stack, without mounting the Docker socket.
-
06
Money is stored as integers in minor units, kept separate per currency. The PHPUnit suite runs on in-memory SQLite with temporary workspaces and Git repositories, and the launcher has its own Python tests.
Private project. Happy to walk through it on a call.