DataRobot App Framework — from component catalog to running application · flow is left → right

← Docs
An App Framework application is composed, not scaffolded once. ⓪ You install the dr CLI and point it at a DataRobot environment. ① The first dr component add lays down af-component-base, then ② each further dr component add renders one more af-component-* copier template into the same recipe repository and records its answers under .datarobot/answers/. ③ dr dotenv setup turns the components' CLI schemas into a .env; ④ dr run dev runs the folders locally; ⑤ dr run deploy runs Pulumi, which provisions every DataRobot resource. At runtime ⑥ users reach a Custom Application, which calls the ⑦ agent deployment — and that reaches the LLM Gateway, the MCP server, memory and vector databases. ⑧ Because every component is version-pinned, dr component update pulls upstream fixes into a project you have already customized. The numbered strip at the bottom narrates the whole process — click a step, an arrow label, or any box for details, or hit ▶ Walk the flow (bottom-right) to tour it; hovering a box traces its connections.
base / framework llm agent fastapi + react datarobot-mcp optional capabilities tooling platform / people numbered flow template render runtime call
scroll to pan