> For the complete documentation index, see [llms.txt](https://docs.bosonnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bosonnetwork.io/deploy-a-node/installation.md).

# Installation

Boson installs in one of three ways, one per deployment scenario. If you have not chosen a scenario yet, read [Planning a Deployment](/deploy-a-node/planning.md) first: it covers the hardware, network, DNS and certificate requirements this section assumes.

| I want to run...                         | Install with                      | Guide                                                                     |
| ---------------------------------------- | --------------------------------- | ------------------------------------------------------------------------- |
| A DHT-only seed node                     | The `boson-bootstrap` DEB package | [Bootstrap Node](/deploy-a-node/installation/bootstrap-node.md)           |
| A super node for myself or a small group | The `boson` DEB package           | [Personal Super Node](/deploy-a-node/installation/personal-super-node.md) |
| A super node other people rely on        | The one-command setup tool        | [Public Super Node](/deploy-a-node/installation/public-super-node.md)     |

The personal and public deployments install the **same** super node software. They differ in what surrounds it: the DEB package needs nothing else on the machine, while the public setup adds PostgreSQL, nginx, DNS and a real certificate, and reconfigures the node to sit behind them.

***

## Downloads

All packages are published on [Boson.Releases](https://github.com/bosonnetwork/Boson.Releases/releases):

| Package           | File                                                                         | Platforms                     |
| ----------------- | ---------------------------------------------------------------------------- | ----------------------------- |
| Super node        | `boson-<version>-amd64.deb`, `boson-<version>-arm64.deb`                     | Debian and Ubuntu             |
| Bootstrap node    | `boson-bootstrap-<version>-amd64.deb`, `boson-bootstrap-<version>-arm64.deb` | Debian and Ubuntu             |
| ZIP archive       | `boson-<version>-<os>-<arch>.zip`                                            | macOS, Linux, Windows         |
| Public setup tool | `install-super-node.sh`                                                      | Ubuntu LTS and Debian servers |

Every package includes its own Java runtime.

{% hint style="info" %}
**Just trying Boson, or developing against it?** The ZIP archive runs a super node from your home directory without installing a service; see [Install Boson](/getting-started/install.md). If you are building an application, you need no install at all: the SDKs are on Maven Central.
{% endhint %}

***

## How a super node is first configured

Both super node installations begin with the same step: the **setup wizard** generates the node's identity and its configuration files. The DEB package runs it for you, without prompting, during installation. The public setup tool installs that package and then rewrites the generated configuration for PostgreSQL and nginx, keeping the identity the wizard created.

[The Setup Wizard](/deploy-a-node/installation/setup-wizard.md) explains what it generates, where the files go, and how to run it by hand.

***

## After installation

* Adjust the node: [Configuring the Director](/configure-a-node/director-config.md) and [Configuring Services](/configure-a-node/services-config.md)
* Manage users and plans: [Users, Devices & Subscriptions](/operate-a-node/users-devices-subscriptions.md)
* Back up, upgrade and harden the node: [Operations](/operate-a-node/operations.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.bosonnetwork.io/deploy-a-node/installation.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.