<div class="section-label"><span class="num">06</span> License Key</div>
<div class="section-title">Activate after you <em>install</em>.</div>
Most readers use a **workstation** license on their own laptop or desktop. Follow the three steps below.
**Before you begin:** finish an [[Install/Get Started|Install]] path so <span class="mono">rbp-license-info</span> is available on your machine.
If CSA assigned a **server**, **shared environment**, or **enterprise site** license instead, skip to [Servers, shared environments, and enterprise sites](#servers-shared-environments-and-enterprise-sites).
<p> </p>
> [!warning]
> The request code is only a request. It does not unlock the product by itself. CSA reviews it and sends back your signed license key.
## (1) Request a code
On your approved computer, run:
```bash
rbp-license-info
```
Copy the full code that starts with <span class="mono">RBP-LRC-1:</span> and send it to CSA the way your account team requested.
> [!tip]
> If the command is “not found,” open the same environment you installed into (for example your Python virtual environment), or jump to [Find the license tool](#find-the-license-tool).
## (2) Activate your key
CSA returns a key that starts with <span class="mono">RBP-LIC-1:</span>. Activate it once:
```bash
rbp-license-info --setlicense RBP-LIC-1:…
```
> [!warning]
> Your license key is a secret.
>
> - Do not put it in public repositories or shared chat logs
> - Store it in your organization’s secrets process when possible
> - Tell CSA if it may have been exposed, or if you move to a different machine than the one that was licensed
## (3) Confirm your license
```bash
rbp-license-info --viewlicense
```
You should see that a valid license is present. Then you are ready to run predictions.
## Troubleshooting
| What you see | What to try |
| --- | --- |
| Command not found | [Find the license tool](#find-the-license-tool) |
| License not found | Confirm step (2) completed |
| Wrong machine / user | Request and activate again on the computer CSA approved |
<div class="btn-row center">
<a class="btn-ghost" href="/Install/Get%20Started">← Get Started</a>
<a class="btn-primary" href="/Install/Python">Python install</a>
</div>
***
# Servers, Virtual Machines, and Enterprise Deployments
Use this section only if CSA told you that you have a **service-node** or **site** license. Individual workstation users can ignore it.
## Service node (one server or VM)
Request the code **on that server**:
```bash
rbp-license-info --sku service-node
```
Send the <span class="mono">RBP-LRC-1:</span> code to CSA. When you receive the key, set it for the processes that run predictions:
```bash
export RBP_LICENSE=RBP-LIC-1:…
```
If the server is rebuilt and its machine identity changes, request a new code and ask CSA to reissue the key.
## Enterprise site (many servers or containers)
CSA gives you a **site ID**. Set it before requesting the code:
```bash
export RBP_SITE_ID=your-csa-assigned-site-id
rbp-license-info --sku site
```
Send the <span class="mono">RBP-LRC-1:</span> code to CSA. On **every** machine in that environment, set both:
```bash
export RBP_SITE_ID=your-csa-assigned-site-id
export RBP_LICENSE=RBP-LIC-1:…
```
Use the exact site ID CSA sent you. A mismatch will block licensed use.
### Confirm (servers and sites)
```bash
rbp-license-info --viewlicense
```
| What you see | What to try |
| --- | --- |
| Site ID mismatch | Exact <span class="mono">RBP_SITE_ID</span> from CSA on every instance |
| Server was rebuilt | New request code + ask CSA to reissue |
| License not found | Confirm <span class="mono">RBP_LICENSE</span> is set for the session that runs predictions |
***
# Find the license tool
Use this section only if your terminal says it cannot find <span class="mono">rbp-license-info</span>. The tool is installed with the product — your terminal may not be looking in the right folder yet. You can always run it by **full path**.
### Quick checks
1. Open a **new** terminal window after installing.
2. If you used Python + a virtual environment, **activate that environment** first, then try again.
3. Confirm the product is installed ([[Install/Python|Python]] or the [[Install/Native Runtime|CSA installer]]).
### Python install (`pip install rbp-engine`)
**Locate the files (works even when PATH is wrong):**
```bash
python -m pip show -f rbp-engine | grep -i license-info
```
On Windows PowerShell:
```powershell
python -m pip show -f rbp-engine | Select-String license-info
```
Or ask Python for the package `bin` folder:
```bash
python -c "import rbp_engine, pathlib; print(pathlib.Path(rbp_engine.__file__).resolve().parent / 'bin')"
```
| System | Typical locations after `pip install` |
| --- | --- |
| **macOS / Linux** | Inside your environment: `<venv>/bin/rbp-license-info` · or user install: `~/.local/bin/rbp-license-info` · and the bundled binary under `…/site-packages/rbp_engine/bin/rbp-license-info` |
| **Windows** | Inside your environment: `<venv>\Scripts\rbp-license-info.exe` · and the bundled binary under `…\site-packages\rbp_engine\bin\rbp-license-info.exe` |
**Run by full path:**
```bash
# macOS / Linux — virtual environment
./.venv/bin/rbp-license-info
# macOS / Linux — bundled copy next to the package
"$(python -c "import rbp_engine, pathlib; print(pathlib.Path(rbp_engine.__file__).resolve().parent / 'bin' / 'rbp-license-info')")"
```
```powershell
# Windows — virtual environment
.\.venv\Scripts\rbp-license-info.exe
# Windows — bundled copy next to the package
python -c "import rbp_engine, pathlib; print(pathlib.Path(rbp_engine.__file__).resolve().parent / 'bin' / 'rbp-license-info.exe')"
# then paste that path into PowerShell and run it
```
### CSA desktop / server installer (including R)
| System | Where to look |
| --- | --- |
| **macOS** | `/Library/rbp-engine/bin/rbp-license-info` · often also linked as `/usr/local/bin/rbp-license-info` |
| **Linux** | `<install-prefix>/bin/rbp-license-info` — common prefixes include `/opt/rbp-engine` or the folder in your installer README · if you set `RBP_ENGINE_HOME`, try `$RBP_ENGINE_HOME/bin/rbp-license-info` |
| **Windows** | `<install-folder>\bin\rbp-license-info.exe` — often under something like `C:\Program Files\RBP Engine\` or the folder CSA documented · if you set `RBP_ENGINE_HOME`, try `%RBP_ENGINE_HOME%\bin\rbp-license-info.exe` |
```bash
# macOS
/Library/rbp-engine/bin/rbp-license-info
/usr/local/bin/rbp-license-info
# Linux (adjust to your install folder)
/opt/rbp-engine/bin/rbp-license-info
"$RBP_ENGINE_HOME/bin/rbp-license-info"
```
```powershell
# Windows (adjust to your install folder)
& "C:\Program Files\RBP Engine\bin\rbp-license-info.exe"
& "$env:RBP_ENGINE_HOME\bin\rbp-license-info.exe"
```
> [!note]
> Exact folder names can vary by the package CSA sent you. If none of these paths exist, check the README that came with your installer, or ask your CSA contact for the install location on your platform.
### Still stuck?
Email or message your CSA account team with your operating system (macOS, Linux, or Windows) and whether you installed via Python or a CSA installer. They can confirm the path for your build.