Skip to main content

For Client Teams

If you build an Ethereum execution or consensus client, StereumLabs runs your code across 36 EC×CC pairings on identical hardware, captures every Prometheus metric you expose, and ships container logs to a queryable index.

Free access for client teams

Client development teams get free dashboard access so they can see how their client behaves across all paired implementations. Email contact@stereumlabs.com with your team affiliation and we'll set up an account.

What we collect for your client

  • Every Prometheus metric you expose. The full per-client metric list is in Client Metrics Lists. If you ship a new metric and we're not scraping it, tell us.
  • Container logs via Filebeat to Elasticsearch. Useful for log-pattern analysis, regression detection, and root-cause investigation.
  • Node-exporter system metrics at the host level (CPU, memory, disk I/O, network), filterable by ec_client, cc_client, role, and other custom labels in Custom Labels.

How teams typically use the data

  • Release validation. See how a new version behaves across all paired implementations under identical conditions. Examples: Prysm v7.1.1 to v7.1.2, Teku 25.12.0 to 26.3.0.
  • Regression hunting. Compare resource consumption and timings before and after a release window.
  • Cross-pairing diagnosis. Spot whether an issue is intrinsic to your client or interaction-specific to one EC/CC partner.
  • Protocol upgrade impact. See what changed at the host level after a hardfork. Example: Fusaka hardfork: hardware impact.
  • Field bug reproduction. On Enterprise, request that we replay a scenario with specific flags or versions.

Per-client dashboards

The Dashboards Catalog lists per-client dashboards authored by MigaLabs for every supported EC and CC, plus comparators for nodes vs supernodes.

Requesting changes

  • Missing metric? Email contact@stereumlabs.com with the metric name and a one-line description.
  • Want a new dashboard panel? Same channel.
  • Need a specific scenario run (your version, a specific EC/CC, a specific config)? Available on Enterprise via contact@stereumlabs.com.

Methodology you can audit

Every published run includes pinned versions, flags, hardware specs, sampling intervals, and validation notes. See Purpose & Scope for the full methodology and known limitations. Architecture & data flow shows how metrics and logs flow from your client to Grafana.