The Graphtia platform

See the connections. Understand the work.

Code understanding and reviewable engineering work. Two related directions, built around context you can inspect.

From entry point to supporting code

The checkout entry point reaches a service, its payment and order dependencies, a validation contract and a test. Lines illustrate static relationships, not runtime execution.

Entry pointcheckout.test.ts
01
Checkout servicecheckout-service.ts
02
Payment gatewaypayment-gateway.ts
03
Order moduleorder-service.ts
04
Validation contractvalidation.ts
05
Related checkscheckout.test.ts
06
Selected module · Static relationships · Supporting checks

Current engineering build · Public access in preparation

Graphtia Explorer

Move between a code graph, a real file tree and the source behind a relationship. Select a module, inspect its evidence and keep the surrounding code in view.

Graphtia Explorer showing the commerce-platform file tree, selected checkout-service.ts module, relationship graph, source code and inspector.
Actual Windows engineering build, locally indexing a neutral commerce-platform example. Source and relationships are real; the example does not connect to a payment provider.
Explore Explorer documentation

Explore

Find files and symbols. Open a focused graph and the source behind a result. The file tree and inspector retain a concrete place to continue.

Analyze

Inspect dependencies and dependents, impact candidates, related tests and findings. Relationship types and source evidence help explain why an item belongs in the result.

Trace

Use paths and bounded neighborhoods to investigate a connection. Expand the scope deliberately instead of assuming the visible graph contains the entire repository.

Understand

Check the indexed revision, source range and result limits. A partial result or a revision mismatch is part of the answer, not something to hide.

Languages & frameworks

A wider view of the source

The current analysis engine includes the language ecosystems below. Framework awareness recognizes supported static conventions; it does not simulate every runtime behavior. Native product validation is currently evidenced on Windows x64.

TypeScript / JavaScriptNode.js packages, React, Next.jsStatic analysis

Includes TS/JS modules and workspace resolution. Dynamic imports, runtime dispatch and full TypeScript type checking are not complete.

RustCargo workspacesStatic analysis

Modules, symbols and explicit source relationships. Macro expansion and type-directed or dynamic dispatch remain partial.

HTMLStatic web documentsStatic analysis

Source structure and static references. This does not execute a browser or observe the runtime DOM.

CSSStylesheets and static assetsStatic analysis

Simple selectors, variables and asset relationships. Runtime CSSOM and preprocessor behavior are not executed.

PHPComposer, Laravel, WordPressStatic analysis

Source and recognizable framework conventions. Runtime hooks, reflection and framework magic remain partial.

GoGo modules, net/http, Gin, Echo, Fiber, gRPCStatic analysis

Source, module and explicit service relationships. Interface dispatch, build tags and cgo remain partial.

JavaMaven/Gradle, Spring, JAX-RS, JPA/Hibernate, gRPCStatic analysis

Recognizable static declarations and enterprise conventions. Reflection, generated behavior and executable build logic remain partial.

C# / .NETASP.NET Core, built-in DI, EF Core, gRPCAnalyzer package required

Requires the official .NET 10 analyzer package. Reflection, source generators and executable MSBuild behavior remain partial.

PythonProject metadata, FastAPI, Django, Flask, SQLAlchemy, CeleryStatic analysis

Source relationships and recognizable framework declarations. Dynamic imports, monkey-patching and runtime metaprogramming remain partial.

Read the support and limitations guide

Engineering evidence

A map with its limits in view

Queries have explicit bounds for result size and traversal. Indexed revisions and truncation states help keep an investigation reviewable as the repository grows.

Large-corpus engineering reports exist, but measurements vary by hardware, language and query. We are not publishing a universal indexing speed or memory promise. Incremental behavior continues to be validated across larger workspaces.

Future product direction · Not publicly available

Graphtia Governance

A future direction for connecting an objective, a plan, bounded work units and evidence that a reviewer can inspect.

The engineering foundations include explicit scope, plan-drift detection and evidence records. A public Governance product and its integrations are still being developed.

Make engineering work reviewable

A future Graphtia Governance workflow connects an objective to a plan, bounded work units, execution records, evidence and review. This conceptual product is not publicly available.

ObjectiveWhat needs to change
01
PlanProposed approach
02
Work unitsBounded responsibilities
03
ExecutionRecorded work
04
EvidenceWhat supports the result
05
ReviewA deliberate decision
06
Future product direction · Not publicly available
Explore Governance concepts

Be part of what’s next

Join the Graphtia waitlist

Get early access and help shape the future of agentic software engineering.

Join waitlist

Graphtia

This page is on its way. Join the waitlist to hear what’s next for Graphtia.

Join waitlist