Supported Languages

KloudMate doesn’t ship its own profiling agent — it speaks the Pyroscope ingest protocol at https://otel.kloudmate.com/v1/profiles/pyroscope, authenticated with Basic auth (KloudMate as the username, your Ingest API key as the password). Any Pyroscope-compatible SDK works out of the box; pick your language below for the exact install and config steps.

Go pyroscope-go — CPU and heap profiling for Go services.

Java The Pyroscope Java agent, attached at JVM startup.

Python pyroscope-io — configure once, before the rest of your app.

Node.js @pyroscope/nodejs — CPU and wall-clock profiling for Node services.

Ruby The pyroscope gem, configured with a block at boot.

.NET The Pyroscope .NET profiler, loaded via CLR environment variables.

Rust The pyroscope crate with a pprof-rs backend.

eBPF Profiler Whole-host profiling with no code changes, for anything not listed above.

Which profile types you get

Every SDK reports CPU (wall or on-CPU time, depending on the runtime); several also report memory. The exact set shows up in Profile Types once your service has sent its first batch:

Language	CPU	Memory
Go	✅	✅ (heap)
Java	✅	✅ (alloc, via async-profiler)
Python	✅	✅ (if built with tracemalloc support)
Node.js	✅	✅ (heap)
Ruby	✅	—
.NET	✅	✅ (alloc)
Rust	✅	—

Not on this list?

If your language isn’t here, check whether it has its own community Pyroscope SDK, or run the eBPF profiler instead — it samples any process on the host without touching application code, at the cost of function-level (not line-level) detail.

Related

Profiling Overview The five views this data feeds into once it's flowing.

API Keys Create the ingest key every SDK below needs.