> For the complete documentation index, see [llms.txt](https://guide.moontrader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.moontrader.com/en-moontrader-docs/getting-started/system-requirements.md).

# System Requirements

### Supported Processor Architectures

Only x86-64 (AMD64) and ARM64 architectures are supported. 32-bit systems are not supported.

### Operating Systems

#### Windows:

* Windows 10 x64 version 2004 and above
* Windows Server 2019 and above
* Windows Server 2016 — possible with Visual C++ Redistributable 2010 and .NET 8 installed, but operation is not guaranteed

#### Linux:

* Ubuntu 20.04+
* Debian 11+
* AWS Linux 2.0+
* CentOS 9.0+
* Similar distributions for x86-64 (AMD64)
* Requires Microsoft .NET 8 Runtime

#### macOS — client only:

* macOS 12+ x86-64
* macOS on Apple Silicon processors (M1/M2/M3/M4)
* Requires Microsoft .NET 8 Runtime

### Internet Connection Requirements

The higher the internet speed, the better. Connection stability is especially important for uninterrupted algorithm operation.

### MoonTrader Client Requirements

**Important:** the client actively uses the graphics processor.

**Minimum specifications:**

* Processor: 2 cores at 1.5 GHz
* RAM: 2 GB
* Graphics card: 2 GB VRAM

### VPS/VDS Requirements (MTCore)

**Minimum specifications:**

* Processor: 2 cores at 1.5 GHz
* RAM: 2 GB
* Supports up to 150 active orders

**Recommended specifications:**

* Processor: 4 cores at 2 GHz
* RAM: 2 GB

<figure><img src="https://2194691319-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPMuOulAKIicy77MPPDXF%2Fuploads%2Fuft9tGFNTMT69HkiHtVh%2FVPS.png?alt=media&amp;token=061936da-a9e3-4bcf-a41c-5ca8c1a49ead" alt=""><figcaption></figcaption></figure>

### Suitable VPS Examples

* **AWS Amazon:** t3.small and above
* **Google Cloud:** n2-highcpu-2
* **Vultr:** 2048 MB High Frequency
* **Inferno Solutions**: 2×2.9 GHz, 2 GB DDR4

**Important:** these options are provided for reference only and are not a purchase recommendation.

<figure><img src="https://2194691319-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPMuOulAKIicy77MPPDXF%2Fuploads%2Fgit-blob-3e40fa527bc208df44e0b5797ea4713d39bbbc13%2Fworld-map-tokyo.png?alt=media" alt=""><figcaption></figcaption></figure>

### Optimal VPS Regions

Place your server as close as possible to the exchange servers:

* **Binance:** Tokyo, Japan
* **OKX:** Tokyo, Japan
* **Bybit:** Tokyo, Japan

**Important:** the closer the VPS to exchange servers, the lower the latency in order execution.


---

# 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://guide.moontrader.com/en-moontrader-docs/getting-started/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.
