> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/features/server-technical-requirements.md).

# Server Technical Requirements

## Operating systems

* Windows Server 2016 or later (all releases)<br>
* Windows 10 / 11 (recommended for development environments only)

## Web server

* Microsoft IIS 10 or higher<br>
* .NET Framework 4.8

## .NET 4 support

* Support for .NET web services and web forms developed by the client<br>
* WorkflowGen software itself requires .NET Framework 4.8

## Minimum hardware configuration

### Hardware

* Quad-core processor<br>
* 16 GB RAM<br>
* SATA hard disk with 40 GB free

### Database servers

* Microsoft SQL Server 2025
* Microsoft Azure SQL Database with the Integrated Vectorization feature
* PostgreSQL 17.6


---

# 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://docs.workflowgen.com/features/server-technical-requirements.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.