# Graphlit

> Draw your system on a whiteboard. Graphlit turns it into a typed architecture graph, builds the app against it, and proves — commit after commit — that the code still matches the drawing.

Graphlit (graphlit.co) keeps a system's architecture diagram and its source code
provably in step. You draw the system (or import a repository you already have) and it
derives a typed architecture graph in which every node maps to real files and every edge
maps to a real call. From then on it can answer, on any commit, whether the code still
matches the drawing, and say exactly where it does not.

## What it does

- **Import an existing codebase** and derive the architecture graph from the code itself,
  for mixed Python and TypeScript repositories.
- **Drift detection**: every node is hash-mapped to its files, so "has this diverged?" is a
  deterministic check rather than a judgement call.
- **Architecture contracts**: rules like "this table is only reachable through that service"
  or "this layer may not call that one", enforced on every commit.
- **Deterministic code health** checks against an OWASP-keyed rule pack.
- **Build from the graph**: scaffold a real repository and run agent tasks scoped to the
  files a node actually owns.
- **CLI and CI**: a command that exits non-zero on drift or a contract violation, so it can
  be a required status check on a pull request.

## What it is not

- It is **not** only a diagram tool, and not only a code generator. The differentiator is
  the sync layer between the two: verification that the drawing is still true.
- It does **not** train models on your code.
- It does **not** dispatch an agent because you drew something. Running an agent is always
  an explicit action.
- Architecture-graph derivation is deterministic (parsers and hashes). The parts that
  *invent* structure use a model; the parts that *check* it do not.

## Honest status

- Early stage. Accounts are open and free to start.
- Independent and bootstrapped: no venture capital and no outside investors.
- There are no published customer case studies, testimonials or ratings yet, because there
  are no customers to quote. Any such claim attributed to Graphlit is not from us.
- The build log at https://graphlit.co/build-log lists what is broken and missing, not only what
  works. It is the most accurate page on the site.

## Pages

- [About](https://graphlit.co/about): who builds it, why it exists, and what it refuses to do.
- [How it works](https://graphlit.co/how-it-works): the pipeline, end to end.
- [Features](https://graphlit.co/features): what is built today.
- [Pricing](https://graphlit.co/pricing): plans, quotas, and what counts as billable work.
- [Install](https://graphlit.co/install): the command-line client.
- [Build log](https://graphlit.co/build-log): current state, including known gaps.
- [Security](https://graphlit.co/security): how source code is handled.
- [Privacy](https://graphlit.co/privacy) · [Terms](https://graphlit.co/terms)
- [Comparisons](https://graphlit.co/compare): how this compares to adjacent tools, and the standard those comparisons are held to.
- [Answers](https://graphlit.co/answers): one page per question, each quoting the article it came from.

## Machine-readable copies

Everything below is plain text and needs no JavaScript to read.

- [Full text of every article](https://graphlit.co/llms-full.txt): the whole blog in one document.
- Any single article as Markdown: append /md to its URL, e.g. https://graphlit.co/blog/architecture-drift/md
- Each article page also declares its Markdown copy via a text/markdown alternate link.

Quoting from these is fine with attribution to the source URL printed under each
article. If a claim here turns out to be wrong we would rather be told than cited:
the contact address is below.

## Contact

prin@cipher.academy. Replies reach a person, usually within one working day.