Files

Below are the most frequent asked questions related to files.

What is the difference between a "Start App" and a "Regular File"?

There are two types of files you can upload: a Start App and a Regular File. A "Start App" is the main executable that our secure bootstrapper will run when a user launches your product. A "Regular File" is any other supplementary file that your application might need, which can only be downloaded by the Start App after it is running.

Are there specific requirements for the "Start App" file?

Yes. The file you designate as your Start App must be a 64-bit (x64) executable binary that can run on Windows operating systems.

Will my users be able to find and copy my main executable from their PC?

No. Our bootstrapper executes your Start App within a secure environment. A major benefit of this is that the executable will never physically appear as a file on the client's PC, protecting it from being easily copied or accessed.

How does my running application get its other required files?

Regular files must first be paired to the specific product in your panel. Then, from within your running Start App, you can use our provided SDK to download those paired files as needed. The files cannot be downloaded otherwise.

Can I use the same executable file for multiple products?

Yes. A single Start App can be assigned to multiple products. Our SDK provides your running application with information such as the Product ID it was launched with. This allows your single executable to know which product is active and download the correct corresponding files.

Can a file be both a "Start App" and a "Regular File"?

No. The two types are mutually exclusive. If you mark a file as a Start App, it can only be used to launch a product; it cannot be paired or downloaded as a Regular File.