> For the complete documentation index, see [llms.txt](https://docs.hexabot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hexabot.ai/faq/how-can-i-deploy-my-hexabot-project.md).

# How can I deploy my Hexabot project?

Choose a Docker or manual deployment path for Hexabot v3 behind NGINX, PostgreSQL, and HTTPS.

Use this guide to choose the right production path for Hexabot v3.

Hexabot supports both direct host deployment and Docker-based deployment.

### Choose your deployment method

* [Docker Deployment](/faq/how-can-i-deploy-my-hexabot-project/docker-deployment.md) — use this when you want Compose-managed services and a containerized runtime.
* [Manual Deployment](/faq/how-can-i-deploy-my-hexabot-project/manual-deployment.md) — use this when you want to run Hexabot directly with Node.js on the host.

### What stays the same

Hexabot serves the admin UI and API from the same NestJS app.

* The default app port is `3000`.
* The API lives under `/api`.
* The health check lives at `/api/health`.

NGINX should proxy all traffic to the same app port.

Do not strip or rewrite `/api`.

### Shared prerequisites

You need:

* A Linux server with SSH access
* Node.js `>= 24.17.0`
* One package manager: `npm`, `pnpm`, `yarn`, or `bun`
* PostgreSQL
* NGINX
* Certbot

Install Docker only if you choose the Docker path.

Helpful setup guides:

* [Setup Node.js with NVM](/developer-guide/setup-node.js-with-nvm.md)
* [Setting Up Docker](/developer-guide/setting-up-docker.md)
* [CLI Command Reference](/developer-guide/cli-command-reference.md)
* [SMTP Configuration](/developer-guide/smtp-configuration.md)

### Shared production notes

Keep the first database bootstrap private.

The first admin and baseline data are seeded only outside production mode.

For ongoing production:

* Keep `DB_SYNCHRONIZE=false`
* Keep `DB_AUTO_MIGRATE=true` on one primary API node only
* Match `client_max_body_size` with `UPLOAD_MAX_SIZE_IN_BYTES`
* Use PostgreSQL instead of SQLite

Hexabot uses `.env` for manual deployment and `.env.docker` for Docker deployment.

### Next step

Open the guide that matches your runtime and follow it end to end:

* [Docker Deployment](/faq/how-can-i-deploy-my-hexabot-project/docker-deployment.md)
* [Manual Deployment](/faq/how-can-i-deploy-my-hexabot-project/manual-deployment.md)


---

# 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.hexabot.ai/faq/how-can-i-deploy-my-hexabot-project.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.