diff --git a/traffic-connector/traffic-data-sources.md b/traffic-connector/traffic-data-sources.md
index 619975a..356f0f6 100644
--- a/traffic-connector/traffic-data-sources.md
+++ b/traffic-connector/traffic-data-sources.md
@@ -1,346 +1,362 @@
 # Traffic Data Sources
 
-<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Kubernetes Daemonset</strong></td><td></td><td>You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.</td><td><a href="../.gitbook/assets/image (50).png">image (50).png</a></td><td></td></tr><tr><td></td><td><strong>OpenShift</strong></td><td><p></p><p>You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.</p></td><td><a href="../.gitbook/assets/kubernetes (1).svg">kubernetes (1).svg</a></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>
-
 
 
 ### Kubernetes
 
-![](https://app.akto.io/public/kubernetes.svg) **Kubernetes Daemonset**
-
-You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.
-
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
 
-![](https://app.akto.io/public/openshift.svg) **OpenShift**
+<tr><td><strong>![](https://app.akto.io/public/kubernetes.svg) Kubernetes Daemonset
+</strong></td><td></td><td>
+You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.</td></tr>
 
-OpenShift should be used as a traffic connector if you are deploying and managing containerized applications using OpenShift.
 
 
+<tr><td><strong>![](https://app.akto.io/public/openshift.svg) OpenShift
+</strong></td><td></td><td>
+OpenShift should be used as a traffic connector if you are deploying and managing containerized applications using OpenShift.</td></tr>
 
-![](https://app.akto.io/public/ebpf.svg) **eBPF**
 
-Akto-eBPF setup is recommended for mTLS systems when TLS termination happens at a proxy.
 
+<tr><td><strong>![](https://app.akto.io/public/ebpf.svg) eBPF
+</strong></td><td></td><td>
+Akto-eBPF setup is recommended for mTLS systems when TLS termination happens at a proxy.</td></tr>
 
 
-![](https://app.akto.io/public/ebpf.svg) **eBPF on mTLS**
 
-Akto-eBPF-mTLS setup is recommended for mTLS systems where TLS termination occurs at the application.
+<tr><td><strong>![](https://app.akto.io/public/ebpf.svg) eBPF on mTLS
+</strong></td><td></td><td>
+Akto-eBPF-mTLS setup is recommended for mTLS systems where TLS termination occurs at the application.</td></tr>
 
 
+</tbody></table>
 
 ### API Gateways
 
-***
-
-![](https://app.akto.io/public/apigee.svg) **Apigee**
-
-Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs.
-
-
-
-![](https://app.akto.io/public/azure.svg) **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.
-
-
-
-![](https://app.akto.io/public/cloudflare.svg) **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.
-
-
-
-![](https://app.akto.io/public/f5.svg) **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.
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
 
+<tr><td><strong>![](https://app.akto.io/public/apigee.svg) Apigee
+</strong></td><td></td><td>
+Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs.</td></tr>
 
-![](https://app.akto.io/public/kongmesh.svg)
 
-**Kong Mesh**
 
-Use this set-up if you are utilizing Kong's service mesh capabilities to manage and secure your microservices and APIs.
+<tr><td><strong>![](https://app.akto.io/public/azure.svg) Azure API Gateway
+</strong></td><td></td><td>
+Azure API Gateway setup is recommended if you are using Azure's API Management service to manage, secure, and analyze your APIs.</td></tr>
 
 
 
-![](https://app.akto.io/public/layer7.svg)
+<tr><td><strong>![](https://app.akto.io/public/cloudflare.svg) Cloudflare
+</strong></td><td></td><td>
+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.</td></tr>
 
-**Layer 7**
 
-Layer7 is recommended if you are using CA Technologies' Layer7 API Management for securing and managing your APIs.
 
+<tr><td><strong>![](https://app.akto.io/public/f5.svg) F5
+</strong></td><td></td><td>
+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.</td></tr>
 
 
-![](https://app.akto.io/public/threescale.svg)
 
-**3Scale**
+<tr><td><strong>![](https://app.akto.io/public/kongmesh.svg)
 
-This setup is recommended if your APIs are managed by 3scale.
+Kong Mesh
+</strong></td><td></td><td>
+Use this set-up if you are utilizing Kong's service mesh capabilities to manage and secure your microservices and APIs.</td></tr>
 
 
 
-![](https://app.akto.io/public/Nginx.svg)
+<tr><td><strong>![](https://app.akto.io/public/layer7.svg)
 
-**NGINX**
+Layer 7
+</strong></td><td></td><td>
+Layer7 is recommended if you are using CA Technologies' Layer7 API Management for securing and managing your APIs.</td></tr>
 
-This setup is recommended if your APIs are routed by NGINX.
 
 
+<tr><td><strong>![](https://app.akto.io/public/threescale.svg)
 
-![](https://app.akto.io/public/haproxy.svg)
+3Scale
+</strong></td><td></td><td>
+This setup is recommended if your APIs are managed by 3scale.</td></tr>
 
-**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.
 
+<tr><td><strong>![](https://app.akto.io/public/Nginx.svg)
 
+NGINX
+</strong></td><td></td><td>
+This setup is recommended if your APIs are routed by NGINX.</td></tr>
 
-![](https://app.akto.io/public/envoy.svg)
 
-**Envoy**
 
-Akto-Envoy setup is recommended if your APIs are routed by Envoy.
+<tr><td><strong>![](https://app.akto.io/public/haproxy.svg)
 
+HA Proxy
+</strong></td><td></td><td>
+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.</td></tr>
 
 
-![](https://app.akto.io/public/istio.svg)
 
-**Istio**
+<tr><td><strong>![](https://app.akto.io/public/envoy.svg)
 
-Akto-Istio setup is recommended if your APIs are routed by Istio.
+Envoy
+</strong></td><td></td><td>
+Akto-Envoy setup is recommended if your APIs are routed by Envoy.</td></tr>
 
 
 
-![](https://app.akto.io/public/kong.svg)
+<tr><td><strong>![](https://app.akto.io/public/istio.svg)
 
-**Kong**
+Istio
+</strong></td><td></td><td>
+Akto-Istio setup is recommended if your APIs are routed by Istio.</td></tr>
 
-Kong Gateway is an open source API gateway, built for multi-cloud and hybrid, and optimized for microservices and distributed architectures.
 
 
+<tr><td><strong>![](https://app.akto.io/public/kong.svg)
 
-![](https://app.akto.io/public/ibmapiconnect.svg)
+Kong
+</strong></td><td></td><td>
+Kong Gateway is an open source API gateway, built for multi-cloud and hybrid, and optimized for microservices and distributed architectures.</td></tr>
 
-**IBM API Connect**
 
-This setup is recommended if your APIs are managed by IBM API Connect
 
+<tr><td><strong>![](https://app.akto.io/public/ibmapiconnect.svg)
 
+IBM API Connect
+</strong></td><td></td><td>
+This setup is recommended if your APIs are managed by IBM API Connect.</td></tr>
 
-![](https://app.akto.io/public/citrix.svg)
 
-**Citrix**
 
-Citrix setup is recommended if you are using ADC (NetScaler) to manage, secure, and optimize your API traffic.
+<tr><td><strong>![](https://app.akto.io/public/citrix.svg)
 
+Citrix
+</strong></td><td></td><td>
+Citrix setup is recommended if you are using ADC (NetScaler) to manage, secure, and optimize your API traffic.</td></tr>
 
 
-![](https://app.akto.io/public/azureappservice.svg)
 
-**Azure App Services**
+<tr><td><strong>![](https://app.akto.io/public/azureappservice.svg)
 
-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.
+Azure App Services
+</strong></td><td></td><td>
+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.</td></tr>
 
 
 
-![](https://app.akto.io/public/mulesoft.svg)
+<tr><td><strong>![](https://app.akto.io/public/mulesoft.svg)
 
-**MuleSoft**
-
-Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs.
+MuleSoft
+</strong></td><td></td><td>
+Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs.</td></tr>
 
 
+</tbody></table>
 
 ### Mirroring
 
-***
-
-![](https://app.akto.io/public/aws.svg)
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
-**AWS Mirroring**
 
-You can deploy Akto in AWS and collect traffic through traffic mirroring.
+<tr><td><strong>![](https://app.akto.io/public/aws.svg)
 
+AWS Mirroring
+</strong></td><td></td><td>
+You can deploy Akto in AWS and collect traffic through traffic mirroring.</td></tr>
 
 
-![](https://app.akto.io/public/gcp.svg)
 
-**GCP Mirroring**
+<tr><td><strong>![](https://app.akto.io/public/gcp.svg)
 
-This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time.
+GCP Mirroring
+</strong></td><td></td><td>
+This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time.</td></tr>
 
 
+</tbody></table>
 
 ### AWS Services
 
-***
-
-![](https://app.akto.io/public/aws\_api\_gateway.svg)
-
-**AWS API Gateway**
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
-Akto-AWS-API-Gateway setup is recommended if you are using AWS API Gateway.
 
+<tr><td><strong>![](https://app.akto.io/public/aws\_api\_gateway.svg)
 
+AWS API Gateway
+</strong></td><td></td><td>
+Akto-AWS-API-Gateway setup is recommended if you are using AWS API Gateway.</td></tr>
 
-![](https://app.akto.io/public/eks.svg)
 
-**AWS EKS**
 
-You can deploy Akto in AWS and collect traffic through a daemonset on your AWS EKS configuration.
+<tr><td><strong>![](https://app.akto.io/public/eks.svg)
 
+AWS EKS
+</strong></td><td></td><td>
+You can deploy Akto in AWS and collect traffic through a daemonset on your AWS EKS configuration.</td></tr>
 
 
-![](https://app.akto.io/public/fargate.svg)
 
-**AWS Fargate**
+<tr><td><strong>![](https://app.akto.io/public/fargate.svg)
 
-AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances.
+AWS Fargate
+</strong></td><td></td><td>
+AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances.</td></tr>
 
 
 
-![](https://app.akto.io/public/beanstalk.svg)
+<tr><td><strong>![](https://app.akto.io/public/beanstalk.svg)
 
-**AWS Beanstalk**
+AWS Beanstalk
+</strong></td><td></td><td>
+You can deploy Akto in AWS and collect traffic through mirroring on your AWS Beanstalk setup.</td></tr>
 
-You can deploy Akto in AWS and collect traffic through mirroring on your AWS Beanstalk setup.
 
 
+<tr><td><strong>![](https://app.akto.io/public/ecs.svg)
 
-![](https://app.akto.io/public/ecs.svg)
-
-**AWS ECS**
-
-You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster.
+AWS ECS
+</strong></td><td></td><td>
+You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster.</td></tr>
 
 
+</tbody></table>
 
 ### Manual
 
-***
-
-![](https://app.akto.io/public/burp.svg)
-
-**Burp Suite**
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
-You can deploy Akto on your machine and download Akto's Burp extension to collect API traffic.
 
+<tr><td><strong>![](https://app.akto.io/public/burp.svg)
 
+Burp Suite
+</strong></td><td></td><td>
+You can deploy Akto on your machine and download Akto's Burp extension to collect API traffic.</td></tr>
 
-![](https://app.akto.io/public/postman.svg)
 
-**Postman**
 
-This setup is recommended if you have updated API collections maintained in Postman.
+<tr><td><strong>![](https://app.akto.io/public/postman.svg)
 
+Postman
+</strong></td><td></td><td>
+This setup is recommended if you have updated API collections maintained in Postman.</td></tr>
 
 
-![](https://app.akto.io/public/HAR.svg)
 
-**Har File Upload**
+<tr><td><strong>![](https://app.akto.io/public/HAR.svg)
 
-For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto.
+Har File Upload
+</strong></td><td></td><td>
+For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto.</td></tr>
 
 
 
-![](https://app.akto.io/public/openApi.svg)
+<tr><td><strong>![](https://app.akto.io/public/openApi.svg)
 
-**OpenAPI**
-
-Upload Open API/Swagger specification file to Akto to create an API inventory.
+OpenAPI
+</strong></td><td></td><td>
+Upload Open API/Swagger specification file to Akto to create an API inventory.</td></tr>
 
 
+</tbody></table>
 
 ### Akto SDK
 
-***
-
-![](https://app.akto.io/public/go.svg)
-
-**Go**
-
-Use where Go-based services are deployed.
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
 
+<tr><td><strong>![](https://app.akto.io/public/go.svg)
 
-![](https://app.akto.io/public/java.svg)
+Go
+</strong></td><td></td><td>
+Use where Go-based services are deployed.</td></tr>
 
-**Java**
 
-You can use Akto's Java agent to capture API traffic directly from your Java applications.
 
+<tr><td><strong>![](https://app.akto.io/public/java.svg)
 
+Java
+</strong></td><td></td><td>
+You can use Akto's Java agent to capture API traffic directly from your Java applications.</td></tr>
 
-![](https://app.akto.io/public/nodejs.svg)
 
-**NodeJS**
 
-This setup is ideal for environments where NodeJS-based services are deployed, ensuring seamless integration and real-time traffic monitoring.
+<tr><td><strong>![](https://app.akto.io/public/nodejs.svg)
 
+NodeJS
+</strong></td><td></td><td>
+This setup is ideal for environments where NodeJS-based services are deployed, ensuring seamless integration and real-time traffic monitoring.</td></tr>
 
 
-![](https://app.akto.io/public/python.svg)
 
-**Python**
+<tr><td><strong>![](https://app.akto.io/public/python.svg)
 
-Use where Python-based services are deployed.
+Python
+</strong></td><td></td><td>
+Use where Python-based services are deployed.</td></tr>
 
 
+</tbody></table>
 
 ### Virtual Machines
 
-***
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
-![](https://app.akto.io/public/docker.svg)
 
-**Docker**
+<tr><td><strong>![](https://app.akto.io/public/docker.svg)
 
-This setup is recommended only if other setups for AWS or GCP don't work.
+Docker
+</strong></td><td></td><td>
+This setup is recommended only if other setups for AWS or GCP don't work.</td></tr>
 
 
 
-![](https://app.akto.io/public/TCP.svg)
+<tr><td><strong>![](https://app.akto.io/public/TCP.svg)
 
-**TCP Agent**
-
-This setup is recommended only if other setups for AWS or GCP do not work.
+TCP Agent
+</strong></td><td></td><td>
+This setup is recommended only if other setups for AWS or GCP do not work.</td></tr>
 
 
+</tbody></table>
 
 ### Source Code
 
-***
-
-![](https://app.akto.io/public/favicon.svg)
-
-**API inventory from source code**
-
-Create API inventory from your source code using our code analysis tool.
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody>
 
 
+<tr><td><strong>![](https://app.akto.io/public/favicon.svg)
 
-![](https://app.akto.io/public/github.svg)
+API inventory from source code
+</strong></td><td></td><td>
+Create API inventory from your source code using our code analysis tool.</td></tr>
 
-**GitHub**
 
-We recommend setting up GitHub if you want to connect and retrieve APIs directly from your source code hosted on GitHub.
 
+<tr><td><strong>![](https://app.akto.io/public/github.svg)
 
+GitHub
+</strong></td><td></td><td>
+We recommend setting up GitHub if you want to connect and retrieve APIs directly from your source code hosted on GitHub.</td></tr>
 
-![](https://app.akto.io/public/gitlab.svg)
 
-**GitLab**
 
-We recommend setting up GitLab if you want to connect and retrieve APIs directly from your source code hosted on GitLab.
+<tr><td><strong>![](https://app.akto.io/public/gitlab.svg)
 
+GitLab
+</strong></td><td></td><td>
+We recommend setting up GitLab if you want to connect and retrieve APIs directly from your source code hosted on GitLab.</td></tr>
 
 
-![](https://app.akto.io/public/bitbucket.svg)
 
-**Bitbucket**
+<tr><td><strong>![](https://app.akto.io/public/bitbucket.svg)
 
-We recommend setting up Bitbucket if you want to connect and retrieve APIs directly from your source code hosted on Bitbucket.
+Bitbucket
+</strong></td><td></td><td>
+We recommend setting up Bitbucket if you want to connect and retrieve APIs directly from your source code hosted on Bitbucket.</td></tr>
 
+</tbody></table>


![](https://app.akto.io/public/kubernetes.svg) Kubernetes Daemonset +		+You can deploy Akto in Kubernetes and collect traffic through a daemonset on your Kubernetes configuration.
![](https://app.akto.io/public/openshift.svg) OpenShift +		+OpenShift should be used as a traffic connector if you are deploying and managing containerized applications using OpenShift.
![](https://app.akto.io/public/ebpf.svg) eBPF +		+Akto-eBPF setup is recommended for mTLS systems when TLS termination happens at a proxy.
![](https://app.akto.io/public/ebpf.svg) eBPF on mTLS +		+Akto-eBPF-mTLS setup is recommended for mTLS systems where TLS termination occurs at the application.

![](https://app.akto.io/public/apigee.svg) Apigee +		+Apigee setup is recommended if you are using Google's Apigee API Management platform to design, secure, and scale your APIs.
![](https://app.akto.io/public/azure.svg) 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.
![](https://app.akto.io/public/cloudflare.svg) 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.
![](https://app.akto.io/public/f5.svg) 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.
![](https://app.akto.io/public/kongmesh.svg) -This setup is recommended if your APIs are managed by 3scale. +Kong Mesh +		+Use this set-up if you are utilizing Kong's service mesh capabilities to manage and secure your microservices and APIs.
![](https://app.akto.io/public/layer7.svg) -NGINX +Layer 7 +		+Layer7 is recommended if you are using CA Technologies' Layer7 API Management for securing and managing your APIs.
![](https://app.akto.io/public/threescale.svg) -![](https://app.akto.io/public/haproxy.svg) +3Scale +		+This setup is recommended if your APIs are managed by 3scale.
![](https://app.akto.io/public/Nginx.svg) +NGINX +		+This setup is recommended if your APIs are routed by NGINX.
![](https://app.akto.io/public/haproxy.svg) +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.
![](https://app.akto.io/public/envoy.svg) -Akto-Istio setup is recommended if your APIs are routed by Istio. +Envoy +		+Akto-Envoy setup is recommended if your APIs are routed by Envoy.
![](https://app.akto.io/public/istio.svg) -Kong +Istio +		+Akto-Istio setup is recommended if your APIs are routed by Istio.
![](https://app.akto.io/public/kong.svg) -![](https://app.akto.io/public/ibmapiconnect.svg) +Kong +		+Kong Gateway is an open source API gateway, built for multi-cloud and hybrid, and optimized for microservices and distributed architectures.
![](https://app.akto.io/public/ibmapiconnect.svg) +IBM API Connect +		+This setup is recommended if your APIs are managed by IBM API Connect.
![](https://app.akto.io/public/citrix.svg) +Citrix +		+Citrix setup is recommended if you are using ADC (NetScaler) to manage, secure, and optimize your API traffic.
![](https://app.akto.io/public/azureappservice.svg) -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. +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.
![](https://app.akto.io/public/mulesoft.svg) -MuleSoft - -Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs. +MuleSoft +		+Mulesoft setup is recommended if you are using API management and ESB capabilities to manage, secure, and analyze your APIs.

![](https://app.akto.io/public/aws.svg) +AWS Mirroring +		+You can deploy Akto in AWS and collect traffic through traffic mirroring.
![](https://app.akto.io/public/gcp.svg) -This setup only takes ten minutes. Once you connect GCP, Akto will process GCP traffic to create an API Inventory in real time. +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.

![](https://app.akto.io/public/aws\_api\_gateway.svg) +AWS API Gateway +		+Akto-AWS-API-Gateway setup is recommended if you are using AWS API Gateway.
![](https://app.akto.io/public/eks.svg) +AWS EKS +		+You can deploy Akto in AWS and collect traffic through a daemonset on your AWS EKS configuration.
![](https://app.akto.io/public/fargate.svg) -AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances. +AWS Fargate +		+AWS Fargate allows you to use Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances.
![](https://app.akto.io/public/beanstalk.svg) -AWS Beanstalk +AWS Beanstalk +		+You can deploy Akto in AWS and collect traffic through mirroring on your AWS Beanstalk setup.
![](https://app.akto.io/public/ecs.svg) -![](https://app.akto.io/public/ecs.svg) - -AWS ECS - -You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster. +AWS ECS +		+You can deploy Akto in AWS and collect traffic through containers on your AWS ECS cluster.

![](https://app.akto.io/public/burp.svg) +Burp Suite +		+You can deploy Akto on your machine and download Akto's Burp extension to collect API traffic.
![](https://app.akto.io/public/postman.svg) +Postman +		+This setup is recommended if you have updated API collections maintained in Postman.
![](https://app.akto.io/public/HAR.svg) -For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto. +Har File Upload +		+For a very quick view of your inventory, you can upload a HAR file that contains traffic to Akto.
![](https://app.akto.io/public/openApi.svg) -OpenAPI - -Upload Open API/Swagger specification file to Akto to create an API inventory. +OpenAPI +		+Upload Open API/Swagger specification file to Akto to create an API inventory.

![](https://app.akto.io/public/go.svg) -![](https://app.akto.io/public/java.svg) +Go +		+Use where Go-based services are deployed.
![](https://app.akto.io/public/java.svg) +Java +		+You can use Akto's Java agent to capture API traffic directly from your Java applications.
![](https://app.akto.io/public/nodejs.svg) +NodeJS +		+This setup is ideal for environments where NodeJS-based services are deployed, ensuring seamless integration and real-time traffic monitoring.
![](https://app.akto.io/public/python.svg) -Use where Python-based services are deployed. +Python +		+Use where Python-based services are deployed.

![](https://app.akto.io/public/docker.svg) -This setup is recommended only if other setups for AWS or GCP don't work. +Docker +		+This setup is recommended only if other setups for AWS or GCP don't work.
![](https://app.akto.io/public/TCP.svg) -TCP Agent - -This setup is recommended only if other setups for AWS or GCP do not work. +TCP Agent +		+This setup is recommended only if other setups for AWS or GCP do not work.

![](https://app.akto.io/public/favicon.svg) -![](https://app.akto.io/public/github.svg) +API inventory from source code +		+Create API inventory from your source code using our code analysis tool.
![](https://app.akto.io/public/github.svg) +GitHub +		+We recommend setting up GitHub if you want to connect and retrieve APIs directly from your source code hosted on GitHub.
![](https://app.akto.io/public/gitlab.svg) +GitLab +		+We recommend setting up GitLab if you want to connect and retrieve APIs directly from your source code hosted on GitLab.
![](https://app.akto.io/public/bitbucket.svg) -We recommend setting up Bitbucket if you want to connect and retrieve APIs directly from your source code hosted on Bitbucket. +Bitbucket +		+We recommend setting up Bitbucket if you want to connect and retrieve APIs directly from your source code hosted on Bitbucket.