> 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/what-is-kilo-connectivity.md). # What is Kilo Connectivity? Understand Kilo cellular IoT connectivity, SIM services, and how network access differs from IoT Server device integration. Kilo Connectivity lets IoT equipment communicate through mobile networks when a deployment cannot rely on site Wi-Fi or a nearby private radio gateway. Use cellular service for a remote meter, a controller, or the backhaul connecting field equipment to its application. A compatible modem uses a **SIM** to identify its mobile subscription and exchange data on an available operator network. This section covers that cellular connection and its management; the IoT Server's connectors handle how application messages enter Kilo. The SIM identifies the mobile subscription. The [connectivity platform](/connectivity-platform.md) is where you manage that service and its usage. The [Kilo IoT Server](/kilo-iot-server.md) has a different job: managing device data, dashboards, and automation. Its software connectors do not replace a cellular subscription. Start with [Global IoT SIM Cards](/what-is-kilo-connectivity/cellular-iot.md) to understand the service, then compare [SIM card types](/what-is-kilo-connectivity/simcardtypes.md) for your equipment. Check coverage, modem compatibility, supported networks, and plan terms for the places where the devices will operate. --- # 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/what-is-kilo-connectivity.md?ask=&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.