Skip to content

Getting started

DXDT is an agentic SRE & FinOps platform: it investigates incidents, continuously hunts cost and reliability findings across your cloud estate (Pulse), and answers operational questions with an agent that can actually look at your infrastructure — and it remembers what your team teaches it.

New here? Read Core concepts first — six ideas explain everything else.

Your first hour

  1. Connect your main cloud from the in-app Marketplace. Every integration has a step-by-step install guide, and everything DXDT does is grounded in what it can see.
  2. Let the first scan land. Pulse usually surfaces real findings — with defensible savings estimates — within the first day.
  3. Set your timezone and report hour (Team → Features) so the Morning Report arrives with your coffee, not someone else's.
  4. Teach DXDT five facts your team knows and no document records — see Institutional memory. This is what makes DXDT yours.
  5. When something breaks, run it through a war room — the record compounds.

The best practices page condenses what the teams who get the most out of DXDT do differently.

Surfaces

Surface For Docs
Web app Day-to-day: chat, war rooms, Pulse, Morning Report, memory Guides
CLI (dxdt) Terminal workflows, scripting, the CI change gate CLI
Public API (/api/v1) Custom integrations, automation API reference

Five-minute CLI start

For terminal-first users and CI:

curl -fsSL https://<your-dxdt-host>/install.sh | sh
dxdt login --host https://<your-dxdt-host>   # opens the browser, mints a token
dxdt ask "top 3 cost anomalies this week"
dxdt pulse findings --status open --json | jq '.[].title'
terraform show -json plan.out | dxdt plan review

dxdt login uses your existing DXDT account (Google/Microsoft sign-in, or SSO if your organization has it configured) and stores a personal access token locally. Full command reference: CLI.

Where next