> 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/connect/create-nodes/deploy-your-node/install-private-nodes.md).

# Install private nodes

You can build your own nodes and install them in your n8n instance without publishing them on npm. This is useful for nodes that you create for internal use only at your company.

## Install your node in a Docker n8n instance <a href="#install-your-node-in-a-docker-n8n-instance" id="install-your-node-in-a-docker-n8n-instance"></a>

If you're running n8n using Docker, you need to create a Docker image with the node installed in n8n.

1. Create a Dockerfile and paste the code from [this Dockerfile](https://github.com/n8n-io/n8n/blob/master/docker/images/n8n/Dockerfile).

   Your Dockerfile should look like this:

   ```dockerfile
   FROM node:16-alpine

   ARG N8N_VERSION

   RUN if [ -z "$N8N_VERSION" ] ; then echo "The N8N_VERSION argument is missing!" ; exit 1; fi

   # Update everything and install needed dependencies
   RUN apk add --update graphicsmagick tzdata git tini su-exec

   # Set a custom user to not have n8n run as root
   USER root

   # Install n8n and the packages it needs to build it correctly.
   RUN apk --update add --virtual build-dependencies python3 build-base ca-certificates && \
   	npm config set python "$(which python3)" && \
   	npm_config_user=root npm install -g full-icu n8n@${N8N_VERSION} && \
   	apk del build-dependencies \
   	&& rm -rf /root /tmp/* /var/cache/apk/* && mkdir /root;


   # Install fonts
   RUN apk --no-cache add --virtual fonts msttcorefonts-installer fontconfig && \
   	update-ms-fonts && \
   	fc-cache -f && \
   	apk del fonts && \
   	find  /usr/share/fonts/truetype/msttcorefonts/ -type l -exec unlink {} \; \
   	&& rm -rf /root /tmp/* /var/cache/apk/* && mkdir /root

   ENV NODE_ICU_DATA /usr/local/lib/node_modules/full-icu

   WORKDIR /data

   COPY docker-entrypoint.sh /docker-entrypoint.sh
   ENTRYPOINT ["tini", "--", "/docker-entrypoint.sh"]

   EXPOSE 5678/tcp
   ```
2. Compile your custom node code (`npm run build` if you are using nodes starter). Copy the **node** and **credential** folders from within the **dist** folder into your container's `~/.n8n/custom/` directory. This makes them available to Docker.
3. Download the [docker-entrypoint.sh](https://github.com/n8n-io/n8n/blob/master/docker/images/n8n/docker-entrypoint.sh) file, and place it in the same directory as your Dockerfile.
4. Build your Docker image:

   ```dockerfile
   # Replace <n8n-version-number> with the n8n release version number. 
   # For example, N8N_VERSION=0.177.0
   docker build --build-arg N8N_VERSION=<n8n-version-number> --tag=customizedn8n .
   ```

You can now use your node in Docker.

## Install your node in a global n8n instance <a href="#install-your-node-in-a-global-n8n-instance" id="install-your-node-in-a-global-n8n-instance"></a>

If you've installed n8n globally, make sure that you install your node inside n8n. n8n will find the module and load it automatically.


---

# 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/connect/create-nodes/deploy-your-node/install-private-nodes.md?ask=<question>&goal=<endgoal>
```

`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.