Home / Security / Aikido Security / Accounts with a subscription

Aikido Security account with a paid subscription

Aikido

No offers yet

Nobody has listed this product yet. We do not invent prices: a displayed price is a public offer, and it only ever comes from a live seller.

Log in to get the notification: without an account there is nowhere to send it.

Plans

Basic

  • Security review on every pull request
  • Code quality checks in pull requests
  • Findings pushed to Jira, Linear and other trackers
  • Sync to compliance platforms such as Drata and Vanta
  • Reports and analytics, plus bot and malicious request protection
  • Billed per developer, purchasable self-serve or through cloud marketplaces

Pro

  • Everything in Basic plus on-prem scanning without shipping code outside
  • Virtual machine scanning and external attack surface monitoring
  • Malware detection in your dependencies
  • CVE-free base images and same-day support
  • A monthly credit allowance for offensive testing, deep pull request review and whole-codebase analysis
  • Unlimited AI-generated fixes

Advanced

  • Everything in Pro for organizations with stricter requirements
  • Broker for internal applications and a private package registry proxy
  • Higher API rate limits and FIPS-grade base images
  • Priority support in Slack or Microsoft Teams
  • FedRAMP authorization
  • A larger monthly credit allowance for the AI features

Enterprise

  • Modules taken separately: code, cloud, offensive testing, runtime defence
  • Multi-tenant portal for groups of companies and agencies
  • Deployment inside your own perimeter
  • Training, onboarding and a dedicated success manager
  • Continuous penetration testing on every release rather than once a year
  • Scope and module mix agreed under a contract

Plan contents as published by the vendor; seller prices arrive at launch.

What you get

A ready Aikido organization with a paid plan: connect your source hosting and cloud, and within minutes you see the picture across dependencies, secrets and configurations. The main thing to establish is whose email owns it and whether you get admin rights: without them you cannot connect new repositories, change limits or see credit spend. Check the remaining monthly credits at the moment of delivery — if they are already spent, offensive testing is unavailable until the next period. The number of paid cycles and the presence of live connections hint at whether the organization was used for work or assembled for resale.

About the service

One service instead of a shelf of separate tools: dependency analysis, flaws in your own code, leaked secrets, container image scanning, infrastructure-as-code and cloud misconfiguration checks. The AI works in the two places where it pays off most: it filters out false positives in code analysis on its own and offers a ready fix you can accept as a pull request without unpicking the rule by hand. A separate offensive line has agents run a penetration test against the application and its interfaces, finding broken access control, business-logic flaws and prompt injection, and producing a report that SOC 2 and ISO 27001 auditors accept. Scanning is embedded in the IDE, in pull requests and in the build pipeline, while deep whole-repository analysis and offensive testing are metered as credits inside your plan. A solid pick for a team that would rather not keep five subscriptions and stitch their reports together by hand.

The same from another vendor