> For the complete documentation index, see [llms.txt](https://docs.loci-dev.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loci-dev.net/welcome-to-loci/introduction.md).

# Introduction

### What is LOCI?

LOCI bridges this gap by modeling compiled binaries with real-world execution data, enabling it to:

* Predict performance impacts
* Detect degradations across software versions
* Identify power-hungry functions
* Optimize resource efficiency
* Provide test coverage references
* Enhance testing & validation

### The LOCI Ecosystem

LOCI is made up of several components that work together across your development and CI/CD workflow:

* **LOCI Inspector** — The execution-aware code dashboard. Visualize function-level performance metrics, explore call graphs, and compare versions to catch regressions before they reach production.
* **LOCI Insights** — Deep-dive report view for breaking down metrics by function and module. Sort, filter, and track trends over time.
* **GitHub Integration** — Automates binary analysis inside GitHub CI/CD. Uploads binaries on every PR and posts performance insights directly as PR comments.
* **Azure DevOps Integration** — The Azure Pipelines counterpart. Connects your pipeline to LOCI for upload-based analysis and PR-thread feedback.
* **LOCI CLI** — Terminal interface for manually uploading binaries and checking analysis progress without leaving your shell.
* **API / CI Quick Start** — HTTP-based access for uploading binaries, polling for results, and retrieving reports programmatically.
* **Self-Hosted Deployment** — Run LOCI inside your own AWS account using `loci-box` and the bootstrapper Docker image.

### Supported Uploads:

* Upload ELF/binaries as a ZIP or TAR archive.
* Files must include symbol information for accurate results.
* ELF/binaries can be compiled from C, C++, or Go Lang.

### Supported Architectures:

* ARMv8 64-bit (Timing reference based on ARM Cortex-A53 processor)
* Aurix TriCore processors (Timing reference based on Aurix TC399 processor)
* ARM Cortex-M4 (Timing reference based on ARM Cortex-M4 processor)


---

# 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.loci-dev.net/welcome-to-loci/introduction.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.