Grafana Pyroscope

Community

Continuous profiling backend — find CPU and memory hotspots across your fleet without attaching a profiler per request.

Runs	grafana/pyroscope:1.16.1
Stack	go
Provisioned for it	Nothing, it's self-contained
Verified	Not yet

Why deploy on Railyard

Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.

Deploying Grafana Pyroscope is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.

Good for

Continuous profiling for Go, Java, Python, Rust, and eBPF-instrumented services
Finding CPU/memory hotspots across a fleet without attaching a profiler per request
Correlating profiles with traces when paired with a tracing backend

Good to know

Runs as a single monolithic process with local disk storage — fine for one team's workload, not sized for multi-tenant or high-cardinality production use
No authentication is enabled by default — don't leave this publicly reachable without putting it behind your own access control
Point your app's Pyroscope client (or Grafana Alloy) at this app's URL on port 4040 to start sending profiles

Project docs ↗