Skip to main content

License Management

FastTransfer requires a license file to operate. This guide explains how to manage your license file and the different ways to provide it.

License File Basics​

License Information

After the trial period, you will need a valid license. By default, FastTransfer will try to find a FastTransfer.lic file in the same directory as the executable. You can also provide another path, a URL, or even the license content using the --license parameter.

License File Location Options​

Place the FastTransfer.lic file in the same directory as the FastTransfer executable:

C:\Tools\FastTransfer\
├── FastTransfer.exe
└── FastTransfer.lic

This is the simplest method and requires no additional configuration. FastTransfer will automatically detect and use the license file.

Option 2: Custom Path​

Specify the license file path using the --license parameter:

./FastTransfer \
  --license "/path/to/FastTransfer.lic" \
  --sourceconnectiontype pgsql \
  --sourceserver "source.example.com" \
  ...

This option is useful when:

  • You want to store the license file in a centralized location
  • Multiple installations need to share the same license
  • You need to organize license files by environment (dev, staging, prod)

Option 3: License Content​

Pass the license content directly (useful for CI/CD):

./FastTransfer \
  --license "LICENSE_CONTENT_STRING_HERE" \
  --sourceconnectiontype pgsql \
  --sourceserver "source.example.com" \
  ...

This option is ideal for:

  • CI/CD pipelines where you store the license in environment variables
  • Containerized deployments
  • Automated workflows that need to inject the license dynamically

Example with environment variable:

$env:FT_LICENSE = "YOUR_LICENSE_CONTENT"
.\FastTransfer.exe --license $env:FT_LICENSE ...

Option 4: URL​

Load the license from a URL:

./FastTransfer \
  --license "https://example.com/licenses/FastTransfer.lic" \
  --sourceconnectiontype pgsql \
  --sourceserver "source.example.com" \
  ...

This option allows you to:

  • Host licenses on a secure internal server
  • Implement centralized license management
  • Update licenses without redistributing files
Security Best Practice

When using a URL, ensure the connection is secure (HTTPS) and the server requires authentication to prevent unauthorized access to your license files.

License Verification​

To verify your license is working correctly, run:

.\FastTransfer.exe --version

If the license is valid, you'll see version information along with license details. If there's an issue, FastTransfer will display an error message indicating the problem.

Common License Issues​

License File Not Found​

Problem: FastTransfer reports it cannot find the license file.

Solutions:

  1. Verify FastTransfer.lic is in the same directory as the executable
  2. Check file permissions (must be readable)
  3. Use the --license parameter to specify the path explicitly

Invalid License Format​

Problem: License file is corrupted or has an invalid format.

Solutions:

  1. Re-download the license file from your account portal
  2. Ensure the file wasn't modified during transfer
  3. Check that the entire license content is present (no truncation)

License Expired​

Problem: Your license has reached its expiration date.

Solutions:

  1. Contact support to renew your license
  2. Purchase a new license from arpe.io
  3. Request a trial extension if you're still evaluating

License Limit Reached​

Problem: You've exceeded the concurrent usage limit of your license.

Solutions:

  1. Wait for other instances to complete
  2. Upgrade your license to support more concurrent transfers
  3. Contact sales to discuss enterprise licensing options

Best Practices​

For Development Teams​

  • Store licenses securely: Use secret management tools (Azure Key Vault, AWS Secrets Manager, HashiCorp Vault)
  • Separate licenses by environment: Use different licenses for dev, staging, and production
  • Automate license deployment: Include license provisioning in your deployment scripts

For Production Environments​

  • Monitor license expiration: Set up alerts for upcoming expiration dates
  • Keep backup licenses: Store a copy in a secure, accessible location
  • Document license locations: Maintain clear documentation of where licenses are stored

For CI/CD Pipelines​

  • Use environment variables: Store license content in secure pipeline variables
  • Rotate licenses regularly: Update licenses as part of security maintenance
  • Test license validity: Include license verification in your test suite

Getting Support​

If you encounter issues with your license that aren't covered here:

  1. Check your email: License-related communications are sent to your registered email
  2. Visit the support portal: support.arpe.io
  3. Contact sales: For license upgrades or renewals at sales@arpe.io
Copyright © 2026 Architecture & Performance. Built with Docusaurus.