> For the complete documentation index, see [llms.txt](https://docs.flashback.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flashback.tech/guides/private-node-setup.md).

# Deploy Your Private Node

This section covers the complete process for setting up a private Flashgate node on your own infrastructure. A private node allows you to run Flashgate's multi-cloud storage services on your own VPS, giving you full control over your data and infrastructure.

## Setup Process Overview

The private node setup involves two main phases:

1. **Prerequisites** - Prepare your infrastructure, DNS, SSL certificates, and required files
2. **Installation** - Run the automated installation script to deploy and configure the node

## What You'll Get

After successful setup, your private node will provide:

* **S3-compatible API** endpoint for AWS S3 operations
* **GCS-compatible API** endpoint for Google Cloud Storage operations
* **Azure Blob-compatible API** endpoint for Azure Blob Storage operations
* **Nginx reverse proxy** with SSL termination and load balancing
* **Docker-based services** for easy management and updates

## Next Steps

1. Review the [prerequisites](https://docs.flashback.tech/guides/private-node-setup/prerequisites.md) to ensure your infrastructure is ready
2. Follow the [installation guide](https://docs.flashback.tech/guides/private-node-setup/install-via-script.md) to deploy your node


---

# 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.flashback.tech/guides/private-node-setup.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.
