> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-system-requirements-prerequisites.md).

# LogicNets Installation: System Requirements & Prerequisites

## Description

To install LogicNets on a local machine requires the following server specifications and prerequisite actions.

## Recommended System Requirements

LogicNets recommends using a recent multi-core server with the following specifications:

* 4 or more cores
* 8 GB RAM or more
* 60+ GB of SSD storage

## Windows Prerequisites

The following prerequisites are required for Windows-based installations.

* Windows Server 2016, Windows Server 2022 (64-bit)
* Internet Information Services (IIS) with CgiModule installed
* Microsoft Visual C++ 2013 Redistributable (this is installed as part of the LogicNets Installation)
* IIS Rewrite Rules Module (this is installed as part of the LogicNets Installation)

For v8.1+, the LogicNets runtime is 64-bit on Windows. It requires the following prerequisite:

* Microsoft Visual C++ Redistributable package vcredist (a Visual Studio redistributable) 64-bit version

## Unix Prerequisites

The following prerequisites are required for Unix-based installations. **Note:** Not all LogicNets features (e.g. Designer, PDF Generation) are available as Linux-based installations.

* CentOS 7 or Later (From Release 8+, LogicNets does not support CentOS. LogicNets does support Ubuntu 20.04 LTS and Ubuntu 22.04 LTS.)
* Apache Web Server, Including mod\_ssl and mod\_rewrite
* unixODBC\*
* OpenSSL
* Zip and Unzip Utilities\*

\* The tool location must be included in the path variable so the system can access the tools from any location on the server.

## Website Domain

The following prerequisites are required for all installations.

* A website sub-domain (e.g. logicnets.mycompany.com) must be available and bound to the server that hosts LogicNets.
* The website hostname/domain must be a fully qualified domain name (FQDN, e.g. <https://mydomain.com> or <https://sub.mydomain.com>). Single Word Domains (<https://mydomain/>) are not supported in conjunction with IE and HTTPS, because of IE restrictions.
* LogicNets must be directly hosted under the sub-domain (e.g. "<https://logicnets.mycompany.com>").

**Important:** LogicNets cannot be installed within a virtual (sub-) directories (e.g. "<https://logicnets.mycompany.com/subfolder>"), since the runtime and security architecture assumes a specific structure for the URLs.

## Email Prerequisites

LogicNets allows you to model functionality to send email. Before this functionality can be used, however, you must correctly configure the server running LogicNets with email functionality. For more information on this, see [Email from On-premise Hosted Server](/release-9/platform-documentation/system-administration/email-configuration/email-from-on-premise-hosted-server.md).


---

# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/installation/logicnets-installation-system-requirements-prerequisites.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.