> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adsumnetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Quick answers on cost, privacy, models, hardware, and how Adsum is built.

<AccordionGroup>
  <Accordion title="Is it free?">
    Yes. The extension itself is **free and open source** (Apache-2.0), now and always. On top of that, the [free tier](/free-tier) lets you start with no key, no account, and no card: it runs on a managed model out of the box. When you want a specific model or heavier usage, bring your own OpenAI-compatible key.
  </Accordion>

  <Accordion title="What data leaves my machine?">
    Your prompts and the context the agent needs go to whichever model provider you use. On the free tier that is our managed model; with your own key it is your provider. See [privacy and security](/privacy-and-security) for the full picture.
  </Accordion>

  <Accordion title="Which models can I use?">
    Any model on an OpenAI-compatible endpoint with strong native tool-calling. Start with Claude Haiku 4.5 (the benchmark model). See [Models](/models) for recommendations and exact settings.
  </Accordion>

  <Accordion title="Can I run it fully local or offline?">
    Yes, point it at a local OpenAI-compatible server such as Ollama or LM Studio. The model still needs solid tool-calling to drive hardware workflows.
  </Accordion>

  <Accordion title="Does it help with the EU Cyber Resilience Act (CRA)?">
    Yes. One click produces a readiness snapshot on nRF and ESP: an SBOM (SPDX), a secure-by-design posture check from your real config, and a fix loop to close a CVE you name. It is a **readiness aid, not a conformity assessment and not legal advice**, and the CVE flow is not a vulnerability scanner: it confirms a component you name is present in your build and helps you patch it, rather than searching for unknown CVEs. See [CRA readiness](/cra-readiness).
  </Accordion>

  <Accordion title="Which boards and SoCs are supported?">
    Nordic nRF52, nRF53, and nRF54 on nRF Connect SDK (Zephyr), and Espressif ESP32, ESP32-S3, and ESP32-C6 on ESP-IDF. BLE on both, Wi-Fi on ESP. More is on the [roadmap](/platforms-and-roadmap).
  </Accordion>

  <Accordion title="Do I need the vendor tools installed?">
    Yes. Adsum drives your existing toolchain: the nRF Connect Extension Pack for nRF, and an ESP-IDF install for ESP. See [getting started](/getting-started) for setup.
  </Accordion>

  <Accordion title="Was my code used to train it?">
    No. The expertise behind the agent is firmware knowledge authored and curated by engineers, not scraped from user projects. See [how it works](/architecture).
  </Accordion>

  <Accordion title="Is it affiliated with Nordic or Espressif?">
    No. Adsum IoT Coder is an independent open-source project. It works with their SDKs but is not endorsed by or affiliated with either company.
  </Accordion>

  <Accordion title="Where are the release notes?">
    In the [changelog on GitHub](https://github.com/adsumnetworks/Adsum-IoT-Coder/blob/main/CHANGELOG.md).
  </Accordion>
</AccordionGroup>