Core concepts

Six ideas explain everything else in DXDT.

Tenant

Your organization. Every session, finding, incident, learning, and token is tenant-bound. The API never returns another tenant's data, and agent tool calls resolve your tenant server-side — it is never a parameter a client can override.

Integrations

Connected via the in-app Marketplace (cloud providers, monitoring, ticketing, and more). Integrations define what DXDT can see; every claim DXDT makes is grounded in data from a connected integration. More connections → better findings, better incident context, better plan reviews. Each integration ships with a step-by-step install guide in the marketplace.

The graph

DXDT continuously maps your infrastructure into a dependency graph: entities (services, databases, load balancers, clusters…) and the relationships between them. The graph powers blast-radius answers ("what depends on this replica?"), incident context, and plan review. You can see what's mapped on the Memory page.

Findings & recommendations (Pulse)

Pulse is the always-on scanning engine. It produces findings (a discovered cost, reliability, or security issue, with severity and evidence) and recommendations (the suggested action, with estimated monthly savings where applicable). See the Pulse guide for the lifecycle and how savings figures are computed — DXDT distinguishes identified savings (estimates on grounded findings) from actioned ones, and never reports "realized" savings that haven't been confirmed against your bill.

Incidents & war rooms

An incident is a tracked operational event (SEV1–SEV4) with a timeline, a commander, and optionally a war room — the live collaboration surface where humans and the DXDT agent work the problem together. Everything is recorded; resolved incidents become searchable history. See War rooms & incidents.

Institutional memory

The facts your team teaches DXDT — corrections, conventions, tribal knowledge — stored with attribution ("taught by dana, Jun 2026") and injected into every future agent run: chat, Pulse scans, resilience analysis, and plan reviews. This is what makes DXDT yours: two DXDT tenants with identical infrastructure behave differently because their teams taught them different things. See Institutional memory.