> For the complete documentation index, see [llms.txt](https://docs.wproofreader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wproofreader.com/v6.11.1/deployment/installation-requirements/on-premise-versions-support.md).

# On-premise versions support

**Which version should I use?**

We generally recommend using the latest available WProofeader SDK on-premise version. This is where we commit all new features, performance improvements, and enhancements. We actively test and QA the latest version, and it is completely suitable for production use.

If you are concerned about the overhead of monitoring the latest WProofeader SDK on-premise version for new features and bug fixes, then using any of the supported versions means that you only need to review new functionality once/twice a year, and bug fixes on an infrequent basis. You can view the up-to-date information on the product enhancements, bug fixes and new features added in the release notes.

Note, that updates and bug fixes are released only as a part of the new version. These changes can't be applied to the previous WebSpellChecker versions and require updating.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wproofreader.com/v6.11.1/deployment/installation-requirements/on-premise-versions-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.