<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <title>About Roam — Athens-based, Apache 2.0, customer-funded</title>
  <meta name="description" content="Who builds Roam, why it exists, how it is funded, and the founding beliefs behind local codebase intelligence for AI agents.">
  <link rel="canonical" href="https://roam-code.com/about">
  <link rel="icon" type="image/svg+xml" href="/favicon.svg">
  <meta name="theme-color" content="#0049b7">
  <meta name="apple-mobile-web-app-title" content="Roam">
  <link rel="apple-touch-icon" href="/favicon.svg">
  <link rel="manifest" href="/manifest.webmanifest">
  <link rel="preload" href="/fonts/space-grotesk-variable.woff2" as="font" type="font/woff2" crossorigin>
  <link rel="preconnect" href="//github.com" crossorigin>
  <link rel="preconnect" href="//pypi.org" crossorigin>
  <link rel="preload" href="./landing.css" as="style">
  <link rel="stylesheet" href="./landing.css">
  <meta name="robots" content="index,follow">
  <meta property="og:title" content="About — Roam">
  <meta property="og:description" content="Why roam-code exists, who built it, what we believe.">
  <meta property="og:url" content="https://roam-code.com/about">
  <meta property="og:image" content="https://roam-code.com/og.png">
  <meta name="twitter:card" content="summary_large_image">
  <meta name="twitter:image" content="https://roam-code.com/og.png">

  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "AboutPage",
    "name": "About Roam",
    "url": "https://roam-code.com/about",
    "inLanguage": "en",
    "isPartOf": {"@type": "WebSite", "name": "Roam", "url": "https://roam-code.com/"},
    "publisher": {
      "@type": "Organization",
      "name": "Cranot",
      "url": "https://github.com/Cranot",
      "founder": {"@type": "Person", "name": "Dimitris", "jobTitle": "Founder"}
    }
  }
  </script>
