|Architecture||Operating System||Activation||Python Versions|
|X86||Windows||windows32||3.6 - 3.10|
|AMD64||Windows||windows64||3.6 - 3.10|
|X86_64||Linux||linux64||3.6 - 3.10|
|X86_64||macOS||darwin64||3.6 - 3.10|
|ARM64||macOS||arm64||3.9 - 3.10|
|ARMv6 (32-bit)||Linux||armv6l||3.6 - 3.10|
|ARMv8||Linux||aarch64||3.6 - 3.10|
TLDR : pip install sourcedefender
We are proud to be in the Top 3% of packages on PyPi when ordered by downloads. We have worked hard to ensure the installation of our package is as straight forward as possible. 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 v7.1.62 release, you can take a look on PyPi .
You only need to license systems that create encrypted code. You do not need to license each device that will run encrypted code.
See what all the fuss is about for free!
Suited to Small Teams of Developers
Suited to Small Teams of Developers
Great for CI/CD Pipelines
You only need to license systems that create encrypted code. You do not need to license each device that will run encrypted code. A example of system that would need a license would be a physical 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.
We appreciate that you may not need to encrypt code on a regular basis, so we have introduced Active Billing . At the end of your billing period we automatically pause your subscription and only activate it the next time you need to encrypt code. This means that on a Standard Plan, if you only encrypt code every other month, we would not charge you for the months you do not encrypt code.
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. On the Standard Plan you will be charged for 10 subscriptions. However, if you know you want to have 10 or more systems regularly encrypting code, then you may be better with either the Professional or Enterprise Plan.
Activation is compatible with Docker Containers providing the Container ID never changes. We scrape the container ID and use that to lock the activation to the instance. If the container ID changes a new subscription would automatically be started and you would be billed accordingly. If you wish to integrate into your Docker environment then we highly recommend either the Professional or Enterprise Plan.
The Professional or Enterprise plans are both compatible for use in CI/CD pipelines. The other plans are incompatible because each use of your activation token would start a new subscription for that instance that you would get billed for.
If you wish to integrate into your CI/CD pipeline then you will need either the Professional or Enterprise Plan.
Our default billing period starts when you activate your first system and lasts for the duration of your Plan. Your systems subscription will automatically cancel at the end of this billing period and reactivated on the next use.
An activation takes place when a user installs the sourcedefender package (via 'pip install sourcedefender') on a system and then runs the "sourcedefender activate --token" command with your unique 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.
We will automatically cancel licences at the end of the billing period, they will only (automatically) renew on next use. Any encrypted code you have deployed will continue to run even after you end your subscription.
We are unable to offer refunds on our subscriptions. Our software is activated on your system automatically at the time of purchase and is set to expire and the end of your billing period. Once the license is activated on your system we have no way of disabling it early.