Works with the stack
you already have.
Send telemetry directly to Epok's owned pipeline and evidence engine. Use open shippers — no proprietary Epok agent for server-side telemetry. Browser RUM and replay use a web snippet, because browser signals need browser instrumentation.
Logs, metrics, traces, infrastructure, RUM and replay feed Epok’s owned ingest pipeline. Shared service and trace context connect them to evidence items with receipts and coverage.
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, evidence and cited analysis reach your team where it works. Missing evidence and next checks stay visible alongside supported causes.
Agents query the same evidence as your team through the MCP agent gateway. Access is on request; scoped credentials, bounded responses, receipts and coverage let clients inspect findings and what was not seen.
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. Follow it into evidence.
The 14-day trial takes whatever you already ship. Run it alongside your current tool and compare evidence, coverage and incident outcomes.