</head>
<body>

  <a class="skip-link" href="#main">Skip to content</a>

  <nav class="site-nav" aria-label="Main navigation">
    <div class="nav-inner">
      <a href="/" class="site-logo">roam<span class="logo-dot">.</span></a>
      <input type="checkbox" id="nav-toggle" class="nav-toggle-checkbox" aria-label="Toggle navigation menu">
      <label for="nav-toggle" class="nav-toggle-label">
        <span class="nav-burger" aria-hidden="true"></span>
        <span class="visually-hidden">Menu</span>
      </label>
      <ul class="nav-links">
        <li><a href="/">Home</a></li>
        <li><a href="/pricing">Pricing</a></li>
        <li><a href="/compare">Compare</a></li>
        <li><a href="/setup">Setup</a></li>
        <li><a href="/docs/">Docs</a></li>
        <li><a href="https://github.com/Cranot/roam-code">GitHub</a></li>
      </ul>
    </div>
  </nav>

  <main id="main" class="legal-page">
    <header class="legal-header">
      <h1>About</h1>
      <p class="legal-meta">Founded in Athens · Apache 2.0 · sole-trader, customer-funded</p>
    </header>

    <article>
      <h2>What Roam is for</h2>
      <p>
        Roam is the <strong>local codebase intelligence layer for
        developers and coding agents</strong>. It gives AI coding
        agents a <strong>map of your repo</strong> — callers, clones,
        tests, layers, hot paths, dependencies, git history, smells,
        security flows, and algorithmic patterns — compiled locally
        into a SQLite graph. AI agents write code; Roam gives them
        the structural context they do not have by default.
      </p>
      <p>
        On top of that engine, Roam compiles <strong>trustworthy
        evidence for AI-assisted software change</strong>: who acted,
        what authority existed, what context was read, what changed,
        what could break, what policy applied, what verified it, who
        accepted risk. When the run ledger and proof-bundle flow is
        enabled, Roam writes tamper-evident audit-trail entries and
        verifiable evidence records, so a reviewer can replay the work
        after the fact. Roam <em>maps to</em> and
        <em>supports evidence for</em> SOC 2 CC8.1, ISO 42001, and
        internal AI-governance controls — it does not certify
        compliance with any framework.
      </p>
      <p>
        One concrete differentiator is <strong>algorithmic risk
        review</strong> (<code>roam math</code>, alias <code>roam
        algo</code>): code that is correct but computationally wrong —
        the class of patterns AI agents ship that pass tests and fail
        at scale. Nested-loop O(n²) lookups, N+1 queries, regex
        compiled inside hot loops, repeated JSON parsing, quadratic
        string concatenation, branching recursion without memoisation.
        Linters operate on tokens. Semantic AI reviewers operate on
        diff text. Roam operates on the diff as a graph mutation, so
        it catches the structural class those layers miss.
      </p>
      <p>
        Roam complements existing review layers. Linters, SAST, and
        AI semantic reviewers (CodeRabbit, Greptile, Qodo) operate on
        the diff as text. Roam operates on the diff as a graph
        mutation. Different layer, different bugs. Most teams that
        ship serious AI-generated code want both signals — see
        <a href="/compare">how Roam compares</a> to the semantic
        reviewers.
      </p>

      <h2>Why now</h2>
      <p>
        2025–2026 changed how teams ship code. Senior engineers stopped
        being the only people writing PRs; agents started shipping
        them too. The tooling kept up on the
        <em>generate</em> side and not on the <em>verify</em> side.
        Public reports show why teams are asking for stronger code-change
        gates:
      </p>
      <ul>
        <li>PocketOS — the founder reported that an AI coding agent deleted a production database and attached backups in seconds; the lesson is authorization and recovery controls, not "better prompts" (<a href="https://zenity.io/blog/current-events/ai-agent-database-deletion-pocketos">Zenity incident analysis, 2026</a>).</li>
        <li>Amazon — Business Insider reported a 90-day reset of code-change controls after major outages; Amazon said only one reviewed incident was AI-related and not caused directly by generated code, which makes this a code-control example rather than an AI-causality claim (<a href="https://www.businessinsider.com/amazon-tightens-code-controls-after-outages-including-one-ai-2026-3">Business Insider, March 2026</a>).</li>
        <li>Faros AI 2026 telemetry — a vendor report correlates high AI adoption with higher downstream review and quality pressure, including bugs per developer and incidents per PR; treat it as telemetry signal, not causal proof (<a href="https://www.faros.ai/research/ai-acceleration-whiplash">Faros AI engineering report, 2026</a>).</li>
      </ul>
      <p>
        Roam's assurance layer is built on top of that local intelligence
        engine. The CLI runs locally under Apache 2.0 and stays free
        forever. Paid layers sit on top when teams want continuous
        review, hosted dashboards, or a paid audit of the last quarter:
        the <strong>PR Replay audit</strong> is the fastest path from
        "I'd like to know what Roam would have caught on my repo" to a
        written report.
      </p>
      <ul>
        <li><a href="/audit"><strong>PR Replay audit</strong></a> — paid one-shot replay against your last 5 / 30 / 90 PRs. Free DIY sample, Team $2,500, Deep $6,000. 50% of the fee credits toward Roam Review.</li>
        <li><a href="/governance">Agent Governance Evidence Pack</a> — control mapping, sample audit report, and evidence checklist for SOC 2 / ISO 42001 / EU AI Act reviewers.</li>
        <li><a href="/trust">Trust posture</a> — data handling, retention, and processing locations per product surface.</li>
      </ul>

      <h2>Who built it</h2>
      <p>
        Roam is built by Dimitris (handle: Cranot), a sole-trader operating
        from Athens, Greece. Solo founder; the company structure is a Greek
        atomiki epicheirisi (sole proprietorship). Customer-funded, no
        external investors. No exit plan beyond "build something useful
        and stay independent."
      </p>
      <p>
        Find me on
        <a href="https://github.com/Cranot">GitHub</a>,
        or email <a href="mailto:hello@roam-code.com">hello@roam-code.com</a>.
      </p>

      <h2>What we believe</h2>
      <ul>
        <li><strong>Code stays on your machine by default.</strong> The CLI does not phone home. No telemetry, no analytics, no "anonymous usage data." Roam Cloud receives metrics only — never source code. Roam Review processes PR diffs ephemerally to render verdicts; private-deployment pilots are scoped separately when hosted processing is blocked by policy. See the <a href="/privacy">privacy page</a> for the full data-flow per product.</li>
        <li><strong>Verifiable claims beat marketing copy.</strong> Every analysis Roam runs writes a tamper-evident audit-trail file plus signed records (in-toto v1, verifiable with cosign). The kind of evidence SOC 2, ISO 42001, and internal AI-governance policies want to see. We don't ask you to trust us; we give you the receipts.</li>
        <li><strong>Open source is the default for the engine.</strong> Apache 2.0. Fork it, audit it, ship a competitor. The CLI will stay free forever — we make money from the hosted layers, not from gatekeeping the engine.</li>
        <li><strong>Privacy is the floor, not a feature.</strong> Zero cookies, zero tracking, zero analytics on this site (see the <a href="/no-cookies">receipt</a>). After the August 2025 CodeRabbit RCE that leaked write access to ~1M repos, careful data-handling stopped being a differentiator and became the minimum bar.</li>
        <li><strong>EU is home, not a market.</strong> Built in Athens. Made in the EU. GDPR-native. The EU AI Act is the regulation we'll feel first — even where the obligations don't apply directly, we'd rather build for the trajectory than retrofit later.</li>
      </ul>

      <h2>Funding model</h2>
      <p>
        Roam is customer-funded. The free CLI exists because it earns
        the right to charge for the paid layers — PR Replay engagements
        today, Roam Review (hosted continuous review) and Roam Cloud
        (shared metrics dashboard) as early-access products, and
        scoped private-deployment pilots when hosted processing is
        blocked by policy. No VC, no acquisition track. The company
        stays small enough to answer email personally. See
        <a href="/pricing">pricing</a> for the per-tier breakdown and
        <a href="/audit">/audit</a> for the paid PR Replay engagement.
      </p>
      <p class="legal-meta">
        Billing entity, tax-ID, and invoice format are disclosed on the
        <a href="/terms">terms of service</a> and the
        <a href="/refund">refund policy</a>. Live payment endpoints
        are pending finalisation of the procurement gates listed on
        the <a href="/audit">audit page</a>.
      </p>

      <h2>Roadmap</h2>
      <p>
        See the <a href="/changelog">changelog</a> for what's shipped.
        Near-term: GitHub App MVP for Roam Review, Cloud dashboard
        scaffold, more cross-language bridges. Each ships when it ships;
        we don't pre-announce roadmap items because plans are guesses
        until they're code.
      </p>

      <h2>Where to find us</h2>
      <ul>
        <li>Site: <a href="/">roam-code.com</a></li>
        <li>Docs: <a href="/docs/">roam-code.com/docs/</a></li>
        <li>GitHub (engine, Apache 2.0): <a href="https://github.com/Cranot/roam-code">github.com/Cranot/roam-code</a></li>
        <li>PyPI (free CLI): <a href="https://pypi.org/project/roam-code/">pypi.org/project/roam-code</a></li>
        <li>Paid PR Replay audit: <a href="/audit">/audit</a></li>
        <li>Governance evidence pack: <a href="/governance">/governance</a> · trust posture: <a href="/trust">/trust</a></li>
        <li>Pricing: <a href="/pricing">/pricing</a> · compare with semantic reviewers: <a href="/compare">/compare</a></li>
        <li>Email: <a href="mailto:hello@roam-code.com">hello@roam-code.com</a></li>
        <li>Security disclosures: <a href="mailto:security@roam-code.com">security@roam-code.com</a> (see <a href="/security">policy</a>)</li>
      </ul>

      <p class="legal-foot">
        Want to write about Roam? See the <a href="/press">press kit</a> for logos and screenshots.
      </p>
    </article>

  <section class="page-cta-strip" aria-label="Get started with Roam">
    <div class="page-cta-inner">
      <p>Ready to try Roam? <a href="/" class="btn-primary">Install the free CLI</a> · <a href="/audit">book a PR Replay audit</a> · <a href="/pricing">see paid plans</a></p>
    </div>
  </section>
  </main>

  <footer>
    <div class="footer-inner">
      <div class="footer-col">
        <strong>Roam</strong>
        <span>The local codebase intelligence layer for AI agents and the teams that run them.</span>
        <span class="footer-meta">Built in Athens. Made in the EU.</span>
      </div>
      <div class="footer-col">
        <a href="https://github.com/Cranot/roam-code">GitHub</a>
        <a href="https://pypi.org/project/roam-code/">PyPI</a>
        <a href="/docs/">Docs</a>
      </div>
      <div class="footer-col">
        <a href="/setup">Setup</a>
        <a href="/about">About</a>
        <a href="/press">Press</a>
        <a href="/changelog">Changelog</a>
        <a href="/status">Status</a>
        <a href="/security">Security</a>
        <a href="/accessibility">Accessibility</a>
      </div>
      <div class="footer-col">
        <a href="/privacy">Privacy</a>
        <a href="/terms">Terms</a>
        <a href="/refund">Refund</a>
        <a href="/no-cookies">No cookies</a>
      </div>
      <div class="footer-col">
        <a href="mailto:hello@roam-code.com">hello@roam-code.com</a>
        <a href="mailto:security@roam-code.com">security@roam-code.com</a>
        <span class="footer-meta">No cookies. No tracking. No analytics.</span>
        <span class="footer-meta"><a href="https://github.com/Cranot/roam-code/tree/main/templates/distribution/landing-page">This page is open source</a></span>
      </div>
    </div>
  </footer>

</body>
</html>
