> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku.md).
# Deploy to Heroku
This hosting guide shows you how to self-host n8n on Heroku. It uses:
* [Docker Compose](https://docs.docker.com/compose/) to create and define the application components and how they work together.
* [Heroku's PostgreSQL service](https://devcenter.heroku.com/categories/heroku-postgres) to host n8n's data storage.
* A **Deploy to Heroku** button offering a one click, with minor configuration, deployment.
{% hint style="info" %}
**Self-hosting knowledge prerequisites**
Self-hosting n8n requires technical knowledge, including:
* Setting up and configuring servers and containers
* Managing application resources and scaling
* Securing servers and applications
* Configuring n8n
n8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime. If you aren't experienced at managing servers, n8n recommends [n8n Cloud](https://n8n.io/cloud/).
{% endhint %}
{% hint style="info" %}
**Stable and Beta versions**
n8n releases a new minor version most weeks. The `stable` version is for production use. `beta` is the most recent release. The `beta` version may be unstable. To report issues, use the [forum](https://community.n8n.io/c/questions/12).
Current `stable`: 2.27.4 Current `beta`: 2.28.1
{% endhint %}
## Use the deployment template to create a Heroku project
The quickest way to get started with deploying n8n to Heroku is using the **Deploy to Heroku** button:
[](https://dashboard.heroku.com/new?template=https://github.com/n8n-io/n8n-heroku/tree/main)
This opens the **Create New App** page on Heroku. Set a name for the project, and choose the region to deploy the project to.
### Configure environment variables
Heroku pre-fills the configuration options defined in the `env` section of the `app.json` file, which also sets default values for the environment variables n8n uses.
You can change any of these values to suit your needs. You must change the following values:
* **N8N\_ENCRYPTION\_KEY**, which n8n uses to [encrypt user account details](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/deployment.md) before saving to the database.
* **WEBHOOK\_URL** should match the application name you create to ensure that webhooks have the correct URL.
### Deploy n8n
Select **Deploy app**.
After Heroku builds and deploys the app it provides links to **Manage App** or **View** the application.
{% hint style="info" %}
**Heroku and DNS**
Refer to the [Heroku documentation](https://devcenter.heroku.com/categories/networking-dns) to find out how to connect your domain to a Heroku application.
{% endhint %}
## Changing the deployment template
You can make changes to the deployment template by forking the [repository](https://github.com/n8n-io/n8n-heroku) and deploying from you fork.
### The Dockerfile
By default the Dockerfile pulls the latest n8n image, if you want to use a different or fixed version, then update the image tag on the top line of the `Dockerfile`.
### Heroku and exposing ports
Heroku doesn't allow Docker-based applications to define an exposed port with the `EXPOSE` command. Instead, Heroku provides a `PORT` environment variable that it dynamically populates at application runtime. The `entrypoint.sh` file overrides the default Docker image command to instead set the port variable that Heroku provides. You can then access n8n on port 80 in a web browser.
{% hint style="info" %}
**Docker limitations with Heroku**
[Read this guide](https://devcenter.heroku.com/articles/container-registry-and-runtime#unsupported-dockerfile-commands) for more details on the limitations of using Docker with Heroku.
{% endhint %}
### Configuring Heroku
The `heroku.yml` file defines the application you want to create on Heroku. It consists of two sections:
* `setup` > `addons` defines the Heroku addons to use. In this case, the PostgreSQL database addon.
* The `build` section defines how Heroku builds the application. In this case it uses the Docker buildpack to build a `web` service based on the supplied `Dockerfile`.
## Next steps
* Learn more about [configuring](/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables.md) and [scaling](/deploy/host-n8n/configure-n8n/scaling.md) n8n.
* Or explore using n8n: try the [Quickstarts](https://github.com/n8n-io/n8n-docs/blob/main/try-it-out/index.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 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.n8n.io/deploy/host-n8n/install-options/use-a-cloud-provider/deploy-to-heroku.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.