Continuous Security Assurance
SSO/SAML
You can authenticate with BuildPulse through Github and Bitbucket - both of which support SSO/SAML, and so do we.
Learn more
Penetration Tests
BuildPulse regularly runs security scans to make sure the platform is hardened with every release.
Learn more
Continuous Monitoring
We continuously monitor our security and compliance status to ensure there are no lapses.
Learn more
Securing our software supply chain
BuildPulse runs SAST scans to make sure there are no vulnerabilities introduced in our source code as well as dependencies.
Learn more
Security Awareness Training
Our team members are required to go through employee security awareness training covering industry standard practices and information security topics such as phishing and password management.
Learn more
Information Security Program
We have an information security program in place that is communicated throughout the organization. Our information security program follows the criteria set forth by ISO 27001 and SOC 2.
Learn more
SOC 2 Certified
We're SOC 2 Type 2 Certified. Contact sales@buildpulse.io for more information.
Learn more
Frequently Asked Questions
Why do I need to give BuildPulse permissions to my Git?
BuildPulse uses git metadata for its analysis – we consume repository and pull request metadata to determine flakiness of tests, generate reports, and comment on pull requests.
Does BuildPulse store source code?
BuildPulse does not store source code ever. For BuildPulse Flaky Tests and Engineering Productivity products, we only need your git metadata and test results. BuildPulse coverage uses your OAuth token to overlay source code on coverage results.
Is BuildPulse SOC II compliant?
Yes, BuildPulse is SOC 2 Type 1 Certified, currently pursuing it's Type 2 certification. Reach out to sales@buildpulse.io for more information.