Pricing

Free while we learn.

We are gathering feedback and refining the tool. Use it, tell us what works, tell us what does not.

Full Access

Free

Everything included. No limits while we gather feedback.

Code graph and call paths See how functions connect, where routes lead, what calls what
Ask questions about your codebase Graph-powered answers about structure, dependencies, and flow
All languages Python, Go, TypeScript, Rust, plus future additions
CLI, VS Code, and dashboard Use whichever fits your workflow
Privacy-first Parsing on your machine. Only graph structure sent.
Create account

No credit card No strings

Common questions

Why is it free?

We are building something new and need real feedback from real developers. When we introduce pricing, it will be simple: one plan, fixed price, everything included.

What is the code graph?

Unfault parses your code and builds a graph of functions, classes, imports, routes, and their relationships. This lets you trace call paths, understand dependencies, and ask questions that require understanding structure.

What languages are supported?

Python, Go, TypeScript, and Rust. Each language has framework-specific understanding (FastAPI routes, for example). We add languages based on user demand.

What happens to my code?

Parsing happens on your machine. We receive the code graph structure, not your source code, strings, or comments. We respect .gitignore.

How is this different from a linter?

Linters focus on syntax and style. Unfault builds a semantic understanding of your codebase: call paths, dependencies, entrypoints, and how things connect. The graph enables questions and exploration that line-by-line analysis cannot.

Can I use it in CI/CD?

Yes. The CLI returns proper exit codes and can output in JSON format.

How do I give feedback?

GitHub Discussions is the best place. We read everything.

Tools should support your flow, not meter it.

Follow the breadcrumbs

Unfault helps you understand what your code means and does, while you are writing it.

See connections

Trace how functions call each other, which routes lead where, what depends on what.

Ask questions

"How does auth work?" gets an answer grounded in your actual code structure.

Stay oriented

Context in the editor as you work. Know where you are in the codebase.