Pixie
px.dev
What it is
Pixie is open-source Kubernetes observability and debugging software for developers. It collects metrics, events, traces, and logs without code changes, using dynamic eBPF probes and ingestors. Users can run community, team, or custom scripts to debug as code and share sessions. Its CLI provides health checks and charts, with a browser interface available when needed. Pixie supports hosted and self-hosted deployments; its Vizier data-collection component runs in the Kubernetes cluster. Requirements include Kubernetes v1.21 or later and Linux nodes, and pods that install BPF programs need privileged access to the Linux kernel. The project lists Cosmic Cloud and New Relic Cloud as free hosted versions. Pixie lists Minikube, EKS, GKE, AKS, and self-managed Kubernetes environments. Telemetry traffic is encrypted in transit. The requirements page says telemetry passes through Pixie Cloud without persistence, while the install guide says hosted-backend telemetry data is stored exclusively on the Kubernetes cluster, not in Pixie Cloud. Listed unsupported environments include EKS Fargate, GKE Autopilot, Docker Desktop, k3d, kind, and Windows. Help options include Community Slack, a troubleshooting guide, and GitHub issues.
Spec sheet
- Purpose
- Pixie is open-source Kubernetes observability and debugging software for developers.Read 4 Oct 2026 · px.dev
- Deployment
- Pixie supports hosted and self-hosted deployments, and its Vizier data collection component runs in the Kubernetes cluster.Read 4 Oct 2026 · docs.px.dev
- Integrations
- The homepage lists Minikube, EKS, GKE, AKS, and self-managed Kubernetes environments.Read 4 Oct 2026 · px.dev
- Security
- Pixie telemetry traffic is encrypted in transit, and the requirements page says telemetry passes through Pixie Cloud without persistence.Read 4 Oct 2026 · docs.px.dev
- Support
- The project directs users to its Community Slack, troubleshooting guide, and GitHub issue tracker for help.Read 4 Oct 2026 · docs.px.dev
- Founded
- 2018Read 28 Sep 2026 · px.dev
- Cloud options
- The maker lists Cosmic Cloud and New Relic Cloud as free hosted versions of the open-source project.Read 4 Oct 2026 · px.dev
- Data collection
- Pixie accesses metrics, events, traces, and logs without code changes using dynamic eBPF probes and ingestors.Read 4 Oct 2026 · px.dev
- Debugging
- Users can run community, team, or custom scripts to debug as code and share sessions.Read 4 Oct 2026 · px.dev
- Interface
- Pixie provides a CLI for health checks and charts, with a browser interface available when needed.Read 4 Oct 2026 · px.dev
- Permissions
- Pixie pods that install BPF programs require privileged access to the Linux kernel.Read 4 Oct 2026 · docs.px.dev
- Requirements
- Pixie requires Kubernetes v1.21 or later and runs on Linux nodes.Read 4 Oct 2026 · docs.px.dev
- Storage
- The install guide says telemetry data used with a hosted backend is stored exclusively on the Kubernetes cluster, not in Pixie Cloud.Read 4 Oct 2026 · docs.px.dev
- Unsupported environments
- The requirements page lists EKS Fargate, GKE Autopilot, Docker Desktop, k3d, kind, and Windows as unsupported.Read 4 Oct 2026 · docs.px.dev
Plans and prices
Strong points and limits
Strong points
- Collects metrics, events, traces, and logs without code changes.
- Supports community, team, and custom scripts.
- Hosted and self-hosted deployments are available.
- Cosmic Cloud and New Relic Cloud are listed as free hosted versions.
Limits
- Requires Kubernetes v1.21 or later and Linux nodes.
- BPF-installing pods require privileged kernel access.
- EKS Fargate, GKE Autopilot, and Windows are unsupported.
- Telemetry storage descriptions differ between listed pages.
Who it suits
Pixie suits developers who need observability and debugging for supported Kubernetes environments and can run Linux nodes. It offers both hosted and self-hosted deployment options.
Verdict
Pixie provides script-based debugging and telemetry collection for Kubernetes, with hosted and self-hosted options. Check its environment requirements and privileged-access needs, and note the differing descriptions of hosted-backend telemetry storage.
Where Specifiction places it
- Cloud Monitoring#18 of 317.5
- Continuous Profiling Tools#18 of 307.4
- Kubernetes Monitoring#35 of 547.6
- eBPF Observability Tools#19 of 297.5
- Distributed Tracing Tools#21 of 327.6
- Container Monitoring#36 of 497.5