> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/installation/system-requirements.md).

# System Requirements

## Access Manager Server (AMS) Operating System Support

### Operating system requirements

The Lithnet Access Manager Service requires Windows Server 2016 or higher.

#### Dependencies

* [.NET Desktop Runtime](https://dotnet.microsoft.com/en-us/download/dotnet/10.0/runtime) 10.0 or later installed
* [ASP.NET Core Runtime](https://dotnet.microsoft.com/en-us/download/dotnet/10.0/runtime) 10.0 or later installed
* Microsoft SQL Express 2022 (if hosting the database locally), SQL Server 2019 or later (Standard or Enterprise edition), Azure SQL or an Amazon RDS SQL database. (SQL express is installed by default). See the [SQL installation options](/ams/installation/installing-the-access-manager-server/sql-installation-options.md) page for more details

## Access Manager Agent Operating System Support

The Lithnet Access Manager agent is supported on Windows, macOS, and Linux. Each operating system family has slightly different requirements.

### Windows requirements

#### Dependencies

The agent requires the installation of .NET Framework 4.7.2 or later if it is not already installed as part of the OS for x64 installations. For arm64 installations, .NET Framework 4.8.1 is required.

#### Supported versions

* x64 Windows 10 / Windows Server 2016 or later
* arm64 Windows 10 or later

### macOS requirements

#### Supported versions

* macOS 14 (Sonoma) (Intel or ARM64)
* macOS 15 (Sequoia) (Intel or ARM64)
* macOS 26 (Tahoe) (ARM64)

### Linux requirements

#### Dependencies

The Access Manager Agent requires the use of the `chpasswd` tool that is built into most modern Linux systems.

#### Supported versions

The agent runs on .NET 10 and should work on any Linux distribution supported by Microsoft for these platforms.

Lithnet provides packages for RPM and Debian-based distributions, as well as tar.gz file for use with others.

See the [Microsoft guide for supported operating systems for .NET 10](https://github.com/dotnet/core/blob/main/release-notes/10.0/supported-os.md)

The following operating system versions have been tested and are supported by Lithnet while they are within their vendor support lifecycle:

| Distribution | Version | Architecture |
| ------------ | ------- | ------------ |
| Ubuntu       | 22.04   | x64/arm64    |
| Ubuntu       | 24.04   | x64/arm64    |
| Ubuntu       | 26.04   | x64/arm64    |
| RHEL         | 8       | x64/arm64    |
| RHEL         | 9       | x64/arm64    |
| RHEL         | 10      | x64/arm64    |
| Fedora       | 42      | x64/arm64    |
| Fedora       | 43      | x64/arm64    |
| Fedora       | 44      | x64/arm64    |
| Debian       | 12      | x64/arm64    |
| Debian       | 13      | x64/arm64    |


---

# 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.lithnet.io/ams/installation/system-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.