Prism gives platform engineers real-time visibility into every route, consumer, and error budget -- with zero instrumentation overhead. Connect your gateway in 60 seconds.
Requests monitored today
Trusted by engineering teams building on top of their APIs
Prism instruments at the gateway layer -- no SDK, no agent, no code change required.
Latency distributions, error rates, and volume trends per route -- updated every 5 seconds. Drill from the fleet view to a single route in two clicks. (demo: fictitious data)
Every API consumer gets its own traffic fingerprint. Know which client drives your P99 spike before you page the on-call.
Define SLOs per route or per consumer group. Prism computes burn rate continuously and fires a page at fast-burn threshold -- 60-second delivery P99.
Schema drift and deprecation warnings surface in the Prism console before consumers notice. Flag, notify, and track acknowledgment -- all in one view.
Kong, AWS API Gateway, Nginx, Envoy, or your own proxy. Prism reads the access log format you already emit. No sidecar, no SDK, no custom plugin required.
We replaced three dashboards with Prism. Alert noise dropped 80% in the first week. The consumer attribution view alone saved us a post-mortem.
— Kenji Watanabe, Senior Platform Engineer, Acme Platform (fictional)
Error budget burn-rate alerts changed how we do on-call. We catch fast-burn events before they reach SLO breach. On-call is back to being a safety net, not a fire drill.
— Ana Ferreiro, Staff SRE, Vortex Systems (fictional)
Connecting our Kong gateway took 12 minutes. We had route-level latency distributions in the Prism console before our standup ended.
— Dmitri Okafor, Principal Engineer, Redline API (fictional)
Flat tiers. No per-seat fees. No event volume overages at starter and growth tiers.
All prices USD. Annual billing. Self-host available at any tier -- same binary.
Straight answers. No marketing hedging.
No. Prism reads access log metadata: method, route, status code, latency, consumer ID. Request and response bodies never leave your network. For self-host deployments, all data stays inside your VPC. For managed deployments, only structured metadata is transmitted -- no payload content.
Kong, AWS API Gateway (ALB/APIGW v2), Nginx (via access_log), Envoy (via access_log_format), and any proxy that emits a standard access log. Custom log formats are supported via a declarative field mapping file. No sidecar, no SDK, no plugin required.
Median time from signup to first route-level latency chart: 14 minutes. The 60-second setup guide covers: create workspace, paste your gateway's log stream endpoint, configure access log forwarding. That is the entire integration.
Yes. The self-host binary is distributed as a Docker image and a Helm chart. No outbound internet connection required. Air-gapped license keys are available for regulated environments. Telemetry is opt-in; the default is off.
You define an SLO per route (e.g. P99 latency < 100ms, 99.9% of requests). Prism computes rolling error budget consumption every 30 seconds. When burn rate crosses a fast-burn threshold (4x over 1 hour), Prism fires an alert to your PagerDuty, OpsGenie, or Slack integration. Slow-burn (2x over 6 hours) fires a lower-priority digest.
Start a free 14-day trial -- full feature access, no credit card, no instrumentation work. Connect your gateway today.