Skip to content
SPECIFICTION
Get listed

Akto API Security Platform vs Automatic API Attack Tool

Akto API Security Platform

akto.io

Automatic API Attack Tool

github.com

Side by side

FigureAkto API Security PlatformAutomatic API Attack Tool
Price from—Free
Free plan—Yes
Free trial——
Open source——
WebYes—
Windows—Yes
LinuxYesYes
APIYes—
Self-hostedYes—
Plans published11
Spec score · API Security Testing Software8.0 (#9)8.2 (#7)
CI/CDAkto supports running API security tests in CI/CD pipelines.The project says it was built with CI/CD in mind and describes running it in a Jenkins job triggered by a schedule or code push.
PurposeAkto helps security teams discover, test, and monitor APIs using real traffic and dynamic analysis.The tool takes an API specification as input and generates and runs attacks based on it.
SupportAkto lists in-app Intercom, Discord community, and email as support channels.The README directs users to source code documentation and gives an email address for questions; it directs bug reports to GitHub Issues.

Plans

Akto API Security Platform

  • Akto API SecurityPriced on request

Akto API Security Platform pricing →

Automatic API Attack Tool

  • MIT-licensed open-source toolFree

Automatic API Attack Tool pricing →

In their own words

Akto API Security Platform

Akto API Security Platform has no write-up on Specifiction yet; its figures are above.

Visit akto.io

Automatic API Attack Tool

Automatic API Attack Tool is a free, MIT-licensed, self-hosted security tool for Windows and Linux. It takes a Swagger 2.0 API specification in JSON or YAML and generates and runs attacks from that definition. Fuzzing scenarios send generated values within the specification’s boundaries and values that violate them, including random invalid values for checked parameters. The project describes extensibility for attack types such as illegal resource access, XSS, SQL injection, and RFI, and supports authorization and input-validation testing. It reports request details, expected-response checks, and a summary. TestNG results are written under build/testng-results, while bad requests are saved in a bad_requests folder. Optional host and port arguments support routing through a proxy. The project is intended for CI/CD and describes scheduled or code-push Jenkins jobs. Running it requires Java 8 or higher and Gradle. Windows build instructions use gradlew.bat build; Linux instructions create an executable from a shell script and the JAR. API discovery is not included.

Visit github.com