AES 256-bit Encryption protecting Python source code

AES is a symmetric algorithm which uses the same key for both encryption and decryption (the security of an AES system increases exponentially with key length). There is no impact on the performance of your running application as the decryption process takes place during the import of your module so encrypted code won't run any slower once loaded from a .pye file compared to loading from a .py or .pyc file.

Features

Symmetric AES 256-bit encryption
Set your own password & salt for encryption
No 'Magic Number' problems changing Python version
Set an expiration time on encrypted code
Encrypted code will load on ANY supported target system

Supported Systems

We support the following Operating System & Architecture combinations and hook directly into the import process so there are no cross platform compatibility issues. Each system, identified by Platform ID will need a license to create encrypted code. The licence is fixed to the system that it is activated on for the duration of the current billing period.
Encrypted code will run on the ANY target platform we support. Python code encrypted in Python 3.9 will run just fine in Python 3.6. Obviously your code needs to be written with the target system in mind as we can't make sys.getwindowsversion() work on Linux and we can't backport newer Python functions.
Architecture Operating System Platform ID Python Versions
X86_64 Windows windows64 3.6 - 3.9
X86_64 Linux linux64 3.6 - 3.9
X86_64 macOS darwin64 3.6 - 3.9
ARM64 macOS arm64 3.9
ARMv6 (32-bit) Linux armv6l 3.6 - 3.9
ARMv8 Linux aarch64 3.6 - 3.9

Download

TLDR : pip install sourcedefender

The installation of our package is straight forward. Anyone who is used to using pip will not find this difficult. Simply run the install command above and you'll be good to go. Installation is just like installing any other Python package.

For more information on the pip package, you can take a look on PyPi .

Pricing

Distribution of encrypted code will always be free!

Free

£0.00

  • File encryption : Unlimited
  • Code expire : 24hrs
  • Email response : 48hrs
  • CI/CD Compatible : Yes

Standard

£5.00 /month

  • File encryption : Unlimited
  • Code expire : Optional
  • Email response : 24hrs
  • CI/CD Compatible : No
  • Active billing : Yes
  • License type : per System

Professional

£50.00 / month

  • File encryption : Unlimited
  • Code expire : Optional
  • Email response : 12hrs
  • CI/CD Compatible : Yes
  • Active billing : No
  • License type : Unlimited

Enterprise

£500.00 / year

  • File encryption : Unlimited
  • Code expire : Optional
  • Email response : 6hrs
  • CI/CD Compatible : Yes
  • Active billing : No
  • License type : Unlimited

* Prices suject to VAT where applicable.

Frequently Asked Questions

You only need to license systems that create encrpyted code. You do not need to license each device that will run encrypted code. A example of system that would need a license would a pyhsical or virtual machine that is part of your CI/CD pipeline. A customers server would not need a license to run any code you encrypt for them.

CI/CD compatibility

The Standard plan is incompatible with CI/CD pipelines as each use of your activation token would increase your usage quota as Active Billing would see each use as being a new activation and charge you accordingly. If you wish to integrate into your CI/CD pipeline then you will need either the Professional or Enterprise Plan.

Multiple Systems

You can use your activation token on as many systems as you need. For example, if you have 10 Developers who that need activating you could use your token 10 times. Active Billing would then charge you for 10 activations on the Standard Plan. However, if you know you want to have 14 or more systems regularly encrypting code, then you may be better with either the Professional or Enterprise Plan.

Active Billing

To ensure your monthly cost is reduced to the bare minimum we will only bill you for newly activated systems or systems that you previously activated and are generate encrypted code.

When you activate sourcedefender on a system using your unique token we keep track of that. Any system that is active systems in use during your billing period so you do not need to let us know if you add/remove a system as this is taken care of automatically. systems where code has been encrypted during the current billing period.

Billing Period

Our default billing period starts when you activate your first system and lasts for 1 month. Your system will automatically renew the license at the end of its billing period.

Activation

An activation takes place when a user installs the sourcedefender package (via 'pip install sourcedefender') on a system and runs the "sourcedefender activate --token" command with your unique token.

Activation Token

This activation token is unique to your account. If you wish to get a new token, click on the Refresh Token button. Any system that was previously activated will continue to work and renew as required.

Renewals

Your license will automatically get renewed the next time you encrypt files after your billing period is over (normally 1 month). This renewal happens automatically when you use the 'sourcedefender' command. If you do not use sourcedefender in that month, then you won't be charged for usage.

Cancellation

Your license will automatically cancel at the end of its billing period (normally 1 month). Active Billing will automatically stop charging you for your license when you stop using it. If you are on the Professional or Enterprise Plans then you would need to log into the Dashboard and cancel your subscription. Any licenses you have activated will expire at the end of the billing period.

Any encrypted code you have deployed will continue to run even after you end your subscription.