Documentation
Everything you need to connect your tools, label a ticket, and read what comes back.
Getting started
Getting started
Create your organisation, connect your tools, and label your first ticket.
Members, roles, and groups
Four role templates, assigned directly to a member or to a group of them.
Cross-product connector import
Already set up Slack, GitHub, or Jira in Incident Copilot? DevOps can bring them across automatically.
Connectors
Connecting Jira
The trigger for the whole pipeline, and where the result lands.
Connecting ServiceNow
An alternative trigger to Jira, for teams that already triage in ServiceNow.
Connecting Linear
An alternative trigger to Jira, with native webhooks and native labels.
Connecting Azure DevOps Boards
An alternative trigger to Jira, for teams already tracking work in Azure Boards.
Connecting GitHub
Read the source of the affected service, and open the draft pull request.
Connecting GitLab
The GitHub alternative — works against gitlab.com or a self-managed instance.
Connecting Grafana
Optional observability context — logs, metrics, and alerts related to the ticket.
Connecting Confluence
Optional runbook context — read-only, never written to.
Connecting Slack
Optional: broadcasts fix-pipeline updates into a team channel.
On-prem agents
For a repository, wiki, or test environment with no public API at all.
Remediation actions
Kubernetes, AWS, Azure, GCP, Jenkins, ArgoCD, Terraform — actions the AI can propose, never run on its own.
Direct cloud connectors
AWS, Azure, GCP, and Kubernetes connected straight to Noviqent DevOps — restart, stop, start, scale, behind the same human approval as every other remediation action.
Choosing an AI provider
Bring your own key — or your own infrastructure entirely.
Prior investigations
Discoveries from past ticket fixes, retrieved automatically so similar tickets don't get re-investigated from scratch.