> For the complete documentation index, see [llms.txt](https://doc-op.blurit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc-op.blurit.io/2.5.4/cloud-images/introduction.md).

# Introduction

## AWS Quickstart

**BlurIt On-Premise Cloud Images** are an all-in-one solution designed to run BlurIt On-Premise on your favorite cloud providers. By leveraging our preconfigured cloud images available on the marketplaces, you can deploy the BlurIt On-Premise solution with complete autonomy.

**Important**: while you can autonomously create virtual servers with our images, you still need to contact us to obtain a valid license.&#x20;

## Supported providers

✅ [AWS](https://aws.amazon.com/marketplace/pp/prodview-khnd7pnhybcca?applicationId=AWS-Marketplace-Console\&ref_=beagle\&sr=0-5)

⏳ Azure (late October)

⏳ GCP (November)

## Supported servers

We highly recommend deploying BlurIt OP on virtual server with Nvidia GPU for better performance, although the software can be run on CPU only.

AMD GPU are not supported.

For a complete list of hardware requirements, please [see details here](/2.5.4/blurit-on-premise/requirements.md#hardware-requirements).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc-op.blurit.io/2.5.4/cloud-images/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
