Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Perses review

Free#43 of 53 in Kubernetes Monitoring

A self-hosted visualization layer for Kubernetes metrics, traces, logs, and profiles.

4.8/10Editor score
Visit Perses
Perses4.8 Visit Perses

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Perses is an open-source dashboard and visualization tool for teams operating Kubernetes and cloud-native environments. It provides a self-hosted layer for exploring Prometheus metrics, Tempo traces, Loki logs, and profiling data through dashboards and explorer views. Its Kubernetes operator, custom resources, datasource discovery, and Kubernetes-inspired RBAC make it a fit for teams building dashboards around Kubernetes operations. Web, API, and self-hosted deployments are supported, and Grafana dashboard migration is included.

The strongest case for Perses is its developer-oriented dashboard workflow. Teams can manage dashboards as code with SDKs, validate them statically with extensible lint rules, and use the CLI for API and CI/CD workflows. Kubernetes custom resources extend that approach into cluster management. Datasource discovery can use HTTP services or the Kubernetes API, while integrations include Prometheus, Alertmanager, Tempo, Jaeger, Loki, VictoriaLogs, OpenSearch, ClickHouse, GreptimeDB, Pyroscope, and Splunk. Trace views include scatter plots, Gantt charts, and tables, and log views support search and filtering.

Perses should suit teams that want an open-source, self-hosted visualization layer with Kubernetes-native management and repeatable dashboard delivery. OIDC/OAuth authentication and RBAC support access control, while embeddable components and plugin extensibility support broader dashboard use. The trade-off is scope: Perses is primarily a visualization and dashboard layer, with observability backends providing the connected data. Teams seeking native data collection or retention should choose a product designed around those responsibilities instead. For Kubernetes operators standardizing dashboards across metrics, traces, logs, and profiles, Perses offers a focused foundation rather than a complete monitoring system.

Perses pros and cons

  • Where it wins
    • Prometheus, Tempo, Loki, and profile visualization in one layer
    • Dashboard-as-code with SDKs, CLI workflows, and static validation
    • Kubernetes operator, datasource discovery, OIDC/OAuth, and RBAC
  • Where it doesn't
    • Primarily visualizes observability data rather than collecting or retaining it
    • Requires connected observability backends for metrics, traces, logs, or profiles
    • Kubernetes-focused workflows may be broader than needed for simple dashboards

Perses fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update