> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/deployment/requirements.md).

# Requirements

You need this before installation.

### System requirements

#### Minimum system requirements:

* Operating system: Ubuntu Server 22.04 LTS or 24.04 LTS.
* Architecture: x86\_64 / AMD64.
* CPU: 1 vCPU.
* RAM: from 1 GB.
* Disk: from 5 GB of free disk space.
* Public static IPv4 address.
* Incoming ports 80 and 443 allowed by the external firewall.
* Outgoing HTTPS connections to api.telegram.org:443 are allowed.
* Root / sudo user.

#### Recommended system requirements:

* Operating system: Ubuntu Server 24.04 LTS.
* Architecture: x86\_64.
* CPU: 2 vCPU.
* RAM: 2 GB / swap file of 1-2 GB if RAM is less than 2 GB.
* Disk: 10 GB of free disk space.
* A clean server, with no existing websites

{% hint style="danger" %}

#### Not recommended:

* ARM64 / AARCH64 architecture.
* Windows Server.
* Ubuntu below 22.04 LTS.
* Server / hosting without a sudo user.
* Non-standard control panels such as Hestia, aaPanel, Plesk, if they already manage nginx/apache/caddy on ports 80 / 443.
  {% endhint %}

### Other requirements:

* Installation key or proof of product purchase.
* Telegram bot token.
* Registered domain.
* AI provider API (Gemini/OpenAI/OpenRouter/Groq).


---

# 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://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/deployment/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.