01
Define the boundary
Choose a service group, ownership domain, environment, critical user journey, or incident class. Record approved signals and fields, expected volume, data classification, region, retention, and notification destinations.
CONTROLLED EVALUATION
Bound the evaluation. Not the ambition.
Mirror telemetry from a representative production boundary while your current observability and paging systems remain the control. Prove the incident outcome against an agreed scorecard before Epok earns a wider operational role.
shadow mode · independent telemetry path · current paging authoritative · no automated remediation
THE EVALUATION CONTRACT
A reversible path from curiosity to an operational decision.
02
Deploy an isolated secondary path
Fan out approved telemetry through OpenTelemetry or an open shipper using an ingest-scoped key. Give the Epok destination its own queue, timeout, retry policy, and volume ceiling so it cannot disturb your existing path.
03
Keep the control plane unchanged
Existing telemetry destinations, monitors, dashboards, paging, and incident command remain authoritative. Epok observes, groups, and recommends; your responders decide and execute.
04
Exercise representative incidents
Use agreed production incident windows, synthetic failures, or approved failure exercises. Include enough related systems to test the cross-service topology your responders actually face.
05
Score every outcome
Classify each incident as correct, incorrect, abstained, or missed. Measure alert fanout, time from first page to verified cause, false pages, telemetry coverage, and responder effort.
06
Expand, coexist, or stop
Review the pre-agreed quality, security, and operational gates. Expand through a separately approved change, keep the bounded deployment, or revoke the key and remove the exporter for a clean exit.
DECISION-GRADE SCORECARD
Separate safe uncertainty from harmful error.
Do not combine abstentions with wrong conclusions, and do not call a trial successful because data arrived. Agree on the incident cohort and thresholds before ingest begins, then review both systems against the same windows.
CURRENT EVALUATION POSTURE
Clear about what is available—and what is not.
AVAILABLE TODAY
Google OAuth, scoped ingest/read API keys, EU-hosted primary infrastructure, DPA on request, and timestamped alert-action history.
REQUIRES ARCHITECTURE REVIEW
Capacity above published self-service limits, custom retention or residency, dedicated or self-hosted deployment, and contracted support requirements.
NOT AVAILABLE TODAY
Microsoft login, SAML enterprise SSO, SCIM, and a completed SOC 2 Type II report. Production approval depends on your organization's requirements.
Evaluate Epok at the scope your environment demands.
Inspect the product without signup, run a self-service workspace, or define a governed evaluation with us.