> 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/kilo-center/kilo-mioty-service-center.md).

# Kilo MIOTY Service Center

- [Project Overview](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/project-overview.md): KiloCenter project overview — MIOTY-native open-source server with Docker, Linux-host, and Kubernetes deploy paths.
- [Next Steps](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/next-steps.md): KiloCenter next steps — install, onboard a base station, set up integrations, configure security, run operations.
- [License And Trademarks](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/license-and-trademarks.md): KiloCenter Community Edition license — AGPL-3.0-or-later with network-use clause — and trademark notices.
- [Getting Started](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started.md): Get started with KiloCenter — install dependencies, generate certs, configure runtime, run the stack.
- [Architecture and Components](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/architecture-and-components.md): KiloCenter architecture — four services (KC-Core, KC-Identity, KC-Gateway, KC-Web) plus infrastructure.
- [Prerequisites](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/prerequisites.md): KiloCenter prerequisites — Docker, Docker Compose, Git, and optional toolchains (Go, Bun) for install or build.
- [Installation: Docker Compose](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/installation-docker-compose.md): Install KiloCenter with Docker Compose — start the four-service MIOTY stack including KC-Web, no host toolchain.
- [Installation: Linux Host](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/installation-linux-host.md): Install KiloCenter on a Linux host without Docker — PostgreSQL, Redis, Mosquitto, TLS certs, and the four KC services.
- [Installation: Local VM and Automation](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/installation-local-vm-and-automation.md): Run KiloCenter in a local VM with automated provisioning — repeatable setup for testing and team onboarding via Docker.
- [Configuration Basics](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/configuration-basics.md): KiloCenter configuration files and baseline settings — config.docker.yaml, KC-Core, KC-Gateway, port mappings.
- [Installation: Kubernetes (Helm)](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/getting-started/installation-kubernetes-helm.md): Deploy KiloCenter to Kubernetes with Helm — chart, prerequisites (k8s 1.25+, PostgreSQL 14+, Redis 7+), and ingress.
- [Onboarding](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/onboarding.md): KiloCenter onboarding — connect MIOTY base stations, register endpoints, verify first uplink and downlink.
- [Connect a Base Station](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/onboarding/connect-a-base-station.md): Connect a MIOTY base station to KiloCenter — BSSCI on port 5000, server CA certificate, and KC-Web creation steps.
- [Register an Endpoint](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/onboarding/register-an-endpoint.md): Register a MIOTY endpoint in KiloCenter — required fields (EUI, network key, profile) and how a base station attaches.
- [Verify the First Uplink](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/onboarding/verify-the-first-uplink.md): Verify the first MIOTY uplink in KiloCenter — confirm data from endpoint through base station to KC-Web.
- [Verify the First Downlink](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/onboarding/verify-the-first-downlink.md): Send and verify the first MIOTY downlink in KiloCenter — queue a command to a bidirectional endpoint, confirm delivery.
- [Integrations](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations.md): KiloCenter integrations — connect external apps to the MIOTY service center via gRPC API and MQTT, with examples.
- [gRPC First Steps](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/grpc-first-steps.md): First steps with the KiloCenter gRPC API — verify local connectivity to KC-Core port 9090 with grpcurl, list services.
- [MQTT First Steps](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/mqtt-first-steps.md): First steps with KiloCenter MQTT — enable the disabled-by-default broker, subscribe to events, publish downlinks.
- [LLM-Assisted Development](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/llm-assisted-development.md): Use KiloCenter with LLM coding assistants — llms.txt and llms-full.txt summaries for ChatGPT, Claude, Copilot, Cursor.
- [API Reference](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/api-reference.md): KiloCenter gRPC API reference — Protocol Buffer definitions for base stations, endpoints, with online portal.
- [Go Examples](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/api-reference/go-examples.md): Runnable Go examples for the KiloCenter gRPC API — generate stubs with buf, authenticate, and call uplink methods.
- [Python Examples](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/api-reference/python-examples.md): Runnable Python examples for the KiloCenter gRPC API — install grpcio, generate stubs, and call uplink methods.
- [JavaScript Examples](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/api-reference/javascript-examples.md): Runnable Node.js examples for the KiloCenter gRPC API — install @grpc/grpc-js with dynamic proto loading, call methods.
- [C# Examples](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/integrations/api-reference/c-examples.md): Runnable C# examples for the KiloCenter gRPC API — create console project, add Grpc.Net.Client, call methods.
- [Security](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/security.md): KiloCenter security — TLS certificate generation, default credential rotation, MQTT auth, and access controls.
- [Security Basics](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/security/security-basics.md): KiloCenter security basics — default credentials to change, TLS cert paths, and minimum hardening for shared deploys.
- [Operations](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/operations.md): KiloCenter operations — health checks, monitoring, log inspection, and recipes for keeping MIOTY service running.
- [Operations and Troubleshooting](https://docs.kiloiot.io/kilo-center/kilo-mioty-service-center/operations/operations-and-troubleshooting.md): KiloCenter operations — health endpoints for KC-Core, KC-Gateway, KC-Identity, common startup issues, diagnostics.


---

# 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/kilo-center/kilo-mioty-service-center.md?ask=<question>&goal=<endgoal>
```

`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.
