Integrations
The external connection hub — issue tracking, chat alerting and approvals, source control, Kubernetes ingestion, remediation controls, and execution windows.
At a glance
| Route | /integrations |
| Group | Admin |
| Page permission | integrations |
What it is
The external connection hub: issue tracking, chat alerting and approvals, source control, Kubernetes cost ingestion, remediation controls, execution windows, anomaly checks, and scan cadence.
Who it is for
Platform administrators wiring the product into your organisation's existing operational tooling.
How it works
ChatOps requests are authorised, not merely received
Incoming ChatOps requests are HMAC-verified with timestamp replay protection, and the acting user's platform permissions are checked before any decision is honoured.
A Slack identity alone is not authority.
Features
How to use it
Connect a chat channel first and send a test alert
Everything downstream — alerts, approvals, digests — depends on this. Confirm delivery before building on it.
Install the GitHub App if you use the source-control features
Required by PR Cost Review, CI/CD Control Tower, and Deploy & Migration. Confirm the permission check passes.
Connect Jira or Linear
So findings become tracked work in the system engineers already use.
Set continuous scanning cadence
Within your plan's permitted interval, and monitor scan freshness.
Define remediation execution windows before enabling any automation
This is what prevents an automated action firing during a change freeze or a peak trading period. It is the specific control that makes automation acceptable to operations teams.
Check remediation readiness
It reports plainly whether automation can execute, or is blocked by a missing execution role.
Configure anomaly checks and the triage digest
So problems arrive rather than waiting to be found.
Why it matters
A cost platform that requires people to visit it fails, because they do not
Routing alerts, approvals, and findings into Slack, Teams, Jira, and Linear means the product reaches people where they already work.
Execution windows are the specific control that makes automation acceptable to operations teams — they are the difference between automation as a capability and automation as a risk.
Connects to
- Powers alerting for Overview and Opportunity Queue
- Approvals for Approvals
- Source control for PR Cost Review, CI/CD Control Tower, and Deploy & Migration
- Ingestion for Kubernetes
- Execution windows for Optimization, Autopilot, and Resource Parking
Cloud Accounts
Registering and verifying credentialed links to AWS, Azure, GCP, and OCI — with separated read and execution roles and precise permission preflight.
AI Provider Accounts
Direct connections to LLM providers, so AI spend incurred outside the cloud bill is consolidated with the rest of the estate's AI cost.