Safeguard today made it possible to run its scans inside a customer's own infrastructure, with only the results leaving. SAST scans now run on customer-managed, on-premises runners. A headless runner image handles non-interactive environments. And CI scanning can run locally on the build runner in GitHub Actions, GitLab CI or Bitbucket Pipelines, uploading results only, with no source code integration required.
Many security teams want a modern scanner but can't hand repository access to a vendor. Banks, insurers and public sector teams often stop the evaluation right there. This release removes that blocker. The code stays where it already lives. Safeguard sees findings, not source.
"The question we hear most from regulated buyers is where their code goes," said Hritik Kumar Sharma, founder of Safeguard. "Now the honest answer is nowhere."
What's new
- SAST on your own runners: run Safeguard's SAST scans on on-premises runners you manage.
- Headless runner image for non-interactive environments such as build farms and locked-down hosts.
- Local CI scanning for GitHub Actions, GitLab CI and Bitbucket Pipelines that uploads only results, authenticated with a secret key.
These options join Safeguard's existing deployment choices: SaaS, private VPC or dedicated tenancy, full on-premises, and fully air-gapped.
Setup guides are at docs.safeguard.sh. See it in action in the interactive demo Scan on your own machines.
About Safeguard
Safeguard is the AI-native software supply chain security platform. It finds risk across code, dependencies, containers and AI, and fixes it autonomously with tested pull requests. It can be deployed as SaaS, in a private cloud, on-prem, or fully air-gapped. Founded in 2024, Safeguard is headquartered in Dublin, California. Learn more at safeguard.sh.
