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

# Deploying a LoRaWAN Gateway

Register a LoRaWAN gateway in Kilo IoT by Gateway EUI, download Basics Station certificates, and go online.

This page walks through registering a new LoRaWAN gateway with the Kilo IoT Server and configuring the hardware to connect.

## Prerequisites

* A LoRaWAN gateway that supports the **Basics Station** protocol
* The gateway's **Gateway EUI** — a unique 16-character hexadecimal identifier, typically printed on a label on the device
* The gateway installed where it has a suitable power source and an internet connection or backhaul (for example Ethernet, Wi-Fi, LTE, or satellite, depending on the model)

## Step-by-step

### Register the gateway

1. Click **Gateways** in the left sidebar.
2. Click the **Add gateway** button, then choose **3rd Party Gateway** — the dialog asks which kind of device you are connecting.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-bf82736e60c92927f6a319f7f9f4a8797d69d29e%2Fgateway-add-type-chooser.jpg?alt=media" alt="The Add gateway dialog asking whether you are connecting a 3rd party gateway or a Mioty base station"><figcaption></figcaption></figure>

3. Enter a **Name** for the gateway — something that identifies its location or purpose (e.g., "Warehouse A — Loading Dock").

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-cccba3fa735b0b7059d41535700832fff4129996%2Fgateway-add-details.jpg?alt=media" alt="The Add a new gateway step with the Name, Select region and Gateway EUI fields"><figcaption></figcaption></figure>

4. Select the **region** from the dropdown. This must match the LoRaWAN frequency band supported by your gateway hardware and used for the deployment. If the gateway was purchased for use in your country, the common regional band is often correct, but you should still verify the hardware specification.

   | Region            | Typical selection                                                                                                |
   | ----------------- | ---------------------------------------------------------------------------------------------------------------- |
   | EU868             | Most deployments in Europe                                                                                       |
   | US915-0 / US915-1 | United States deployments; select the variant that matches your network plan                                     |
   | AU915-0           | Australia deployments                                                                                            |
   | AS923 / AS923-2   | Asia-Pacific deployments where these bands are used                                                              |
   | IN865             | India deployments                                                                                                |
   | KR920             | South Korea deployments                                                                                          |
   | RU864             | Russia deployments                                                                                               |
   | EU433             | Special-case 433 MHz deployments; use only if the gateway hardware is specifically built or configured for EU433 |

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-1a1ccd0503c7006a5deb22772a6f5cd4b67d4be5%2Fgateway-add-region.jpg?alt=media" alt="The region dropdown open, listing the available LoRaWAN bands"><figcaption></figcaption></figure>

5. Enter the **Gateway EUI** — the 16-character identifier from the gateway hardware. This is not the same as a device's Device EUI; it uniquely identifies the gateway itself. Name, region and EUI are all on this one screen; if your model is not offered, use **My device is not on the list**.
6. Click **Next**.

### Download certificates and LNS address

After submitting the gateway details, the next screen displays:

7. Your gateway's **Name**, **Region**, and **Gateway EUI** for confirmation.
8. The **LNS Address** — click the copy icon to copy it to your clipboard. This is the server endpoint your gateway will connect to.
9. The **certs.zip** file — click the download icon to save the certificate bundle. These TLS certificates authenticate the gateway's Basics Station connection.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-c04852eb2f10b31689b2c412dd411808d9c7c85d%2Fgateway-add-lns-certs.jpg?alt=media" alt="The gateway summary showing the LNS address with its copy control and the certs.zip download"><figcaption></figcaption></figure>

10. Click **Continue**.

A toast confirms *"3rd party gateway was successfully added"* and the gateway appears in the list straight away. The wizard then offers an optional step to upload up to three photos of the hardware — useful for identifying the unit on a future site visit. Add them now or click **Continue** to skip.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-bc427b4a515f77536d2748310c004225fcbeacaa%2Fgateway-add-photo.jpg?alt=media" alt="The optional device photo step, with the gateway already listed behind the dialog"><figcaption></figcaption></figure>

### Configure the gateway hardware

With the LNS address and certificates in hand, you now configure the gateway itself:

1. Access the gateway's management interface — this may be a local web interface, a device IP on your network, or a vendor-managed portal, depending on the gateway model.
2. Navigate to the LoRaWAN or Basics Station configuration section.
3. Enter the **LNS Address** you copied from the server.
4. Upload or point to the **TLS certificates** from the downloaded `certs.zip`.
5. Save the configuration and restart the gateway if required.

The exact steps vary by gateway manufacturer — refer to your gateway's documentation for its specific Basics Station configuration interface.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2FYqbtHA2GwXpAQwCIyvj3%2Fbasicsstation.jpg?alt=media&amp;token=82a11437-c4b3-466f-8674-9befc24d8355" alt="Gateway Basics Station configuration — select Basics Station mode"><figcaption></figcaption></figure>

### Verify the connection

Once the gateway establishes its Basics Station connection, it will appear in the **Gateways** list with an online status.

This typically takes a few minutes after configuration.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-c8570851f666441f6b94c72cb9ccec3da54b5126%2Florawan-gateways-table.jpg?alt=media" alt="The LoRaWAN Gateways tab listing a gateway with its status, EUI, location and firmware version"><figcaption></figcaption></figure>

If the gateway does not come online:

* Verify the LNS Address was entered correctly (no extra spaces or characters)
* Confirm the certificates were uploaded to the correct location on the gateway
* Check that the gateway has internet access and can reach external endpoints
* Ensure the gateway firmware supports Basics Station (some older firmware versions may need an update)

These steps describe the current gateway registration path. Other options in the interface related to crypto-based onboarding programs are unrelated to IoT gateway deployment and are excluded from this documentation.

## Tips

* **Placement matters.** Gateways work best when elevated — mounted on a wall, placed on a high shelf, installed on a mast, or mounted on a rooftop. LoRaWAN signals pass through walls but lose strength with each barrier.
* **One gateway can cover a lot.** In a typical indoor deployment, a single gateway covers an entire floor or small building. Start with one and add more only if you see coverage gaps in device connectivity.
* **Remote deployment is possible.** Some gateways can operate with autonomous power systems such as solar and use cellular or satellite backhaul, making them practical for remote industrial locations where no local LAN is available.
* **Keep certificates secure.** The `certs.zip` file authenticates your gateway. Store it securely and do not share it. If a certificate is compromised, you can regenerate it from the gateway's Settings page.


---

# 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.kiloiot.io/gateways/lorawan-gateways/deploying-a-lorawan-gateway.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.