Snapshot 201050

Document
Trust center
URL
https://www.aikido.dev/trust-center
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
407466 bytes
SHA-256 (raw)
81bc17caf2be57fb3bb2aba5edd3c84a4d78fb69cc8d6f9ac821b520cc53014b
SHA-256 (normalized text)
2856bebe773a7d65c5a50fefa79b14836640880d14b39bd85ac6c0fde9e74f66

Normalized text

Scripts and page chrome removed; this is what change detection compares.

EN
Login
Start for Free
No CC required
We take our own
security seriously
Due to the sensitivity of the data stored in Aikido, security on our own platform is our highest priority.
Privacy & GDPR
Aikido is in full compliance of the
General Data Protection Regulation (GDPR).
Learn more
Compliance
Aikido is ISO 27001:2022, ISO 42001 & AICPA's SOC 2 Type II compliant, and FedRAMP Certified: Class C (Moderate).
Request Certificates
Pentesting & Bug Bounties
Aikido conducts annual external
pentests and maintains an active
bug bounty program.
Message help@aikido.dev with your Intigriti
username to get invited to the bug bounty program.
Request Bug Bounty Access
CREST Member
Aikido is CREST accredited for penetration testing. Our human-led pentests follow processes CREST has independently reviewed.
View our CREST listing
Aikido
never stores your code.
Aikido doesn't store your code after completing the analysis. We perform actions such as git clones in a fresh docker container for each repository. After analysis, the data is wiped and the docker container is terminated.
Online scanning
For GitHub, no refresh or access tokens are stored in our database. An Aikido database breach would not result in your GitHub code being downloadable. By default, our integrations require a read-only scope.
Local scanning
Alternatively, you can run Aikido locally (on-prem) as well. Download the Aikido local scanners to get started.
Read documentation
Trusted by 150k+ orgs
|
Loved by 300k+ devs
|
4.7/5
Lovable
Pendo
Revolut
Soundcloud
Niantic
n8n
Deel
Visma
Handshake
Joe & the juice
Runway
Too Good To Go
NiCE
Belfius
Lovable
Pendo
Revolut
Soundcloud
Niantic
n8n
Deel
Visma
Handshake
Joe & the juice
Runway
Too Good To Go
NiCE
Belfius
Faq
Frequently Asked Questions
Can I try Aikido without giving access to my own code?
Yes - you can connect a real repo (read-only access), or use our public demo project to explore the platform. All scans are read-only and Aikido never makes changes to your code. Fixes are proposed via pull requests you review and merge.
What happens to my data?
We clone your repositories into short-lived, isolated environments created just for your scans. These environments exist only for the duration of the analysis, which usually completes in one to five minutes. Once the scan finishes, every clone and container is automatically removed.
Does Aikido make changes to my codebase?
We can’t & won’t, this is guaranteed by read-only access.
What do you do with my source code?
Aikido does not store your code after an analysis. Some analyses, such as SAST and Secrets Detection, require a git clone operation. More detailed information can be found on help.aikido.dev.
How can I trust Aikido?
We’re doing everything we can to be fully secure & compliant. Aikido has been examined to attest that its system and the suitability of the design of controls meets the AICPA's SOC 2 Type II & ISO 27001:2022 requirements. Find out more on our Trust Center.
Does Aikido require agents?
The core platform is API-based, so you are up and running in minutes. This also makes Aikido less intrusive. We use an on-device agent for Device Protection, our endpoint security tool.
‍
‍
Do you have a bug bounty program?
Yes we do! You can find our bug bounty programs on Intigriti.
Availability
Aikido is available on any device, worldwide.
Health checks & simple pings of the components are used to check if the functions are operational.
Open Status Page
Release process
1
Integration and automatic end2end testing in CI ensures that updates do not break any use cases required by users.
2
Changes are communicated to the customer success team in a timely manner.
3
Test environments can freely be created upon request.
4
Changes are communicated to end users in-app.
5
There is no beta environment that contains newer features. Experimental features are released by feature flagging.
Responsible Disclosure Policy
At Aikido, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.
If you discover a security vulnerability, we would like to know about it so we can take steps to address it as quickly as possible.
hello@aikido.dev