> 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/getting-started.md).

# First Steps

Get oriented with Kilo IoT Server and walk through your first LoRaWAN deployment from gateway to live dashboard.

Get your first device reporting, put its readings on a dashboard, and create a response your team can use. You can let the [AI Assistant](/getting-started/let-ai-set-it-up.md) handle configuration with you, or follow the hands-on LoRaWAN walkthrough in this section.

The walkthrough explains each step from radio connection to a useful application. Other device protocols have their own starting points; choose the matching [connector](/connectors.md) when your project uses MQTT, MIOTY, or a tracker.

<figure><img src="https://2057878315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtNQh1wBSHSaknslMdOXm%2Fuploads%2Fgit-blob-988b95effffe48b2df420bf690f2d48b2ab68cbb%2Fsidebar-and-overview.jpg?alt=media" alt="The Kilo IoT Server sidebar beside the Overview page with its device and gateway counts, notifications and news"><figcaption></figcaption></figure>

**Start here if you would rather not do it by hand.** [Let AI Set It Up for You](/getting-started/let-ai-set-it-up.md) covers the two ways to have AI do the setup work — the assistant built into Kilo, or the AI client you already use connected over MCP — and what each one will and will not do on its own. For many people that is the shortest route to a working deployment; the manual walkthrough below is still here whenever you want to understand the mechanics.

## What's in this section

| Page                                                                     | What you'll learn                                                                                                       |
| ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| [Let AI Set It Up for You](/getting-started/let-ai-set-it-up.md)         | Have the built-in assistant or your own AI client register devices, write the automation and configure alarms with you  |
| [Navigating the Interface](/getting-started/navigating-the-interface.md) | A walkthrough of every section of the dashboard — sidebar, user menu, overview page, themes, and language               |
| [Your First Deployment](/getting-started/your-first-deployment.md)       | A LoRaWAN quickstart: register a gateway, set up an LNS connector, add a device, build a dashboard, and set up an alarm |

## Prerequisites

* A Kilo IoT account (cloud or on-premise)
* A modern web browser (Chrome, Firefox, Safari, Edge)

**Hardware is optional.** The [Emulator connector](/connectors/emulator-connector.md) creates devices that generate their own telemetry from real device presets, so you can build and test an entire deployment — dashboards, rules, escalating alarms — before any hardware arrives, then switch those same devices to a real connector when it does and keep everything you built.

To follow the hands-on LoRaWAN guide with real equipment you will want a LoRaWAN gateway and at least one sensor with its Device EUI and AppKey. Without them, use the Emulator and the guide still works end to end.

## The LoRaWAN quick-start flow

The typical LoRaWAN path from zero to a working deployment follows these steps:

```
Create account → Deploy gateway → Set up connector → Register device → View telemetry → Build dashboard → Set up alarm
```

Not every Kilo deployment begins with a gateway. LoRaWAN does. Direct integrations can start at the connector and device-modeling steps instead.

Each step builds on the previous one. In the LoRaWAN journey, the gateway provides network coverage, the device sends data through that gateway, the dashboard visualizes the data, and alert rules monitor it for conditions that need your attention.

The [Your First Deployment](/getting-started/your-first-deployment.md) guide walks through this entire sequence.

## After the basics

Once you have live data, integrate Kilo with your own systems through the [API](/api.md) — REST for standard integrations, and gRPC for typed, service-to-service, and on-premise/industrial automation.

## Start with an existing camera

For a video deployment, follow [Installing Twin](/lens/installing-twin.md) and [Connecting a Camera](/lens/connecting-a-camera.md). Each camera uses its own local Twin container; no LoRaWAN gateway is involved in this path.


---

# 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/getting-started.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.
