Pilot · Five .NET teams

Not being able to see where code is really used is becoming history.

SliceTrace maps symbol usage across all your .NET repositories. Static cross-repo call graphs today; runtime confirmation from OpenTelemetry next.

Become one of five pilot customers — pilot pricing for life.

Apply for the pilot Which problem costs you most?
  • Visual Studio extension
  • Scanner in your build pipeline
  • Hosted or on-prem

Visual Studio extension

Call paths where you already work

The SliceTrace extension brings the call graph into Visual Studio. Right-click any symbol, choose View Call Hierarchy Across Repositories, and see every caller — including the ones in other repositories — without leaving the editor.

Visual Studio View Call Hierarchy Across Repositories
Visual Studio context menu on IRepository.GetAllInPartitionAsync with the SliceTrace command View Call Hierarchy Across Repositories selected, and a Usages panel listing callers from other repositories

Vote

Which of these costs you the most?

Upvote every problem you recognise. One vote per problem; click again to undo.

  1. I can’t change this legacy code. I don’t know what breaks.

  2. A change in one repo broke a consumer in another. We found out in production.

  3. Too many PRs. Architecture drifts and nobody notices.

  4. The AI agent can’t find the root cause without a lot of supervision.

Anonymous: we store a random id from your browser (no cookie) with your votes, so each problem counts you once.

How it works

One call graph across every repository

Static analysis shows what your code can call, across repository boundaries. Next, runtime data from OpenTelemetry will confirm what it actually calls.

  1. Scan in the build pipeline

    The SliceTrace scanner runs as a step in your build pipeline and analyses your .NET code statically, so the graph stays current with every build.

  2. Confirm with OpenTelemetry next

    Runtime data from OpenTelemetry will add the calls that static analysis alone can’t resolve, including the ones that cross service boundaries.

  3. Trace any symbol

    Pick a class or method and see every call path it is part of. Developers get the answer in Visual Studio, and AI coding agents can query the same paths.

Why SliceTrace

Know what a change touches before you make it

Across systems, not just one solution

Call paths follow your code across the .NET systems it runs in, not only the solution you happen to have open.

Grounded in real runtime behaviour next

OpenTelemetry data will show which paths your running systems actually take, alongside everything the code could call in theory.

Context for AI coding agents

Agents see the same call paths your developers do, so they can reason about the impact of a change instead of guessing from the files in front of them.

Deployment

Hosted or on-prem

Hosted

We run SliceTrace for you. Add the scanner to your pipeline, connect your telemetry, and start tracing call paths.

On-prem

Run SliceTrace inside your own infrastructure, so your code and telemetry never leave your network.

Pilot

Become one of five pilot customers

Pilot pricing for life. We work closely with each pilot team on their own .NET estate.

We store your email and company only to select and contact pilot customers. No newsletter, no resale.

Contact

Contact us

Tell me which of these problems you live with, and what SliceTrace would need to do to be worth it for your team.

Book a call