| Kubernetes Daemonset | You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration. | /files/SUahjM9YtaKPVT6M2M1Q | /pages/iYvzrAu7CguT468kXVb9 | |
| OpenShift | OpenShift should be used as a traffic connector if you are deploying and managing containerized applications using OpenShift. | /files/nVRId7uQzAUSVaKCDl6V | /pages/fKKLLFI9i7vaptlmzgr3 | |
| eBPF | Akto-eBPF setup is recommended for mTLS systems when TLS termination happens at a proxy. | /files/Hc2nMfE7P3Qmhq3sgz1Z | /pages/RdPmErdJcjf1QeMk5mm6 | |
| eBPF on mTLS | Akto-eBPF-mTLS setup is recommended for mTLS systems where TLS termination occurs at the application. | /files/Hc2nMfE7P3Qmhq3sgz1Z | /pages/M5a5Pe1qvWEsrgZAJMu2 |
| Apigee | Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs. | /pages/JH1OmW8yIqKZDHN84CpE | /files/6Ab9i1dd0vPEhGPDpGce | ||
| Azure API Gateway | Azure API Gateway setup is recommended if you are using Azure's API Management service to manage, secure, and analyze your APIs. | /pages/v3ndPVrKjVABS1z6YBYo | /files/smHwrrSwoMrJJo5QGIAF | ||
| Cloudflare | You should use Cloudflare as a traffic connector if you are leveraging Cloudflare's CDN and security features to manage and optimize your API traffic. | /pages/dJ9wIuhlODMmYau7jFuY | /files/yBhps5Nv6uRZDAAbQEM0 | ||
| F5 | F5 setup is recommended if you are using F5's BIG-IP as an API gateway or load balancer to manage and control your API traffic. | /pages/ZGoj62PYmbhZ52J0JojO | /files/w8zod5p0yfxgqknnecJ3 | ||
| Kong Mesh | Use this set-up if you are utilizing Kong's service mesh capabilities to manage and secure your microservices and APIs. | /pages/8c5doDurdWdXUcDvjqF9 | /files/C1znPLGuz3ZC6FpE9V8G | ||
| Layer 7 | Layer7 is recommended if you are using CA Technologies' Layer7 API Management for securing and managing your APIs. | /pages/sT0HIvPUetPr0apcFPNA | /files/5eJZswceZRbfrnY3ZjoZ | ||
| 3Scale | This setup is recommended if your APIs are managed by 3scale. | /pages/HqIHtWu74Mmtpm8chqIg | /files/jJWoLOITRqT7rrfW2Mys | ||
| NGINX | This setup is recommended if your APIs are routed by NGINX. | /pages/B9s3MOHZYWm7tShmZynP | /files/i4U09YR0RDXQZPPBkocn | ||
| HA Proxy | HA Proxy should be used as a traffic connector if you are leveraging HA Proxy for load balancing, high availability, and proxying HTTP and TCP-based applications. | /pages/CGn9ZF3FaNGesxd30wQq | /files/JBLpuuNGG00Qg7fVBGdf | ||
| Envoy | Akto-Envoy setup is recommended if your APIs are routed by Envoy. | /pages/PRFkHXiJ8XYmrsmPSeP5 | /files/TTSiw2CAEUs1iw1PFhoF | ||
| Istio | Akto-Istio setup is recommended if your APIs are routed by Istio. | /pages/rxSll4erNY2bzmW51uBO | /files/Dxna5GoZsp142BlQyXEV | ||
| Kong | Kong Gateway is an open source API gateway, built for multi-cloud and hybrid, and optimized for microservices and distributed architectures. | /pages/sVAm3aCwHelRqrjejxEp | /files/C1znPLGuz3ZC6FpE9V8G | ||
| IBM API Connect | This setup is recommended if your APIs are managed by IBM API Connect | /pages/46iC7R1ZUqCnBSV02ERr | /files/IdDWeooTzXj4LaosGfRP | ||
| Citrix | Citrix setup is recommended if you are using ADC (NetScaler) to manage, secure, and optimize your API traffic. | /pages/kAVrDIzBCMElRb7vT2Zy | /files/EB8rTIdBDT5fAKWTxgDe | ||
| Azure App Services | Azure App Services setup is recommended if you are using Microsoft's web app service with sidecar containers to collect and analyze your API traffic. | /pages/VsFPYKjZ8CRk9G0qm2rl | /files/7yob8JEKLTi2rQuyNI22 | ||
| MuleSoft | Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs. | /pages/TCOVJCetYq9oeiMwifLn | /files/XHBEdqaVgfZ1GqbreVLP |
| AWS Mirroring | You can deploy Akto in AWS and collect traffic through traffic mirroring. | /pages/gPEp4kGRJ7Rtg2ohCdya | /files/0uE9KlR9LGYUP3T3rqW9 | |
| GCP Mirroring | This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time. | /pages/2KiafZeeb7QaXst0NezO | /files/ow0Zcz0rNTDoRYXSRLNV |
| AWS API Gateway | Akto-AWS-API-Gateway setup is recommended if you are using AWS API Gateway. | /pages/qyVRTH58h7efOmEcf7ED | /files/hz7o6hpr2N4ESHMhfa7d | |
| AWS EKS | You can deploy Akto in AWS and collect traffic through a daemonset on your AWS EKS configuration. | /pages/yIylQBR0fp8zTQKdgzdW | /files/7LWdCFyhOEADLpFrxQVj | |
| AWS Fargate | AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances. | /pages/XoPLBuQy8P5g4Zau300e | /files/LjRBZruh6ly88LAAnib0 | |
| AWS Beanstalk | You can deploy Akto in AWS and collect traffic through mirroring on your AWS Beanstalk setup. | /pages/CIOAzaPZUptJbvnXn0LE | /files/jm8B59aTEjffhUWRadtI | |
| AWS ECS | You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster. | /pages/sf4YnyRTX16CUS3UAmUq | /files/EpSyKE932B2Oi25oczYW |
| GCP Mirroring | This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time. | /files/ow0Zcz0rNTDoRYXSRLNV | /pages/wigUw3mbYC6Nz0HuIs0E | |
| Apigee | Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs. | /files/6Ab9i1dd0vPEhGPDpGce | /pages/NEBGlgXefxobvny74tUQ | |
| Google Cloud Run Functions | This setup is recommended if your applications are deployed using Google Cloud Run Functions. | /files/imVFyuoqcF8QflRtbYZL | /pages/cvYGgdp2ZkLvyTBMDoNc | |
| Google Cloud Run | Google Cloud Run setup is recommended if you are using Google's serverless platform. | /files/xc0TYTrjrWeLkQblkdfU | /pages/1GN3BuQNPpHTsCluIRMY | |
| GKE | This setup is recommended if you are running containerized applications on Google Kubernetes Engine. | /files/Udhp8xY7NUScb2ys8q1u | /pages/h0RPMVnwFoLJfaYRPqnW |
| Azure App Services | Azure App Services setup is recommended if you are using Microsoft's web app service with sidecar containers to collect and analyze your API traffic. | /files/7yob8JEKLTi2rQuyNI22 | /pages/VsFPYKjZ8CRk9G0qm2rl | |
| Azure API Mangement | This setup is recommended if you are using Azure's API Management service to manage, secure, and analyze your APIs. | /files/smHwrrSwoMrJJo5QGIAF | /pages/v3ndPVrKjVABS1z6YBYo | |
| AKS | This setup is recommended if you are deploying applications on Azure Kubernetes Service. | /files/5CKpKGAGvt1DN8vlA8CG | /pages/slO4npAmojBBF31jCC3L | |
| Azure OpenShift | Azure OpenShift setup is recommended if your containerized applications are running on Azure Red Hat OpenShift. | /files/nVRId7uQzAUSVaKCDl6V | /pages/76wp1H3nt8EL3vQOkVGI | |
| Azure Container App | This setup is recommended if your applications are deployed using Azure Container Apps. | /files/SBX5aX4QrvD55Ry70CuR | /pages/XHr4AM6sad4ymTmGIVJv | |
| Azure Functions | Azure Functions setup is recommended if you are using Azure's serverless compute service. | /files/39T8kuIVMSC1esh9AfyF | /pages/tDtpNViMhmxQUC6pWote |
| Go | Use where Go-based services are deployed. | https://github.com/akto-api-security/gomiddleware | /files/16SKUyUzf7JclMIsBijC | |
| Java | You can use Akto's Java agent to capture API traffic directly from your Java applications. | https://github.com/akto-api-security/java-servlet-api-logging | /files/98SnyJNtnZN1vTJymYQX | |
| NodeJS | This setup is ideal for environments where NodeJS-based services are deployed, ensuring seamless integration and real-time traffic monitoring. | https://github.com/akto-api-security/express-api-logging | /files/B8y0GYEudKXuIstZEN33 | |
| Python | Use where Python-based services are deployed. | https://github.com/akto-api-security/flask-middleware | /files/E3t5YSqWYEvJVcHWaLTf |
| Docker | This setup is recommended only if other setups for AWS or GCP don't work. | /pages/AWqylABCOebwFeGqNKoY | /files/GT9vFe88RRDSRAFg4mV5 | |
| eBPF (bare Linux, TLS) | Install the dockerless eBPF tarball on a Linux VM or host to capture TLS traffic without Docker. | /pages/PErYME4f8pbFIfAp3eWr | /files/Hc2nMfE7P3Qmhq3sgz1Z | |
| TCP Agent | This setup is recommended only if other setups for AWS or GCP do not work. | /pages/LfCPeVu7n0LxxvKIge92 | /files/q2UamY2Tz2mdBBXyqM0d |
| Burp Suite | You can deploy Akto on your machine and download Akto's Burp extension to collect API traffic. | /pages/7V0Vb2dSF6b6e9ZgpYDE | /files/eT86MG6BQqmu90TYN7pp | |
| Postman | This setup is recommended if you have updated API collections maintained in Postman. | /pages/r9NB0Eo9o2fanTsdKbUi | /files/RPakkKe31PPyMjAWnycr | |
| Har File Upload | For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto. | /pages/Fm01z3tJSCUKJg2czoa7 | /files/IqWGyX3shOzIJ1pkzYtT | |
| OpenAPI | Upload Open API/Swagger specification file to Akto to create an API inventory. | /pages/gwLedSLOPVhMScIUiSbR | /files/C0TawNtOZLlnDBMtPrIm | |
| SOAP API | Upload WSDL file using Postman to Akto to create an API inventory. | /pages/NQaqlbKNlswoHdgUQvzM | /files/v3PLeg2wrmwehDC5acJD |
| Imperva | Import API definitions discovered by Imperva into Akto's API inventory. | /pages/DdpTh79DoD4cy3cEvduE | /files/iwzczepERECVS2bUsAVF | |
| Wiz | Connect Wiz as a traffic source to periodically import API endpoints discovered by Wiz into Akto's API inventory. | /pages/o4d9avpsQhsDtMRxdoxm#connect-wiz-traffic-source | /files/l5qY7YOg2PUWUDUKcUy9 |