The CI/CD Hub is the operational view of what is shipping: real pipeline runs from your CI providers, not a status someone copied into a doc.
Real CI data
The hub reads CI runs ingested from GitHub Actions and CircleCI. Those providers send events to Malveon over webhooks, which land in a CI runs table that the hub reads. The data is real and arrives as your pipelines run.
Automation
The hub includes automation modules that act on live provider APIs using your stored OAuth tokens. For example, the flaky-test automation can open a real GitHub pull request, and the metrics and scale-prediction modules query Datadog directly.
Connect first
The hub shows real data once you connect a CI provider. Before that, it returns empty results rather than placeholder data, so an empty hub means "nothing connected yet," not "nothing happening." CI failure rate from the hub also feeds the Malvedeck project health engine.