Labs

RaccSec Labs

The evidence behind the work

RaccSec.com introduces the projects. This is where they get taken apart: architecture, the constraints that shaped them, the decisions worth defending, what broke along the way, and what the work actually produced.

01 What this is

Depth, not summaries

A portfolio entry tells you something was built. It rarely tells you why it was built that way, what was ruled out, or what the tradeoffs cost. Those are the parts another engineer actually wants, so they live here rather than on the portfolio.

02 Projects

Featured

  • Local-first AI platform

    AvaOS

    Building an owner-controlled, local-first operating system for governed AI teammates. Threat model first, deterministic governance around an untrusted model, and validation on the Windows machine that actually has to run it.

    • Applied AI
    • Local-first
    • Governance
    • Windows security

    Private alpha

  • AI governance platform

    RaccZero

    Governing AI use where sensitive data enters the browser. A reviewed alpha spanning a browser extension, a policy backend, and two portals, with the release blockers stated as plainly as the design.

    • AI governance
    • Data loss prevention
    • Browser extension
    • Applied AI

    Reviewed alpha

All projects

03 Case studies

What each one covers

Case studies here are not fixed to a template, because a platform and a detection tool do not tell the same shape of story. Most will work through some combination of these.

  • The problem, and the environment that produced it
  • Constraints: budget, access, time, blast radius
  • Architecture and how data actually moves
  • Decisions worth defending, and the options rejected
  • Security considerations and trust boundaries
  • What broke, and what the iterations cost
  • Limitations, and what would be done differently
  • Validated results, with the evidence behind them