Aikido Security

What do you like best about the product?

I love how Aikido consolidates SAST, dependency, and secret scanning into one tool, making onboarding new projects incredibly fast—just five minutes compared to two hours before. The dependency analysis is much clearer, grouping related issues and reducing noise. The support from the Aikido team is outstanding: responses are fast, and they even alerted us to a GitLab CVE before our own vulnerability management tool did.

What do you dislike about the product?

There isn’t much to dislike, but I would say that secret scanning findings are similar to previous tools, so there’s not a huge improvement in that specific area. Also, I don’t have exact numbers for issue reduction yet, so more detailed analytics could be helpful.

What problems is the product solving and how is that benefiting you?

It solved our dependency grouping problem. I also like that it offers AI AutoFixes instead of standard recommendations.

What do you like best about the product?

I really appreciate Aikido's clear and predictable per-user pricing, which is much easier to plan for than the previous per-lines-of-code model. The integration of add-ons without hidden or unexpected costs, the strong balance of coverage and impact, and the ease of migration made Aikido stand out. It allows us to focus on security without worrying about budget overruns, and the platform supports our shift-left approach to security in development.

What do you dislike about the product?

There are currently no significant drawbacks for us with Aikido. We are still in the process of developing our KPIs and using reporting features, so I can't comment on compliance exports yet, but this is not a negative for our current needs.

What problems is the product solving and how is that benefiting you?

At Engel & Völkers Technology, we need to manage application security across multiple products while keeping remediation practical for our development teams. One of the biggest challenges is translating security findings into clear, actionable priorities.

Aikido helps us by consolidating code and dependency security findings in one place, adding the context we need to judge relevance, and providing guidance on how to resolve issues.

For us, the value is better visibility, sharper prioritization, and a more consistent remediation approach. It helps us use our security resources effectively and makes security a natural part of everyday development.

What do you like best about the product?

I’m evaluating Aikido across nine repositories as a solo developer, covering SaaS products and mobile apps. It has already spotted a shell-escaping issue I missed and flagged a high-severity dependency vulnerability before Dependabot did in my setup.

The clear overview and “inbox zero” approach make working through findings motivating. Even the free plan provides useful insights. Generating fixes as pull requests is convenient, although mine are still under review, so I cannot yet judge their end-to-end effectiveness.

What do you dislike about the product?

Some findings and fixes need more context. For example, an autofix proposed removing debug output from an internal, non-web-exposed debugging script. The potential disclosure concern is understandable, but simply deleting the output defeats the script’s purpose. I also received missing-lockfile warnings for repositories where I don’t use dependencies.

The biggest barrier for me is the jump from free to €300/month. My free account shows that additional findings exist without revealing their details.

I would welcome a smaller paid plan around €50/month for solo developers, covering 15–20 repositories. My priorities would be full vulnerability details, dependency and licence scanning, an SBOM overview, integration with tools like GitHub Issues, and PR security checks. Bulk autofix and broader extras matter less to me. That would give me a practical reason to upgrade without jumping straight to a package designed for a larger team.

What problems is the product solving and how is that benefiting you?

It gives me an additional view of security issues across my repositories and has surfaced issues my existing checks missed. Having findings together helps me assess what needs attention and work through them. The value is already visible, even though my evaluation of the paid features is still limited. While AI agents can spot this as well, Aikido is running 24/7 to spot them faster.

What do you like best about the product?

I really appreciate how Aikido enables a true shift left with seamless integration into GitHub and other cloud-based source controls. The onboarding experience is smooth, with immediate scanning and clear, intuitive access for developers. Its reachability features make it easy to trace vulnerabilities to their exact source, and the platform's clarity and flexibility in triaging issues drastically reduce alert fatigue. The collaboration with the Aikido team has been outstanding, with fast responses and fixes. The ability to respond rapidly to zero-day events and the clarity in separating base image vulnerabilities from application code are both huge time-savers.

What do you dislike about the product?

We did experience some initial glitches during integration, though these were resolved quickly with support from the Aikido team. Beyond that, we haven't used all features extensively yet, so it's too early to comment on any deeper limitations, but so far nothing has stood out as a major drawback.

What problems is the product solving and how is that benefiting you?

SCA scanning and AI-assisted flows

What do you like best about the product?

Repository scans and the automatic integration with our ticketing service. The scans run continuously across our codebases and surfaced a long backlog of small security issues that had gone unnoticed for years, the kind of thing that would normally take a dedicated audit to catch. The ticketing integration means findings land directly in our existing workflow as tickets instead of sitting in a separate dashboard nobody checks, which has saved us a lot of manual triage.

On top of that, it's genuinely easy to use. Setup was quick and the interface doesn't require a security background, so the whole team engages with it, not just the security-minded folks. And because scans run consistently across all our codebases, it's pushed us toward a shared security standard across projects that used to drift apart, an unexpected win we hadn't set out to get.

Their support has also stood out: quick to respond and genuinely hands on, not just pointing us to documentation but actually helping work through our specific setup.

What do you dislike about the product?

Honestly, nothing significant to flag yet. We're still a few months in and haven't explored every tool in the platform, so there may be gaps we haven't hit, but nothing has gotten in our way so far.

What problems is the product solving and how is that benefiting you?

Aikido is solving the problem of security debt we didn't know we had: small vulnerabilities and issues that had accumulated across our codebases over several years without anyone actively hunting for them. Before using it, that kind of continuous scanning just wasn't happening, so things slipped through unnoticed.

The benefit is twofold. First, we now have visibility we simply didn't have before, and a steady stream of concrete, actionable findings instead of periodic, manual audits. Second, because it scans consistently across all our different codebases, it's helping us enforce a shared security standard across projects that used to be handled inconsistently, which reduces risk without adding extra process overhead for the team.