Rookout
Rookout is a live application debugging platform founded in 2017 in Tel Aviv, Israel that lets developers set non-breaking breakpoints in running production, staging, and development applications to capture full-stack debug data — variables, stack traces, logs, and metrics — without redeploying, restarting, or stopping services. Rookout pioneered the "live debugger" category for cloud-native and Kubernetes-hosted applications and shipped language agents/SDKs for Python, Java/JVM, Node.js, .NET, Go, and Ruby that attach to running processes and stream snapshots back to the Rookout web IDE or developer's IDE. Dynatrace announced its acquisition of Rookout on July 31, 2023 and closed the deal in Q2 of Dynatrace's fiscal year ending September 30, 2023. The standalone Rookout product has since been folded into the Dynatrace platform as the Dynatrace Live Debugger (and Live Logger), and the rookout.com and docs.rookout.com domains now redirect to dynatrace.com. There is no public REST API, OpenAPI specification, webhook catalog, or CLI for Rookout — the developer surface consists entirely of language agents, deployment integration examples, IDE extensions, and the Explorook desktop helper that exposes local source folders to the Rookout web debugger. The Rookout GitHub organization remains public and continues to maintain those agents, tutorials, and integration samples under Apache-2.0.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Rookout the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Rookout scores 11.1/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Rookout
Each block below is one kind of artifact we hold for Rookout. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Rookout Trust Center
SOC 2, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA, FedRAMP, GDPR, CSA STAR
SECURITYResources
Every other property we hold for Rookout — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Build 11
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 11 ·
Access & Security 3
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/rookout · machine-readable index on apis.io