Licensing - Rasa Documentation

Rasa offers Enterprise licenses for teams building assistants at scale, with advanced features like enterprise-grade security, scalability, and dedicated support. But if you’re just getting started, you can get a free Developer Edition License to try it out.

Developer Edition

Start building CALM assistants with the free Rasa Developer Edition.

How Licensing Works

Rasa will look for your license in the env var RASA_LICENSE, which must contain the content of the license key file provided by rasa. You can set the RASA_LICENSE env var temporarily in your terminal, but it is recommended to set it persistently so that you don’t have to set it every time you run Rasa.

Bash
Windows Powershell

## Temporary
export RASA_LICENSE=YOUR_LICENSE_STRING_HERE

## Persistent
echo "export RASA_LICENSE=YOUR_LICENSE_STRING_HERE" >> ~/.bashrc
## If you're using a different flavor of bash e.g. Zsh, replace .bashrc with your shell's initialization script e.g. ~/.zshrc

## Temporary
$env: RASA_LICENSE=YOUR_LICENSE_STRING_HERE

## Persistent for the current user
[System.Environment]::SetEnvironmentVariable('RASA_LICENSE','YOUR_LICENSE_STRING_HERE','USER')

Then you can use the rasa CLI as usual, for example:

rasa init

Requesting a Developer License from the CLI

If you run a licensed command without a valid RASA_LICENSE value, the CLI now prompts you for an email address instead of exiting immediately. Licensed commands include rasa train, rasa run, rasa inspect, rasa license, and rasa --version. The CLI sends the email to Rasa to request a Developer Edition license.

Enter your email address to request a Rasa developer license.
By entering your email address, you accept Rasa's developer terms: https://rasa.com/developer-terms
> you@example.com
Your license request was submitted. Check your email for the license key,
then set it in `RASA_LICENSE` and rerun your command.

Submitting your email address:

Sends the address to Rasa’s license request form and opts you in to the Rasa Developer Terms and the marketing communications attached to the form.
Does not run the command you invoked. After you receive the key, set RASA_LICENSE and rerun the command.

The CLI only shows the prompt in an interactive terminal. rasa --help, rasa -h, and subcommand help (for example rasa train --help) do not require a license and skip the check entirely.

Skipping the prompt in CI

In a non-interactive shell (for example a CI job or a container without a TTY), the CLI does not prompt and instead exits with the original license error. You can also opt out explicitly with the --no-prompt flag on commands that support it:

rasa train --no-prompt

Use --no-prompt in automated pipelines to fail fast when RASA_LICENSE is missing rather than block on user input.

Developer Edition

​How Licensing Works

​Requesting a Developer License from the CLI

​Skipping the prompt in CI

How Licensing Works

Requesting a Developer License from the CLI

Skipping the prompt in CI