
Stackify Prefix is not being switched off. BMC Helix, which owns Stackify, says customers are expected to be able to keep using Prefix after March 31, 2027, but its Premium support ends on that date and Prefix gets no more updates. That is a different story from Stackify Retrace, the production APM, which shuts down completely on the same day.
So there is no deadline for Prefix itself. What changes is that it is frozen: no fixes for new runtime versions, no new frameworks, no support guarantees. This post explains what Prefix did, which tools, most of them free and open source, cover the same job for each language, and what to do about production monitoring now that Retrace is going away.
Table of Contents
- What changes for Stackify Prefix
- What Prefix did, so you know what to replace
- Option 1: a local OpenTelemetry viewer, for any language
- Option 2: tools for your language
- Prefix alternatives at a glance
- Prefix was local. Retrace was production.
- Frequently asked questions
What changes for Stackify Prefix
BMC Helix's Prefix Premium end-of-life notice covers three points:
- Prefix keeps running. It is "not being shut down on March 31, 2027", and customers are expected to be able to keep using it after that date.
- Premium support ends. After March 31, 2027 there are no Premium support services and no support guarantees.
- No more updates. BMC calls Prefix functionally stable and says it will not get new feature enhancements.
BMC's migration guide for Retrace customers adds that for developers who use Prefix on their own machines, its premium features are now available at no cost.
If Prefix works for you today, you don't have to drop it tomorrow. The risk builds slowly: the next .NET, Java, Python or Node.js release, or a new framework version, may not work with a profiler that no longer gets updates. Picking a replacement now means you choose it on your own schedule instead of during a broken build.
What Prefix did, so you know what to replace
Prefix is a profiler for your development machine. Stackify describes it as the same kind of profiling Retrace does on production servers, made available while you write and test code. For each web request it shows:
- the request itself and how long it took
- SQL queries, including slow ones and N+1 patterns
- exceptions, including the ones your code catches and hides
- the log lines written during the request
Stackify lists Prefix support for .NET, PHP, Node.js, Python and Ruby on Windows, macOS and Linux, and for Java on Windows. Newer versions can also take in OpenTelemetry traces and logs over OTLP, which Stackify marks as a preview.
No single tool replaces all of that for every language. The two practical routes are a local OpenTelemetry viewer, which works the same for every language, or a dedicated tool for the language you write.
Option 1: a local OpenTelemetry viewer, for any language
If your app is instrumented with OpenTelemetry, any of these tools can show its traces on your laptop. You point the OpenTelemetry SDK at a local endpoint and open a web page. The same instrumentation can later send data to your production monitoring tool, so you only instrument once.
- Aspire dashboard (standalone). Microsoft's dashboard runs on your machine and shows OpenTelemetry logs, traces and metrics from any language, not only .NET. It is MIT licensed, and Microsoft says it is designed for development and short-term diagnostics. It is the closest match to Prefix's request-by-request view.
- Jaeger all-in-one. One container with in-memory storage that shows traces only. Open source under Apache 2.0, and a long-standing CNCF project.
- Grafana's otel-lgtm image. One container with an OpenTelemetry Collector, Prometheus, Tempo, Loki, Pyroscope and Grafana, so traces, metrics, logs and profiles all work locally. Apache 2.0, and meant for development, demos and testing.
- otel-desktop-viewer. A single binary with no containers that shows traces, metrics and logs. Apache 2.0, built by the community rather than a vendor.
Unlike Prefix, these viewers only show what your OpenTelemetry instrumentation captures. Automatic instrumentation covers requests, outgoing HTTP calls and unhandled exceptions well, but caught exceptions and SQL parameters usually need extra setup. Our guide to moving from Stackify Retrace to OpenTelemetry covers those gaps.
Option 2: tools for your language
If you'd rather not run OpenTelemetry locally, each language has its own tools for the same job.
.NET
- Visual Studio diagnostic tools. The Performance Profiler's Database tool shows ADO.NET and Entity Framework Core queries, and its other tools cover CPU and memory use. Visual Studio Community is free for individuals and small teams.
- dotnet-trace. Microsoft's free, cross-platform command-line tool records a trace of a running .NET Core or .NET 5+ app (not .NET Framework) without a native profiler. Its default settings sample thread stacks to show where time goes, and its database profile captures ADO.NET and Entity Framework commands. Open the trace in Visual Studio or PerfView on Windows, or save it in Speedscope format.
- MiniProfiler. An open source (MIT) per-request profiler for ASP.NET Core that shows SQL timings on the page. As of November 2026 its last NuGet release was in late 2024, so check that it supports your .NET version.
- JetBrains dotTrace. A paid performance profiler that also shows SQL queries and HTTP requests, sold as part of JetBrains' dotUltimate and All Products Pack bundles.
Java
- Java Flight Recorder with JDK Mission Control. JFR has been built into OpenJDK since JDK 11, and Mission Control is the open source tool for reading its recordings. Together they show where time and memory go in your app.
- async-profiler. An open source (Apache 2.0) sampling profiler for CPU and memory with flame graphs.
Neither shows a request-by-request view with SQL the way Prefix does. For that in Java, OpenTelemetry's Java agent with a local viewer from option 1 is the closer fit.
Python
- Django Debug Toolbar. Shows each request's SQL queries with timings and EXPLAIN links, plus cache and profiling panels. BSD licensed.
- django-silk. Records HTTP requests and database queries so you can inspect them afterwards. MIT licensed.
- py-spy. A sampling CPU profiler that attaches to a running Python process. It shows where time goes, but not SQL or logs.
PHP
- Xdebug. The standard PHP extension for profiling, tracing and step debugging. Free.
- Laravel Telescope. For Laravel apps: shows requests, exceptions, log entries and database queries. MIT licensed.
Node.js
- The built-in profiler. Node.js can record a V8 profiling log with
--profand turn it into a readable report with--prof-process. - OpenTelemetry with a local viewer. For a request-by-request view with database calls, Node.js automatic instrumentation plus a viewer from option 1 is the closest match to Prefix.
Clinic.js often comes up in older lists, but its README now says it is not actively maintained and its results may not be accurate.
Ruby
- rack-mini-profiler. Shows database profiling, flame graphs and memory profiling for each request in Rails and other Rack apps. MIT licensed.
Prefix alternatives at a glance
| Tool | Languages | What it shows | Cost |
|---|---|---|---|
| Aspire dashboard | Any, through OpenTelemetry | Traces, logs, metrics | Free (MIT) |
| Jaeger all-in-one | Any, through OpenTelemetry | Traces | Free (Apache 2.0) |
| otel-lgtm | Any, through OpenTelemetry | Traces, logs, metrics, profiles | Free (Apache 2.0) |
| otel-desktop-viewer | Any, through OpenTelemetry | Traces, logs, metrics | Free (Apache 2.0) |
| Visual Studio diagnostic tools | .NET | Database queries, CPU, memory | Free in Community edition, with conditions |
| dotnet-trace | .NET Core, .NET 5+ | Hotspots, database commands, runtime events | Free |
| MiniProfiler | .NET | Request timings, SQL | Free (MIT) |
| dotTrace | .NET | Performance, SQL, HTTP requests | Paid |
| JFR + Mission Control | Java | CPU, memory, JVM events | Free |
| async-profiler | Java | CPU and memory flame graphs | Free (Apache 2.0) |
| Django Debug Toolbar | Python (Django) | SQL with EXPLAIN, cache, profiling | Free (BSD) |
| django-silk | Python (Django) | Requests, SQL | Free (MIT) |
| Xdebug | PHP | Profiling, tracing, debugging | Free |
| Laravel Telescope | PHP (Laravel) | Requests, exceptions, logs, queries | Free (MIT) |
| rack-mini-profiler | Ruby | SQL, flame graphs, memory | Free (MIT) |
Prefix was local. Retrace was production.
Prefix only ever covered your own machine. If your team also used Stackify Retrace in production, that is the bigger job: Retrace shuts down on March 31, 2027, and after that nobody can log in, send data or open stored data. BMC says there is no automated migration, so every Retrace agent has to be replaced.
The local tools above don't replace production monitoring. None of them keeps history, alerts anyone or watches real traffic. For that you need an APM. Atatus has agents for every language Retrace's own agents supported, plus Go, and also accepts OpenTelemetry data. That means the instrumentation you use with a local viewer during development can send the same data to Atatus in production.
To plan the production side:
- Stackify Retrace end of life: dates, what stops and what to do
- How to export your Retrace data before the deadline
- Migrating .NET apps from Retrace to Atatus
- Replacing Retrace agents in Java, PHP, Node.js, Python and Ruby
- How Atatus compares with Stackify Retrace
Frequently asked questions
Is Stackify Prefix shutting down?
No. BMC Helix says Prefix is not being shut down on March 31, 2027, and customers are expected to be able to keep using it. Premium support ends on that date, and Prefix gets no further feature updates.
Is Stackify Prefix Premium free now?
BMC's migration guide for Retrace customers says that for developers who use Prefix on their own machines, its premium features are now available at no cost. Premium support itself ends on March 31, 2027.
What is the best free alternative to Stackify Prefix?
For a Prefix-like view of each request in any language, a local OpenTelemetry viewer such as the standalone Aspire dashboard is the closest match. For a single language, tools like Django Debug Toolbar, Laravel Telescope, rack-mini-profiler or Visual Studio's diagnostic tools cover the same ground without OpenTelemetry.
Does Atatus replace Stackify Prefix?
Not directly. Atatus is a production APM, like Retrace, not a local profiler like Prefix. The Atatus agent can run in development and staging too, but for day-to-day local debugging most teams pair a local tool with an APM in production.


