> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/self-hosting-fabricate/fabricate-requirements.md). # Fabricate requirements The server or cluster that you deploy Fabricate to must at a minimum have access to the following resources:

Resource	Requirement
CPUs	Minimum: 2 vCPUs Supported architectures: `AMD64 (x86-64)`, `ARM64 (aarch64)`
Memory	Minimum: 4 GiB Recommended: 16 GiB
Disk space	Minimum: 32 GiB (for Database, Redis, Docker images) For best performance, recommend NVMe SSD storage with high IOPS.
SMTP server	An external SMTP server is required. Supported protocols: `STARTTLS (587), TLS / SSL (465)`
LLM Provider	An external LLM provider is required for AI features. Supported providers: Amazon Bedrock, Anthropic, Azure AI Foundry
Access to quay.io	Fabricate images are available for Enterprise customers on the quay.io registry. To access the images, you must authenticate using credentials provided to you by Tonic.ai. For details, contact sales@tonic.ai.

--- # 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://docs.tonic.ai/fabricate/self-hosting-fabricate/fabricate-requirements.md?ask=&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.