> For the complete documentation index, see [llms.txt](https://wirebox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wirebox.ortusbooks.com/getting-started/installing-wirebox.md).

# Installing WireBox

WireBox can be installed as a standalone framework or included with the latest ColdBox Platform release, so it is unnecessary if you are within a ColdBox application.

## Supported Languages

WireBox supports both **BoxLang** (preferred) and **CFML** (ColdFusion Markup Language):

| Language    | Extensions            | Notes                                                      |
| ----------- | --------------------- | ---------------------------------------------------------- |
| **BoxLang** | `.bx`, `.bxm`, `.bxs` | Preferred — modern JVM language, owned by the ColdBox team |
| **CFML**    | `.cfc`, `.cfm`        | Fully supported for existing applications                  |

## System Requirements

* **BoxLang** 1+ (Preferred)
* **Adobe ColdFusion** 2023+
* **Lucee** 6+

## Standalone Installation

You can leverage [CommandBox](http://www.ortussolutions.com/products/commandbox) to install the standalone version of WireBox with a simple command:

```bash
# Latest Version
box install wirebox

# Bleeding Edge
box install wirebox@be
```

This will install WireBox as a dependency in your application into a folder called `wirebox`. You can then leverage the standalone namespace within your application: `wirebox.system.ioc`.

### Mappings

You will need the following mapping that points to the folder you installed `wirebox` into:

{% tabs %}
{% tab title="BoxLang" %}

```java
// Application.bx
this.mappings[ "/wirebox" ] = expandPath( "path/to/wirebox" );
```

{% endtab %}

{% tab title="CFML" %}

```cfscript
// Application.cfc
this.mappings[ "/wirebox" ] = "path.to.wirebox";
```

{% endtab %}
{% endtabs %}

This will ensure that the appropriate libraries can find each other.

{% hint style="danger" %}
Remember that this only applies to the standalone approach.
{% endhint %}

## Namespaces

### Standalone Namespace

`wirebox.system.ioc`

![](https://content.gitbook.com/content/MtgLfPeIR8KWTwoO8bDr/blobs/HcGmJNGeXH681IqV8wZy/installing_WireBoxSystem.jpg)

### ColdBox Namespace

`coldbox.system.ioc`

![](https://content.gitbook.com/content/MtgLfPeIR8KWTwoO8bDr/blobs/B2v0tPWzi9HwZzjuaWQl/installing_ColdBoxSystem.jpg)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wirebox.ortusbooks.com/getting-started/installing-wirebox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.