Engineering intelligence

Software should explain itself.

Helix connects changes, ownership, and review evidence so your team can understand why code exists, what a change affects, and what evidence is missing before it ships.

01 / Nodes

Nodes appear.

Files, people, and pull requests take their place.

01 / The gap

Software is changing faster than teams can understand it.

AI made generating code easy. Understanding it did not. The why gets scattered. People leave. Docs go stale. The same mistakes return.

GitHubJiraSlackConfluenceDatadogpeople’s memoriesGitHubJiraSlackConfluenceDatadogpeople’s memories

02 / The missing asset

Software remembers what changed.

It rarely remembers why.

03 / The questions

An engineer should not need six tools and a three-year-old Slack thread.

01

Why does this service exist?

02

What depends on this API?

03

Why did we introduce Redis?

04

What could this change break?

05

Who understands this part of the system?

06

Which past decisions matter here?

Every answer should be immediate, evidenced, and understandable.

04 / Engineering Graph

A shared memory of how software evolved.

Your software is years of decisions, architecture, incidents, and people. Helix connects them into one living system.

The graph

Code, people, and decisions as a living constellation.

01Pull requests

02Files

03Directories

04Authors

05Reviewers

06Ownership

07Coupling

08DNA patterns

09Agent loops

Why

Why it exists

Trace code and architecture back to the decisions that created them.

Impact

What it affects

See the services, APIs, tests, and teams connected to a change.

Trust

Whether to trust it

Review facts, patterns, and evidence before software reaches production.

05 / Agent loops

The graph learns while you ship.

Five deterministic loops watch merge history and write patterns back onto the graph. Facts stay facts. Inference is labeled.

Loops

Five loops watching the graph.

01

Silo

Files with a single author. The bus factor, evidenced.

02

Coupling

Files that refuse to ship alone.

03

Expertise

Who actually knows a path, recency first.

04

DNA

How this team reviews the hottest code.

05

Memory

Evidence that should compound, not decay.

06 / Engineering DNA

Every team works differently. That is not a bug. It is DNA.

Encoded in how the team designs, reviews, ships, and learns. Generic best practices tell part of the story. Helix discovers how you actually build.

Engineering DNA

How this team actually works, read from the graph.

07 / Product

Review changes. Understand systems. Learn from history. Ship with confidence.

Live product

Graph, Pulse, and Ask Helix. Recorded from the workspace.

A selected node lighting up its blast radius on the graph

Helix Review

Ship readiness from blast radius, ownership, checks, and evidence coverage.

Ask Helix

Ask why Redis exists. Every sentence points at a node you can open.

Pulse

Architecture, silos, churn, experts, and DNA the loops just encoded.

API

IDEs, agents, and CI query the same living graph. Evidence as a budget.

08 / How Helix works

Every engineering event becomes knowledge.

  1. 01

    Connect a repository

    Public GitHub, or a token for private work.

  2. 02

    Build the Engineering Graph

    People, files, pull requests, relationships.

  3. 03

    Loops encode DNA

    Every merge writes patterns back onto the graph.

  4. 04

    Ask, with citations

    Helix reconstructs an answer. It does not search a wiki.

  5. 05

    Ship with evidence

    Ship, review, or hold. From history, not a vibe.

09 / Integrations

Connect the tools your team already uses.

Start with the source of engineering change. Expand the graph as Helix adds more trusted signals.

GitHub

Available in private beta

GitLab

Planned

Linear

Planned

Jira

Planned

Slack

Planned

Datadog

Planned

PagerDuty

Planned

OpenTelemetry

Planned

Notion

Planned

Confluence

Planned

Git

records what changed.

Helix

remembers why.

10 / Get started

Understand your Engineering DNA.

Connect GitHub in minutes. Start on the sample, or index a public repo.

Pricing

Start with developers. Expand into the platform.

Explorer

Freeforever

Individuals and open source.

  • 1 saved repository
  • 8 pull requests per index
  • 5 Ask Helix answers
  • Living graph of people, files, directories, and PRs

Team

$49/ month

Per-developer operating system for who knows what.

  • 10 saved repositories
  • 25 pull requests per index
  • Unlimited Ask Helix, with citations
  • Full Pulse: silos, churn, experts, bus factor

Scale

$199/ month

Org-wide engineering intelligence.

  • Unlimited saved repositories
  • 50 pull requests per index
  • Org Pulse: bus-factor and silo alerts
  • Shared workspaces, team digests, and saved review reports