The Akita beta works for REST APIs and runs best on Docker, container platforms, and Kubernetes.

The Akita Agent should work out-of-the-box for any system that:

1. Supports packet capture or is a container with kernel privileges, and
2. Has root privileges or CAP_NET_RAW capability enabled.

The Akita Agent runs on Linux and macOS on both 64-bit AMD/Intel architectures and M1 & M2.

❗️

Windows support

We do not yet have official Windows support for the Akita Agent. While our users have gotten Akita to work as a container within the Windows Subsystem for Linux (WSL), it does not currently work to trace Windows APIs from a Docker container in WSL.

Akita currently supports only REST APIs, and the most popular API content types.

Supported Content-Types include:

• application/json
• application/x-www-form-urlencoded
• application/octet-stream
• text/plain
• application/yaml
• application/x-yaml
• text/yaml
• text/x-yaml

📘

Character Set Support

By default, Akita supports the UTF-8 and ASCII character sets. If your API is using a different character set (example: latin-1) you will need to specify it using the charset attribute in the Content-Type header.

Running on platform-as-a-service

We’re still building out support for Akita on platform-as-a-service solutions. We currently experimentally support
Express.js, and Django on Heroku [Experimental].

What if I don't meet the system requirements?

You can still check out what Akita has to offer via the OpenAPI Spec Generator Chrome Extension.

How do I try Akita?

Create your account here!