A Delphi dashboard is a living workspace built around a single question your organization needs to answer continuously. We call it a command center because it’s the room you walk into every day to see state, spot change, and act on it — not a static report you ask someone to run. Every KPI, visualization, alert, and agent in Delphi lives inside a command center, so creating one is the first step to doing anything useful on the platform.
When you click Create new command center from the home screen, you land on the Choose your domain picker. The grid shows the curated domain packs Delphi ships with — pick one to skip straight to a working starter — plus a Custom card with a dashed border. Choose Custom when none of the packs fit your problem and you want Delphi to design the command center around your description in chat.
Path one: pick a domain pack
If one of the packs is a good fit, click it. Each pack ships with a curated set of KPIs, child initiatives, suggested visualizations, and recommended connectors for that domain. Today’s catalog spans Financial Planning and Analysis, Agricultural Operations, Water Resources and Environmental Monitoring, National Governance and Sovereign Intelligence, water-stressed utility operations, and pharmaceutical supply-chain compliance. The financial pack, for example, recommends connectors for Alpha Vantage, FRED, SEC EDGAR, and BLS time series; the pharma pack ships with controlled-unclassified-information handling baked in. You’ll see the recommended sources listed before you generate, so you know what’s coming.
This path is the fast one. Reach for it when one of the packs is genuinely a great fit, when you want a working command center in under a minute, or when you’re evaluating Delphi and just want a sense of what it can do. You can always edit the result via chat afterwards.
Path two: chat with the Onboarding Assistant
If you pick the Custom card instead, you land in a chat with the Onboarding Assistant — an agent that conducts a structured interview to understand your problem, your domain, the entities you care about, and the data you already have.
The interview is conversational. The assistant asks about the outcome you’re trying to drive, the constraints you’re working under, the systems of record you want connected, and the people who’ll be using the dashboard. Answer in your own words — there’s no fixed form. Behind the scenes the assistant is building a domain model and a draft command center while you talk.
When the interview reaches enough confidence to act, the assistant generates the command center for real: KPIs grounded in the entities you described, a layout tuned to your stated goals, and a set of recommended connectors based on the systems you mentioned. Your draft is saved in the browser as you go, so if you close the tab you can resume the interview where you left off.
This path produces command centers that match the shape of your actual work, not a generic template. It takes longer, but the result is tailored end-to-end.
After the command center is created
Either path lands you on the metrics page of a fresh command center. From here, the way you change anything is to talk to Delphi in chat. Ask it to add or remove KPIs, build new visualizations, wire up specific connectors, or pull in additional data sources. The chat panel on the right is the editing surface for the whole platform. See Chatting with Delphi for how to phrase requests well.
When you’re ready to bring real data in, browse the integrations catalog for the full list of supported sources and ask Delphi to connect the ones you need.
Open it for your team
A command center is more useful when the right people are in it. Once the dashboard feels real enough to share, invite your team and decide who should be able to do what using roles and permissions. You can keep a command center private while you experiment, invite a few collaborators as editors to build it out together, or open it up read-only to a wider audience once it’s stable.