> 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/readme.md). # Intro to Kilo Every IoT project follows the same fundamental path:\ **Devices → Connectivity → IoT Platform.** Kilo supports the entire journey — from sourcing hardware, to connecting it, to managing it in the cloud. Kilo is a full-stack IoT company that provides the tools and infrastructure needed to build scalable, connected systems. Our focus is IoT — pure and simple. And we build it **AI-first**. The Kilo IoT Server doesn't treat AI as a feature in a menu — it puts an experienced IoT integrator inside the platform that understands your entire deployment and can do the work with you: onboard devices, write and deploy automations, and configure alarms, all from a plain-language conversation, all grounded in your real data. The result is a platform where setting up and operating IoT is something you can simply *describe*. See the [IoT AI Assistant](/kilo-iot-server/ai-assistant.md). Kilo is built around **three core pillars**, which together cover the entire IoT stack: 1. **Kilo Electronics** (Devices) 2. **Kilo Connectivity** (Connectivity) 3. **Kilo Cloud** (IoT Platform) Kilo is also modular by design. You can use the full Kilo stack for simplicity, or choose only the services you need. For example, you can use Kilo Cloud as your IoT platform while bringing your own devices, or you can source hardware through Kilo Electronics while using your existing platform. *** ### How Kilo Fits the IoT Stack #### Devices — Kilo Electronics Kilo Electronics is the fastest-growing electronics distributor in the Kilo ecosystem. It is our German subsidiary operating out of Germany under **Kilo IoT, GmbH**. [Kilo Electronics](https://kiloelectronics.com/) supplies sensors, gateways, and other IoT hardware to support real deployments. #### Connectivity — Kilo Connectivity Kilo provides IoT connectivity through LoRaWAN and a global Cellular IoT network. We are one of the largest cellular IoT connectivity providers, with more than **800 global connectivity partners**. Our global IoT SIM cards operate in **every country worldwide** without requiring SIM swaps or separate contracts for different regions. #### IoT Platform — Kilo Cloud Kilo Cloud is the platform where device data becomes actionable. It is an AI-first IoT server that enables device management, dashboards, automation, and alerting — with a built-in AI integrator that can provision devices, build and deploy rules, and set up alarms on your behalf. Access it at [**Kilo Cloud**](https://app.kiloiot.io/), the core IoT platform. *** ### Who Kilo Is Built For Kilo is designed for flexibility and scale. Whether you are a system integrator building solutions for customers, a hardware developer deploying connected products, or a business operating hundreds or thousands of devices, Kilo provides the infrastructure needed to bring IoT systems to life. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kiloiot.io/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.