Farrington engineering desk · Asheville, NC

Systems, with the
hood open.

The technical side of Farrington Development—open-source software, production field notes, working systems, and useful experiments from three decades of building for the web.

Explore the work↓ Visit the company site↗
Current Farrington Command Center PWA showing the production Agents workspace
COMMAND CENTER · LIVE PWAAGENTS · PRODUCTION
PRODUCT ENGINEERINGAI SYSTEMSOPEN SOURCEPRODUCTION OPERATIONS

01 / OPEN SOURCE

Useful software should
stand on its own.

OPENOCTIAGPL-3.0SELF-HOSTED

An open operations system for teams that want to own their stack.

OpenOcti is the open-source edition of our operations platform: CRM, projects, documents, voice, and AI staff in one self-hosted system. The source, issues, and release history are public.

  • Runs on your infrastructure
  • Bring your own model providers
  • Community-supported and inspectable
View the source↗ Visit openocti.com ↗
OpenOcti application dashboard showing its operations workspace OPENOCTI · APPLICATION UI
  • TruthDiff local preview for checking documentation against code changes TRUTHDIFF · LOCAL PREVIEW
    TRUTHDIFFAGPL-3.0LOCAL-FIRST

    Find documentation that no longer matches the code.

    TruthDiff is an evidence-first engine that maps Git changes to the documentation and operational knowledge they may invalidate.

    • Node.js CLI and zero-dependency library
    • Deterministic proof stays separate from inference
    • No account, repository upload, or paid API required
    VIEW TRUTHDIFF ON GITHUB ↗
  • Security Workbench local defensive operations dashboard SECURITY WORKBENCH · LOCAL UI
    SECURITY WORKBENCHMITLOOPBACK-ONLY

    A constrained local surface for trusted security tools.

    Security Workbench Community Edition brings defensive tools, repository intake, and an optional local advisory guide into one loopback-only dashboard.

    • Fixed, pre-registered actions with no arbitrary shell
    • Repository intake clones without checkout
    • Local advisory guide cannot execute tools
    VIEW SECURITY WORKBENCH ON GITHUB ↗

02 / FIELD NOTES

Lessons from systems
that have to work Monday.

Architecture, product decisions, and operating lessons—written from production work, not theory.

001 Building an open agent harness without giving up operational control AI SYSTEMS 002 Why a modern website should behave like a web application PRODUCT 003 Technical SEO for developer-led and AI product companies DISCOVERY 004 What changes when an internal tool becomes an operating system ARCHITECTURE

03 / OPERATING PRINCIPLES

Built to survive
contact with reality.

01

Build the whole path.

A feature is not finished at the interface. Data, failure handling, security, deployment, and recovery are part of the product.

02

Operate what we ship.

Production changes the questions. We build with the people, constraints, and Monday-morning consequences in view.

03

Show the evidence.

Demos, source, release history, and measured outcomes are more useful than a wall of claims.

HAVE A HARD SYSTEM TO BUILD?

Bring the problem.
We’ll bring the bench.

Farrington Development works with a small number of teams where the cost of a bad build is high and the right system changes the business.

Start a project↗