Jump to Content
Akita Software
DocsChangelogFAQs
AkitaBlogGitHubAkita Software
AkitaBlogGitHub
DocsChangelogFAQs

About Akita

  • Welcome! 👋
  • What Akita Gives You
  • How Akita Works
  • System Requirements
    • Akita Client Requirements
    • API Traffic Requirements
  • Talk to Us

Get started

  • Set up the App
  • Capture Traffic with the Akita Client
  • Understand Your API with the Akita App

Generate API Models

  • Where Should I Run the Akita Client?
  • Single Host/VM
    • Install on Linux
    • Install on macOS
    • Install on Docker
  • AWS ECS
  • AWS Fargate
  • 🚧 AWS Lambda 🚧
  • Azure App Service
  • Docker
  • Fly.io
  • 🚧 Google App Engine 🚧
  • Kubernetes
  • Other Ways to Build API Models
    • Django on Heroku
    • Express.js
    • With Browser HAR Files
    • With Postman Collections
    • With Proxies
  • Troubleshooting

Understand your API Models

  • Explore API Models
  • Automatically Track Changes
  • Explore Your API Graph
  • Data Formats

Customize API Models

  • Customize Packet Capture
  • Customize Path Parameters
  • Customize Host Mapping
  • Tag Your Traffic with Versions

Share API Models

  • Managing Teams

CLI Reference

  • apidiff
  • apidump
  • apispec
  • get
    • get graph
  • learn
  • setversion
  • upload
  • AkitaURIs
  • Choosing an output format

More about Akita

  • Data Access & Handling Policy
  • Terms of Service
  • Privacy Policy
  • Status Page

🚧 AWS Lambda 🚧

Coming soon!

Suggest Edits

AWS Lambda does not support network-level packet capture, which means you can't deploy the Akita Client on AWS Lambda. It's on our roadmap to build a solution for this!

Please reach out to us if you would like to use Akita to monitor your AWS Lambda deployments so we can put you on our list.

In the meantime, check out Other Ways to Build API Models for alternatives.

Updated 2 days ago


Did this page help you?