> 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/deploying-and-managing-a-self-hosted-instance/using-docker-compose.md).

# Using Docker Compose

The following guide walks you through self-hosting Fabricate on a single virtual private server (VPS) or a bare metal server.

This deployment uses a Docker Compose setup where:

* All services run on the same machine.
* Data are stored in local volumes.

You can host Fabricate on any cloud provider, such as:

* Amazon EC2
* Google Cloud VM
* Microsoft Azure VM
* DigitalOcean droplet

You can also deploy Fabricate on a bare metal server.

This guide uses an Amazon EC2 instance, but the setup is the same for any other provider.

Before you start, confirm that your server meets the [minimum hardware requirements](https://docs.tonic.ai/fabricate/self-hosting-fabricate/fabricate-requirements.md).

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>System requirements</strong><br><br>Requirements for a Docker Compose deployment.</td><td><a href="https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/system-requirements-for-docker-compose-deployment.md">System requirements for Docker Compose deployment</a></td></tr><tr><td><strong>Complete the deployment</strong><br><br>Steps to complete a Fabricate deployment using Docker compose.</td><td><a href="https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/completing-a-docker-compose-deployment.md">Completing a Docker Compose deployment</a></td></tr><tr><td><strong>Troubleshoot the deployment</strong><br><br>Common issues and how to address them.</td><td><a href="https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/troubleshooting-a-docker-compose-deployment.md">Troubleshooting a Docker Compose deployment</a></td></tr><tr><td><strong>Upgrade Fabricate</strong><br><br>How to upgrade your instance to a new version of Fabricate.</td><td><a href="https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/upgrading-fabricate-from-docker-compose.md">Upgrading Fabricate from Docker Compose</a></td></tr><tr><td><strong>Uninstall Fabricate</strong><br><br>Removing a Fabricate instance.</td><td><a href="https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/removing-a-docker-compose-deployment.md">Removing a Docker Compose deployment</a></td></tr></tbody></table>


---

# 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/deploying-and-managing-a-self-hosted-instance/using-docker-compose.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.
