/
Licensing and connector requirements

Licensing and connector requirements

Owned by Bob Swift (Deactivated)

This guide provides an overview of the licensing, dependencies, and distribution details for the Appfire Command Line Interface (ACLI) product family. It also includes answers to frequently asked questions about using and evaluating ACLI.

Licensing overview

ACLI products are licensed commercially under the Appfire End User License Agreement (EULA).

  • To use ACLI, you must purchase or subscribe to at least one ACLI product listed in the Feature tour.

  • Choose the ACLI products that best match your use case and target platform.

Distribution details

  • ACLI installers and distributions include binary files covered under various open-source licenses, such as BSD, LGPL, and Apache.

  • For details, see the license directory included in the distribution.

Connector app requirements

Most ACLI clients require an associated server app, called the ACLI Connector, to be installed on the Atlassian instance. This app:

  • Enables license enforcement

  • Provides extended remote interfaces beyond what the base Atlassian product offers

Some ACLI clients can run without a connector. See the Feature tour for exceptions.

Evaluate ACLI before purchase

To try ACLI:

  1. Request an evaluation license for one of the ACLI server apps.

  2. Install the app on your server.

  3. Download the ACLI client distribution or use one of the available installers.

Frequently asked questions

Question

Answer

Question

Answer

  1. Do clients require the ACLI Connector app?

Yes, in most cases. Some clients can not require it—see the Feature tour for details.

  1. Can I purchase ACLI clients separately?

No. Clients are included at no additional charge when you purchase one or more ACLI Connector apps.

  1. How can I evaluate ACLI?

Install an ACLI Connector server app using an evaluation license, then download the ACLI client distribution or use an installer.

  1. Is the server app required to use ACLI?

Yes, with limited exceptions. See above.

  1. Can ACLI access a server without the Connector app?

This is not for ACLI clients. Other products in the Run CLI Actions family can support this, but advanced capabilities often require the Connector. In unsupported cases, the CLI will show an error message.

  1. Is ACLI available for Atlassian Cloud?

Yes. Depending on your use case, you can purchase or start a trial subscription for Jira Cloud or Confluence Cloud.

  1. Do I need a license for a developer or test server?

No. If your Atlassian app has a valid production license, it includes a developer license. Go to my.atlassian.com, expand the app entry, and find the developer license link. ACLI works with these servers even if the Connector isn’t licensed. Note: Crucible/FishEye support is limited due to detection issues for developer licenses.

  1. How many client users can I have?

Unlimited. Any number of users can install and run ACLI clients. The only requirement is that the server has a validly licensed ACLI Connector installed.

  1. Which server product should I choose?

  • Choose the ACLI Connector for basic command-line connectivity to the target Atlassian product.

  • Choose a Run CLI Actions app for advanced integration, such as Jira workflow functions or Confluence macros.

10. Where do I find CLI Connector apps on the Atlassian Marketplace?

Each product-specific CLI entry in the Marketplace is a UPM-installable CLI Connector. The downloadable CLI client package includes clients for all supported products. Examples: - Jira Command Line Interface (CLI) - Confluence Command Line Interface (CLI) - Bitbucket Command Line Interface (CLI)