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

# Introduction

Welcome to the Inspector developer documentation.

Inspector is a **Code Execution Monitoring** tool that helps software developers to identify bugs and bottlenecks in their application automatically. Before users stumble onto the problem. 

Installing our library you will be able to visualize what your application is doing on every execution cycle, and identify unexpected behavior at a glance.

![](https://2873457055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ51SrLj6qvIRejC1XD%2Fuploads%2FHbZQw8pATi2zTR3ykWK3%2FHome.png?alt=media\&token=5939203c-aea5-484f-807d-82c9a1d369d6)

This documentation will help you to start working with Inspector in just a few minutes, as well as support if you get stuck.

Below are the supported technologies. Choose the one your application is built with.

### Supported Platforms

{% content-ref url="/pages/-LuWcB8gWM5wptHOWiEF" %}
[Laravel](/guides/laravel.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MbG50kVKWT\_dmhrNUpX" %}
[Symfony](/guides/symfony.md)
{% endcontent-ref %}

{% content-ref url="/pages/GqQIK9NcYrhKhzY5acoB" %}
[CodeIgniter](/guides/codeigniter.md)
{% endcontent-ref %}

{% content-ref url="/pages/u2aisXfoYkJFTHoQsOcI" %}
[Broken mention](broken://pages/u2aisXfoYkJFTHoQsOcI)
{% endcontent-ref %}

{% content-ref url="/pages/-LuWUZySI5nmGZTcqyyK" %}
[PHP](/guides/raw-php.md)
{% endcontent-ref %}

{% content-ref url="/pages/sFz09Y2ifm3lLFM7iSEA" %}
[Slim](/guides/slim.md)
{% endcontent-ref %}

{% content-ref url="/pages/uqOsMUhOjGdNXKmHEtnE" %}
[Neuron AI](/guides/neuron-ai.md)
{% endcontent-ref %}

### Security and compliance

Inspector is committed to deliver a powerful and easy-to-use monitoring platform while keeping your data secure. The security of our systems is of the utmost importance and we consistently aim to improve our security posture by building it into every layer of our products.

#### Encryption of data

Inspector datastores and their client communications are encrypted throughout the Inspector platform both in transit and at rest.

#### At rest

Our storage and analysis infrastructure is not accessible from the public internet and data are encrypted at the sotrage level. This helps mitigate the risk of unintentional or malicious access to user data.

#### In transit

All connections with Inspector API are secured by an industry-standard 256-bit HTTPS Encryption.

### Performance

Inspector is designed to be completely transparent from your users point of view. It collects and sends data to our inspection API asynchronuosly. This means that it doesn't introduce any latency in your code execution. 

### Contacts

* Email: <support@inspector.dev>
* Website: <https://www.inspector.dev>
* Blog: <https://www.inspector.dev/blog>
* GitHub organization: <https://github.com/inspector-apm>


---

# 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.inspector.dev/concepts/master.md?ask=<question>&goal=<user_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.