Your work. Your space.

Find the right Gonu tool for the next step.

Features & demosExplore Engineering Brain workflows and sample screensExploreWeb ChatFor quick questions, planning and everyday workTry nowDesktop WorkerFor local repository work with a dedicated desktop appDownloadVS Code ExtensionFor developers who already work in VS CodeSource betaGonu CLIFor terminal workflows and structured task inspectionSource betaGonu IDEFor developers exploring an integrated Gonu editorNot releasedDocs & demosPractical guides for every Gonu toolLearn
Skip to content
gonu.
Checking account…Try on web
04 / Company Digital TwinPartial implementation

See systems and responsibility together.

Inspect code, shared service records, explicit owners and Git contributions without confusing contribution with expertise.

Public demo · no login needed. Real workspace use requires sign-in, project access and a configured release.

TAKE A LOOK INSIDE

See how the workflow fits together.

Interactive illustration

All screens use synthetic sample content. Clicking through this demo does not run a model, access your files, change an account or use your allowance.

  1. Scan accessible code and configuration. Add services as explicit records instead of guessing them from directory names.

  2. Assign an authorized project member to a shared service, decision or handover record.

  3. Review explicit ownership separately from Git authorship when deciding whom to ask.

g.Company Digital TwinSAMPLE
ILLUSTRATIVE WORKSPACE

System map / Session service

Service

Explicit project record

Source

src/session-store.ts

Configuration

Selected deployment manifest

Directories are not counted as services.
Step 1 of 3

A useful first request

Who is explicitly assigned to this service, and which changes are recorded? Do not infer an expertise score.

MADE FOR Engineering managers and project leads

When it earns its place.

Find a starting point for a technical handoff or review, especially when ownership is scattered across documents.

THE USEFUL RESULT

A source-backed starting point for ownership and handoff conversations.

Only current project members and permitted sources are used. No employee surveillance or private-memory harvesting.

CURRENT CAPABILITIES

Know exactly what to expect.

The described foundation is implemented. The advanced actions listed as pending are not available yet.

Implemented in the beta

  • Source, record, explicit owner and Git-author relationships.
  • Searchable bounded graph and readable evidence.

Not available yet

  • Verified expertise inference and customer relationships.
  • Complete live infrastructure and company graph discovery.

GET READY

Start with the right context.

  • A scanned project with shared service or ownership records.
  • Owners who have current access to the project.

Brain workflows require the matching API/Web release and an authorized managed project. The model, executor and integrations must be configured for the task you choose. Opening a demo does not enable an integration.

Inspect people & ownership

Practical guides

Organization, members & teamsWeb workspaceEngineering Brain: your software and its historyWeb workspaceDiscuss your team's setup