> For the complete documentation index, see [llms.txt](https://guides.privatesolution.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.privatesolution.org/xma-setup/welcome-to-xma.md).

# Welcome to XMA

**XMA** is DMA with nothing to buy and nothing to plug in. Your motherboard does the job of the DMA card.

## How it works

Your main PC already has the hardware XMA needs. The trick is firmware: instead of reading memory through a card, the XMA setup uses your own motherboard's features.

1. **Main PC** — stays exactly as it is. Nothing to install, nothing to open.
2. **The plan** — your firmware is set up for your specific motherboard.
3. **The software** — runs on the main PC and does the whole job.

## What you get with a plan

* Firmware configured for **your** motherboard
* Setup help on Discord whenever you need it
* Software access for as long as your plan is active

## What it costs

Plans start at **$69 / month**. See the current plans on [privatesolution.org](https://privatesolution.org).

{% hint style="info" %}
XMA is the easiest way to start — no card, no case opening, no second PC. If you would rather own hardware once and never pay monthly, look at [Hardware](/hardware/hardware-products.md) instead.
{% endhint %}

## Next step

[Set up XMA](/xma-setup/xma-setup-guide.md) — it is short.


---

# 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://guides.privatesolution.org/xma-setup/welcome-to-xma.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.