Pixee
US platform that checks security scanner findings for exploitability and proposes fixes for your code as pull requests.
What it does
Pixee is not a scanner itself. It builds on security tools you already use, such as CodeQL, Semgrep, Snyk Code, SonarQube, Checkmarx or Veracode. Any other scanner with SARIF output can be connected too. For each finding, Pixee checks whether the vulnerability can actually be exploited and filters out false positives with a stated reason. For real vulnerabilities, it creates fixes as pull requests in GitHub, GitLab, Azure DevOps or Bitbucket. Your team decides whether to merge a fix. Supported languages include Java, Python, JavaScript/TypeScript, C#, Go and PHP, as well as infrastructure code such as Terraform or Dockerfiles.
Who it suits
Development and security teams in larger companies. It pays off when many open scanner findings have piled up and there aren’t enough people to review and fix them all by hand.
Data protection for businesses
You can run Pixee in four ways: as a cloud instance just for your company, self-hosted on a Linux VM, in your own Kubernetes cluster or fully offline. If you host it yourself, code and findings stay in your network; Pixee only needs an outbound connection for licence validation. You then connect your own language model, such as OpenAI, Anthropic, Azure AI Foundry, AWS Bedrock or Google Vertex AI, and that provider’s terms apply. Only the code snippets needed for the vulnerability in question are sent to the model. The vendor does not name an EU location for the hosted option. It also does not mention a data processing agreement or say whether customer code is used for training.
Limits
There are no fixed prices, and the vendor does not mention a free entry tier. For the status of a SOC 2 certification, Pixee refers you to its team. Pixee needs at least one connected scanner. You have to review the automatic fixes yourself before merging.