About Us

When seeking to encrypt, release and distribute scripts written in an interpreted language, some of the most common questions I'm sure you've pondered upon were; can it be done, if so, how? Prior to the advent of enscrypt.io, the generally accepted answers to those questions are that you can't, or that it doesn't really work, or you shouldn't, or it costs lots of money. And no matter what you do, someone smart enough or someone with enough time on their hands can get to it, so don't bother.

These answers are somewhat true to a very small degree but they're also a huge copout.

Ignoring the practicality of securing code just because someone can get to it is similar to refusing to lock the doors to your car just because cars can be broken into. Yes, cars can be broken into regardless of the security measures put in place, but it is a fact that, locking a car reduces the chances of a break in and, fortunately, in this modern day and age, the majority of newer cars come equipped with alarm systems designed to set off deafening noises whenever a breakin is detected. A great deterrent.

When it comes to protecting source code, there are quite a few options out there. But our methodology is the only one that approaches the task of source code protection with dynamic intelligence which not only self-defends (in more ways than one), but also notifies. We understand whenever an attack is to take place, attackers will often perform a series of reconnaisanace steps, and in doing so, leave traces behind that alerts us to their activities, very well in advance, giving us time to react before it is too late. If your code is stolen today, you want to know today. Not weeks. Not months. And definitely Not years later!
enScrypt.io is both a command line and web based source code protection service utilized for the purposes of:

  1. Preventing and protecting source code against Unauthorized Modifications
    • This feature is default on all obfuscated scripts. It guarantees no one, not even the root/admin user, or you (the creator), can modify or alter a protected script.
    • You no longer have to rely on system permissions which can be altered by anyone with superuser privileges.
  2. Guarding against Unauthorized Duplication of protected scripts
    • When enabled, this setting ensures all duplicated copies of protected scripts abort immediately upon execution
      • Purpose:
        • When a script is being dissected by a hacker or curious user, it is often duplicated first and the duplicated copy is then altered and used as comparison to the original copy.
          • By causing a duplicated script to abort, you add a layer of frustration for potential hackers to contend with.
          • Additionally, and probably most importantly, if the 'satelite' setting was enabled during obfuscation, you can be notified the moment an hack attempt is detected on your source code.
  3. Providing a much simpler, foolproof way to grant execute permissions to only a select set of users
    • This setting, when turned on, ensures your script can only be executed by the username(s) you specified during obfuscation.
  4. Providing a foolproof method of ensuring protected scripts get executed only on a particular list of servers
    • With this feature, you can license your scripts out to different entities and ensure the usage of said scripts are confined to a defined list of servers
  5. Endowing developers with the unique power to set irreversible remotely verified expiration dates on all protected scripts
    • With this capability in your arsenal, you can rest assured your protected scripts will run only for the duration of time you specified
  6. Enabling a simplified method through which developers can monitor where their code is being used, and by whom
    • Yes, this feature affords you the luxury of monitoring hack attempts (if any) that are being carried out on your protected scripts
      • Purpose:
        • Suppose one of your protected scripts contain credentials. If the protected script were to fall into the wrong hands, this setting will let you know the moment they perform any hack experiments on it.
        • And once you're notified, you can be many steps ahead of the would-be hackers and immediately change the credentials or remotely disable the script.
  7. Restricting the importation of protected obfuscated modules from plain text scripts
    • Ensure protected scripts can only be imported by other protected scripts