> 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/applications/why-kilo-is-powerful-and-easy.md).

# Is Kilo Powerful and Easy to Use?

Kilo chose flexibility over a fixed template, then added the Kilo AI engine and ready-made Solutions so starting out is easier.

Every IoT platform eventually has to choose between two goals. You can make it easy by limiting what people can do, or you can make nearly anything possible and accept that there is more to learn. Early in Kilo's design, we faced that choice.

## Why did Kilo choose power over simplicity?

We chose power. Kilo lets you define your own readings and units, build widgets and conditions the way your project needs them, write rules from simple threshold checks up to full expressions, and reuse them across every device. You are not limited to what a template foresaw.

That choice has a cost. A platform that can do anything has more to learn, and a newcomer faces a blank canvas.

## What changed?

Two things make the learning curve gentler without removing any of the power.

**Ready-made solutions.** Kilo packages the complete answer to a use case as a ready-made application. You preview it, install it, and see devices, rules, alarms, and a dashboard working right away, with nothing to set up first. The install screen lists the devices to buy, and when they arrive the AI chat can connect them to your application. You learn by examining something that already works. See [Installing a Solution](/applications/installing-a-solution.md).

**The Kilo AI engine.** The AI engine in Kilo is grounded in your own data. It reads the status of your devices, and it can also help you configure the platform: add devices, create rules, and set up alarms. You describe what you want and it helps you set it up. See [AI in Kilo](/ai-assistant.md).

## What does that mean in practice?

| If you are...        | You can...                                                                                                            |
| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| New to IoT           | Install a solution, buy the devices it lists, and ask the AI chat to connect them and to explain or adjust the setup. |
| Experienced with IoT | Start from a ready-made baseline, then use the full rule and automation toolset to refine it.                         |
| Ready to go live     | Buy the devices listed on the install screen, swap the Emulator for them, and keep everything else as configured.     |

You can start from something that works and still change everything in it.


---

# 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/applications/why-kilo-is-powerful-and-easy.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.