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

# Supported Engines

CFConfig covers most of the common settings you'll find in Adobe and Lucee servers. This includes datasources, CF Mappings, Lucee caches, mail servers, logging settings, debugging settings, event gateways (Adobe), scheduled tasks (Adobe), and custom tag paths.

If you find a setting or feature which is not supported, please send a pull request. If you don't have time for a pull request, please [enter a ticket](https://ortussolutions.atlassian.net/projects/CFCONFIG) so we can track remaining features.

Here's an overview of what's supported.

* **BoxLang 1.x**
* **Lucee 6.x**
* **Lucee 5.x**
* **Lucee 4.x**
* **Adobe CF 2025**
* **Adobe CF 2023**
* **Adobe CF 2021**
* **Adobe CF 2018**
* **Adobe CF 2016**
* **Adobe CF 11**
* **Adobe CF 10**
* **Adobe CF 9**
* **Railo 4.x**

## Sponsored Support

If there is an engine/version or specific setting that's very important to you, Ortus is happy to have sponsored features. Please [contact us](https://www.ortussolutions.com/#contact) if you'd like to sponsor a feature.


---

# 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://cfconfig.ortusbooks.com/the-basics/supported-engines.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.