> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/self-hosting/software-installation/installation-prerequisites.md).

# Installation Prerequisites

To run appRules, your computer must meet the following criteria:

* **OS** – Windows 10/11, Windows Server 2019/2022 and higher
* [**.NET 8 Runtime**](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) – Required (replaces .NET Framework 4.8.1)
* **ASP.NET Core 8** – Required; must be activated in Windows Features
* **IIS 7 and above** – Optional; appRules includes its own web server (see HostService Settings)

## Installation Notes

* Due to UAC and file permissions in Windows, the installer must be run **As Administrator**.
* IIS and/or HostService each require one open port (default 80 and/or 8080). WebApiService requires an additional port (default 8082). Port 443 must be open if using SSL.
* The caching engine (GarnetServer) requires port **6379** to be open.

The following may be required depending on the target machine platform:

### .NET Runtime Notes

appRules no longer requires .NET Framework. All components — the portal, WebApiService, CachingService, and SchedulerService — run on **.NET 8**.

The Windows Desktop Runtime is not required; the **ASP.NET Core 8 Runtime** (server hosting bundle) is sufficient for server deployments.

> **Recommended download:** [.NET 8 Hosting Bundle](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) — installs both the .NET Runtime and ASP.NET Core Runtime in a single package.

\
 


---

# 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.appstrategy.com/apprules-r-documentation/platform/self-hosting/software-installation/installation-prerequisites.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.