Parity

Parity connects to the customer's VPC, and its in cluster remediator has 'read-only access to your cluster' by default, 'the same level of read-only access as a traditional observability platform', plus a Slack app. It gathers data and tests hypotheses, and Parity describes no write action in outside systems. It names no integrations with Prometheus, Datadog or PagerDuty.

SourceParity, docs.tryparity.com/security and tryparity.comread 2026-10-06

Customers add their own runbooks, 'connect them to your existing alerts, and Parity will follow them just as you would', so the steps Parity takes are the ones the team writes. Every plan includes unlimited runbooks and runbook executions, and investigations gather cluster data and test hypotheses to reach a root cause in seconds. Parity names no branching syntax for runbooks.

SourceParity, tryparity.comread 2026-10-06

Each investigation gathers information from the live cluster and the customer's runbooks at run time, and questions about the cluster's status and configuration are answered from the cluster itself. Parity describes no persisted index, graph or knowledge store over the customer's knowledge.

SourceParity, tryparity.comread 2026-10-06

The remediator is read only by default and 'there is no way for an LLM to execute dangerous or arbitrary commands on your cluster as the access is controlled via RBAC on the remediator'. Parity suggests remediation for engineers to act on, so the team makes each change itself. Parity describes no approval step before an action goes through.

SourceParity, docs.tryparity.com/securityread 2026-10-06

The remediator's reach is set by Kubernetes RBAC in the customer's cluster, with API keys per organization, egress only connectivity and TLS on all traffic to Parity's hosted services. Parity names no attestation, SSO or user roles. Its model providers do not train on user data.

SourceParity, docs.tryparity.com/securityread 2026-10-06

Each investigation reports a root cause and remediation suggestions after testing hypotheses, and engineers can chat with the cluster to answer questions about its status and configuration. Parity describes no record of the commands, queries or steps it took.

SourceParity, tryparity.comread 2026-10-06

Each investigation gathers what it needs from the cluster when it runs. Parity describes no memory store or retained context across investigations.

SourceParity, docs.tryparity.com/security and tryparity.comread 2026-10-06

'For organizations with strict security requirements, you can self-host the entire Parity platform', and Parity can help deploy open source models on the customer's infrastructure. The standard remediator runs in the customer's cluster with egress only access. The remediator is a Kubernetes pod that installs with Helm into a namespace the customer picks, in about two minutes.

SourceParity, docs.tryparity.com/security and /quickstartread 2026-10-06

Runbooks are the customer's own ('If you have runbooks, add them to Parity'). Parity names no prebuilt agents, templates or runbook library. Plans cover unlimited runbooks, runbook executions, investigations and users, with a 14 day money back guarantee.

SourceParity, tryparity.comread 2026-10-06

Runbooks are connected to the customer's existing alerts so Parity follows them when an alert fires, and an alert opens an investigation. Engineers can also mention @Parity in a Slack message or thread to start the work.

SourceParity, tryparity.com and docs.tryparity.com/slackread 2026-10-06

Parity supports 'bring your own model providers' when the platform is self hosted, and can help deploy open source models on the customer's own infrastructure, so the customer chooses the model source. On the hosted service, the underlying model providers do not train on Parity users' data.

SourceParity, docs.tryparity.com/securityread 2026-10-06

Customers install the remediator with an organization API key and Helm, and add the Slack app. Parity names no API, SDK or MCP server for driving it. Its documentation runs to three pages, covering a quickstart, Slack setup, and safety and security.

SourceParity, docs.tryparity.com/quickstart and docs.tryparity.com/llms.txtread 2026-10-06

Each investigation ends with a root cause and suggested remediation that engineers check for themselves. Parity describes no evaluation harness, scored tests, quality gate or improvement loop for its investigations.

SourceParity, tryparity.comread 2026-10-06

Parity works through a read only in cluster remediator and Slack. It names no browser, desktop or computer control.

SourceParity, docs.tryparity.com/quickstartread 2026-10-06