What is our primary use case?
My main use case for Aikido Security is to consolidate all our application security scanning into one platform, primarily to manage multiple tools more efficiently. I use it to scan our code for vulnerabilities with SAST, check for open-source dependencies with SCA, scan our Docker images, detect hardcoded secrets, or API keys in our database, and integrate it directly into our CI/CD pipeline so that every code commit is automatically scanned before reaching production.
During the microservice migration to AWS, Aikido Security flagged critical vulnerabilities and detected hardcoded API keys, allowing us to fix both issues before they reached production.
What is most valuable?
One of the best features Aikido Security offers is the ability to scan everything in the same place, allowing us to check for vulnerabilities in our source code.
Aikido Security scans our source code for security issues, checks open-source libraries for known vulnerabilities, scans Docker images, checks AWS and cloud configurations for misconfigurations, and finds hardcoded passwords or API keys. It combines multiple security tools in one platform, making it unnecessary to have separate tools for each type of scan, which is particularly helpful for developers and DevSecOps engineers.
Aikido Security has positively impacted my organization by allowing us to rely on a single tool for scanning, which saves us money, time, and reduces overhead, making it more cost-optimized for our environment. We have been able to save at least 60% of our overall costs because we use one tool to capture different vulnerabilities across various areas on a single platform.
What needs improvement?
One area I think Aikido Security could improve is the depth of their reporting and remediation guidance; sometimes, the platform flags a vulnerability but the suggested fix lacks detail, requiring engineers to research the solution themselves. I would love to see step-by-step remediation guidelines built directly into the alerts and better integration options with more third-party ticketing tools like Jira for automation.
The user interface can feel overwhelming when there are many alerts, so a better way to prioritize and group vulnerabilities by severity would make focusing on the most critical issues easier. Additionally, I would like to see deeper integration with third-party tools like Jira and more detailed remediation guidelines built into each alert.
For how long have I used the solution?
I have been using Aikido Security for about two years.
What do I think about the stability of the solution?
In my experience, Aikido Security has been very stable, with no significant outages or downtime impacting our environment, and being a SaaS tool, it handles maintenance and updates without our concern.
What do I think about the scalability of the solution?
Aikido Security scales very well as our organization expands, handling growth without performance issues, and its licensing model scales with the number of repositories and developers, ensuring fast and consistent scans even as our code base grows.
How are customer service and support?
The customer support experience has been very positive; they are responsive, knowledgeable about their product, and provide clear guidance on configuration and integrations. They also offer a solid documentation library for common questions, though 24/7 support for enterprise customers would be an improvement.
Which solution did I use previously and why did I switch?
Before using Aikido Security, we had a combination of separate tools like Sneak for open-source dependency scanning, SonarQube for static security analysis, and Trivy for container scanning. Managing these three platforms with different dashboards, alerts, and CI/CD integrations was time-consuming and often led to issues falling through the cracks, which is why we switched to Aikido Security for its consolidated capabilities.
How was the initial setup?
The setup and onboarding took less than a day, requiring no dedicated staff to manage it since it runs automatically in the background.
What was our ROI?
There is absolutely a return on investment with Aikido Security; After implementation, we saw a 35% reduction in vulnerabilities reaching production, and our security review time per deployment dropped significantly as issues were caught much earlier in the development process.
What's my experience with pricing, setup cost, and licensing?
The pricing for Aikido Security is very reasonable compared to other application security platforms, and since it is a SaaS platform, the setup was minimal with no infrastructure to maintain. The licensing model is straightforward and scales based on the number of repositories and developers, making it easy to budget for.
Which other solutions did I evaluate?
We explored other options like Checkmarx for static application security testing and Prisma Cloud for container and cloud security, but they were either too expensive or too complex to set up and manage with more engineers. Aikido Security was easier to implement, more affordable, and covered all the key scanning capabilities we needed.
What other advice do I have?
My advice for anyone considering Aikido Security is to proceed and try it as the onboarding process is straightforward and can be completed within a day. Start by connecting critical repositories and integrating with CI/CD pipelines from day one for automatic scanning, and prioritize alerts systematically to avoid feeling overwhelmed.
My overall impression of Aikido Security is very positive; it simplifies the life of a DevSecOps engineer by consolidating tools into one platform, making application security accessible and manageable without a large dedicated team. I would recommend Aikido Security for any organization serious about shifting security left and embedding it into their development lifecycle. I give this product a rating of 8.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.