# Our story

CodeThreat began as a passion project focused on meeting industry standards and delivering real business value. Our journey started with a small, self-funded team aiming to transform application security. We officially launched our team and products in early 2023.

Initially, we concentrated on evaluating existing AppSec programs to understand the value they provided to users. This led to the creation of projects like [FlowBlot.net](https://github.com/CodeThreat/FlowBlot.NET), which laid the foundation for our future efforts. We started as a research team, emphasizing benchmarks and critical thinking, which has become a core part of our identity.

As a team that began with a research focus, we developed unique approaches to program analysis and AppSec programs. Our initial efforts in dataflow and taint analysis outputs marked the beginning of our scanner development. We spent a significant amount of time refining our tools before transitioning into a product phase. The early stages of our program analysis framework, now known as ShiftQL, were rigorously tested in various early test beds over extended periods.

> Over time, we have evolved into a team that is dedicated to understanding how industry changes affect end-users. We continually measure and analyze these impacts, aiming to solve the core problems faced by our target audience.

#### We prefer a startup approach with constant iterations and data-driven decisions, but

> In extreme, uncertain, and chaotic moments, we embrace the disorder, diving into it and leveraging the uncertainty to create innovative and risky implementations of new technologies that have never been attempted before.

**Evaluating Challenges and Recognizing Achievements**

> We pause to evaluate our successes and failures. We recognize that mistakes are part of our journey, and we find value in learning from them. Our approach is to analyze these instances from the ground up, focusing on finding solutions rather than making excuses. This reflective process ensures continuous improvement and innovation in our workflows and solutions.

The purpose of this handbook is to document and maintain the essence of our practices and solutions. Whether our team consists of five or ten people, we believe the solutions we implement go beyond products. They represent significant team efforts. This handbook ensures that both new and current team members can understand and contribute to our transparent workflows, maintain our systems, and most importantly, continue to provide value to our users efficiently.

<figure><img src="/files/Uel7B3zfgQfxWtpXsxt9" alt=""><figcaption><p>100k message in our discord  </p></figcaption></figure>

| Year | State                | Detail                                                                                  |
| ---- | -------------------- | --------------------------------------------------------------------------------------- |
| 2020 | Pre-Alpha            | SAST Scanner Initial Version                                                            |
| 2021 | Alpha                | C# Language Fully Supported. Only CLI. Closed Alpha Tests                               |
| 2022 | Pre-Beta Closed Test | Early Adopter CLI Tests. More Language Supports                                         |
| 2023 | Beta                 | Full-Fledged AppSec Platform and Cloud Beta Release                                     |
| 2024 | Stable Release       | AI Features, more language supports, Better analyzers such as SCA, License Scanner etc. |


---

# 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://codethreat-sast.gitbook.io/codethreat-company-handbook/handbook/our-story.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.