Works with the stack
you already have.
Send server-side telemetry with OpenTelemetry or your existing open shipper—there is no proprietary Epok agent to install. Browser RUM and replay use a web snippet, because browser signals need browser instrumentation.
Six signal types, one endpoint — correlated by shared service and trace ID once they arrive.
If you can send HTTP, you can send to Epok. No proprietary wire format.
Add Epok as an output alongside your current tool — run both in parallel during evaluation.
Host, container, Kubernetes, and database metrics — point any of these at the same endpoint over OTLP or Prometheus remote_write. Epok keys them to your services so they show up in the investigation, not a separate dashboard.
Wherever you deploy, your telemetry can flow to Epok. Step-by-step guides in the docs.
Grouped incidents and cited root cause, delivered to the channel you already watch.
Don't see your shipper?
Almost anything that emits logs can reach Epok over one of the protocols above — most setups are a few lines of output config. The docs have copy-paste snippets, or email [email protected] and we'll help you wire it up.
Send a copy of your telemetry. See it light up.
The 14-day trial takes whatever you already ship. Run it alongside your current tool and compare what each one catches.