# Is it open source?

Sentinel3's code is split into its frontend code and backend algorithm. The frontend code, like all Chrome extensions published in the Chrome Store, is open source, which means anyone can access it, and it can't be obfuscated per the [**Chrome Store's policy**](https://developer.chrome.com/docs/webstore/review-process/#review-time-factors).

Sentinel3's backend code and algorithm is a proprietary, closed source code for two simple reasons:

1. If scammers learn how Sentinel3's algorithm detects scams, [**they will develop ways to circumvent them**](/kerberus/sentinel3/how-is-it-different/detects-scams-2-2.md), endangering our users.
2. Sentinel3 is the most powerful Web3 security solution, backed by 0 user losses and up to $30k of coverage. The algorithm and its engines are proprietary to protect our intellectual property.

At no point does Kerberus have control or access to your private keys.

{% hint style="info" %}
Would you give the world the keys to your house's alarm system? We wouldn't. That's why Sentinel3's backend source code is proprietary and closed source.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.kerberus.com/kerberus/sentinel3/is-it-open-source.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.