> For the complete documentation index, see [llms.txt](https://docs.seoneo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seoneo.io/additional-information/faqs/technical-requirements.md). # Technical Requirements? ### Hardware Requirements In order to run SEO Neo properly, you need to have a VPS or other device with **minimum**: 4 cores, 8GB RAM, and 10GB free hard disk space (Recommended to use SSD hard disk type). For optimal performance it **recomennded** to have 16 GB RAM. SEO Neo requirements depend on how you use the software. Factors that change your system requirements are: * Running very big campaigns (more than 20 link groups/campaigns) * Running multiple campaigns at the same time * Thread settings of your campaigns (you can change how many threads are used for each campaign, in campaign creation form). * Keeping a big number of old (finished) campaigns. This makes software database bigger and slower. This requires a fast SSD hard drive. ### Software Requirements SEO Neo supports the following Operating Systems: * **Windows 10** or higher, **Windows Server 2016** or higher * **MAC OS** (**Intel** / **M** processors) --- # 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, and the optional `goal` query parameter: ``` GET https://docs.seoneo.io/additional-information/faqs/technical-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.