Each time you apply transformations to your project counts as a request, independently of the number of files and protections. Every time this protected version is executed, it does not count as a new service request. The protected version of the code doesn't contact our service. So in summary, you only do Jscrambler service requests when you have a new version of the code to protect.
Your protected code will continue to work regardless of you staying subscribed or not. You need to keep subscribed only in case you need to protect newer versions of the code. The ones you have protected before will work forever.
You can use our Code Annotations to control our transformations through several code blocks
All of Jscrambler's Code transformations are developed to have the least impact possible. The performance hits are manageable and depend a lot on the application you are trying to protect. You can fine-tune your protection on most sensitive parts and apply it more where it is most needed through code annotations.
You may use an API client if you would like to integrate Jscrambler into your development process and submit requests to our Web service programmatically. Check them out here.
Potency represents the power of a transformation to increase your code complexity. Resilience represents the difficulty to revert the transformed code into its original form. Cost represents the impact of a given transformation in execution time and space that it will have in a transformed application.
If you want to migrate from one of Jscrambler's 3.x versions to our most recent version, we've prepared a guide which introduces the main differences between the versions and explains how you can start protecting your applications in the newer version. You can find the guide here.