Licensing

SpecSync provides different licensing options including a free usage for smaller projects. For details and pricing, please check the available plans.

Please send your questions or license inquiries to [email protected].

License files and license keys

SpecSync licenses can be provided in two formats: as a license file or as a license key.

License files

License files are digitally signed text files that contain license information. SpecSync tries to find the license file in the project folder (where the specsync.json configuration file is located). Since the license files are project or enterprise specific, these can be safely checked in to the source control.

The location of the license file (absolute or relative to the project folder) can be specified with the --license option of the synchronization tool or in the toolSettings/licensePath setting of the configuration file if necessary. You can also consider to configure the license path in the user-specific configuration file.

The SpecSync license files are digitally signed text files. You can open them with a text editor (e.g. Notepad) to check the expiry date, the edition and other details.

License keys

As an alternative to license files, SpecSync supports license keys. A license key is a text string that can be specified directly in the configuration file or provided via command line option or environment variable. This approach is particularly useful for secure environments such as CI/CD pipelines where you don't want to store license files.

This feature is available with SpecSync v5 or above.

The license key can be specified in the following ways:

• In the toolSettings/license configuration setting of the configuration file or the user-specific configuration file

• With the --license command line option of the synchronization tool

• Via the SPECSYNC_LICENSE_KEY environment variable (SpecSync automatically loads the license key from this variable)

• In the toolSettings/license configuration setting by loading from an custom environment variable using the {env:ENV_VAR} syntax

You can convert an existing license file to a license key using the specsync upgrade command, or you can request your license key by contacting support. The license files issued after 12th December 2025 also contain the license key (open the file in a text editor).

Limitations of the Free Edition

• Maximum 30 scenarios can be synchronized

• Enterprise features cannot be used

Scenario Outlines count as one scenario.

Limitations of the Standard Edition

• Maximum 300 scenarios can be synchronized

• Enterprise features cannot be used

Scenario Outlines count as one scenario.

Enterprise features

• Two-way synchronization (using the pull command). See Two-way synchronization for details.

• Re-linking scenarios to new Test Cases (using the re-link command). See Re-link scenarios to new Test Cases

• All customization features

Enterprise support

The Service Level Agreement (SLA) for the support services for SpecSync for Azure DevOps Enterprise license holders can be downloaded from here.

EULA

The End User License Agreement (EULA) can be downloaded here.

SpecSync for Azure DevOps uses 3rd party software libraries, please find their licenses at http://speclink.me/specsync3rdpartylic.