The DFE console, where an operator sets up and runs a deployment.
It manages the deployment through the dfe-engine API alone, never past it to the infrastructure. Its Observe pages are served from a separate URL and framed inside the console, and the console sends its telemetry to an OTLP endpoint when OTEL_EXPORTER_OTLP_ENDPOINT is set.
- Sources and their ingest rules, defined in one place.
- Schemas and meta schemas, transforms, field maps and the library they draw on.
- Detection rules and hunts.
- An Observe view for searching and charting the data.
- Platform and admin settings, and a first-run setup flow.
corepack enable # yarn 4, node >= 24
yarn install
yarn dev # turbo dev - app on http://localhost:3000On a system-installed node (/usr/bin/node) corepack enable fails with
EACCES on its symlink. Either corepack enable --install-directory ~/.local/bin (any writable directory on your PATH), or prefix each command
with corepack -- corepack yarn install -- which needs no enable. A yarn 1
on your PATH is the wrong yarn for this lockfile.
Point it at an engine with NEXT_PUBLIC_API_URL and INTERNAL_API_URL. With neither set, every page says the engine URL is not configured.
Full environment reference: docs/local-development.md.
A Turborepo/yarn-workspaces monorepo with one shipped app and six packages:
| Workspace | What it is |
|---|---|
apps/dfe-core-ui |
the Next.js app - the one artifact shipped (standalone container) |
packages/dfe-engine-types |
a committed copy of the engine's OpenAPI specs + generated types |
packages/dfe-icons |
SVG -> React icon codegen + storybook |
packages/dev-logger |
small shared logging helper |
packages/dfe-json-viewer-cn |
the JSON viewer component |
packages/dfe-shared-ui |
shared React components and utilities |
packages/typescript-config |
shared tsconfigs |
| Doc | Covers |
|---|---|
| docs/architecture.md | app + package map, route groups, where dfe-ui sits in the DFE stack |
| docs/console-and-the-flow.md | the four menu groups, and how a source page draws the engine's flow resolver |
| docs/engine-api-client.md | the typed engine API client and how the engine spec is synced |
| docs/authentication.md | local and OIDC sign-in, session renewal, sign-out and redirects |
| docs/observe-embed.md | how the Observe pages are framed in the console |
| docs/build-and-deploy.md | standalone build, container, publish |
| docs/local-development.md | toolchain, env vars, tests, storybook, running natively on a Mac |
| apps/dfe-core-ui/e2e/README.md | running the Playwright suite against a console and an engine |
The suite's published docs are at https://dfe.docs.hyperi.io, and this repository's pages at https://dfe.docs.hyperi.io/dfe-ui/.
How to work in this repo, the commands that prove a change and what tends to bite are in CONTRIBUTING.md. A question that is not a bug goes in an issue as well.
Open bugs: this repo | whole DFE suite
BUSL-1.1, see LICENSE.