Overview

Overview

Nullify meets teams inside their existing tooling.

Nullify's preferred operating mode is asynchronous: once connectors are configured, findings, fixes, and campaign updates flow to teams automatically, without requiring them to live inside the Nullify UI.

The following connectors are available today:

• Version control — GitHub, GitLab, Bitbucket Cloud, and Azure DevOps (installation guides in the Enterprise Tier section).

• Ticketing — Jira Cloud with two-way sync for ownership, status, priorities, and manual issue creation (default issue type Task), and Linear.

• Messaging — Slack and Microsoft Teams for proactive coaching, escalations, and campaign updates.

• Developer metadata — Atlassian Compass to import team ownership and component mappings.

• Identity — OIDC single sign-on for authenticating users into Nullify.

• Cloud — AWS, GCP, and Kubernetes connectors for infrastructure context and exposure analysis.

• CI/CD — Buildkite, Jenkins, and CircleCI for build log ingestion, enabling autofix iteration on failing CI pipelines.