# Frequently asked questions

## Can I use KAPE in client engagements? 

- KAPE is free for any local, state, federal or international government agency. KAPE is also free for educational, research, and internal company use.
- As of January 1, 2026 KAPE IS NO LONGER AVAILABLE for commercial use (i.e. when used on a third-party network and/or as part of a paid engagement).

## Is there a way to have KAPE download all the binaries that are needed for the Modules?

In short, no, and there will not ever be an officially supported way to do this, as it is a massive liability.

While certain Modules come with the binaries they need, in general, the user needs to pick which Modules they want to run, they need to take steps to discover and download the binaries, they need to extract and copy them to the proper location.

This way, there is ZERO surprises when KAPE does something.

You can always find the URL of the binary that is needed using `--mlist . --mdetail` and adjusting the directory as needed for each category.

## How can I execute all of the config files found in a subdirectory of the Targets or Modules directory?

One option is to create a compound Target or Modules that references all the files in the directory you want to include, but an easier way is to simply include the name of the directory in the appropriate option.

Assuming the directory `.\Targets\Windows` exists, you could execute all Targets under that directory like this:

`.\kape.exe --tsource c --tdest C:\temp\tout\ --tflush --target Windows`

You can also of course include other Target names as well, separating them with a comma:

`.\kape.exe --tsource c --tdest C:\temp\tout\ --tflush --target Windows,Chrome`

## I am in a corporate environment and want to push to S3, but there is a proxy in the way. Does KAPE support this?

It sure does! See [here](https://github.com/EricZimmerman/KapeFiles/issues/121#issuecomment-524682298) for details on how to do this.

## I am experiencing scaling issues with gkape. How do I fix this?

[This issue](https://github.com/EricZimmerman/KapeFiles/issues/614) addresses this. Long story short, don't have too low of a resolution (1080p or lower) with too high of scaling (150% or more) otherwise you will not be able to see components of gkape's GUI.