---
title: "Welcome to Flowsint"
description: "Complete documentation for Flowsint - a modular OSINT investigation platform."
category: "Overview"
order: 1
author: "Flowsint Team"
tags: ["documentation", "overview", "getting-started"]
version: "1.2.8"
last_updated_at: "2026-05-15"
---

### What is Flowsint?

Flowsint is a modular investigation and reconnaissance platform focused on OSINT (Open Source Intelligence). It provides:

- Graph-based visualization of entity relationships
- 30+ automated enrichers for intelligence gathering
- Modular architecture with clean separation of concerns
- Privacy-first design with local data storage
- Extensible platform for custom enrichers
- Automated search flows (more on that [here](/docs/getting-started/flows))

<Alert variant="warning">
    <AlertTitle>Disclaimer !</AlertTitle>
    <AlertDescription>
    The author(s) and contributor(s) of this tool assume no responsibility or liability for any damages, losses, or consequences that may result from the use or misuse of this software.
    By using this tool, you acknowledge and agree that:
        - You are solely responsible for your use of this software
        - You will use this tool in compliance with all applicable laws and regulations
        - You will obtain proper authorization before conducting any security testing or reconnaissance activities
        - You understand the potential risks and legal implications of using security tools
</AlertDescription>
  </Alert>

### Why Flowsint?

If you've already practiced some OSINT, you know that analysts often rely on a multitude of research tools: scripts, third-party services, specialized applications. But these tools often work **in silos** and quickly become obsolete if they're not maintained: a service disappears, an API changes, an access point closes. The analyst juggles with unstable tools and sometimes has to **manually adapt their data** to continue their investigation.

OSINT tools, for most, are **consumables**: they evolve, appear, and disappear. Research methods change, security mechanisms evolve. However, the fundamental need always remains the same: **to see, exploit, and analyze data in a clear and understandable way**. Analysts need to be able to list, centralize, and visualize connections to have a clear understanding of their investigation.

This is exactly what Flowsint was built for: a solid and durable foundation on which your investigations rest. Tools become simple extensions that plug in and unplug easily. A new tool comes out, and with a few manipulations it can be integrated into your investigation workflow.

**Flowsint is the stable infrastructure that allows you to stay agile in the face of constant evolution of methods and sources.**

Flowsint is a local tool, running on your machine only. This ensures a great level of confidentiality, but comes with responsabilities.

<Alert variant="warning">
    <AlertTitle>At your own risk</AlertTitle>
    <AlertDescription>
    All enrichers run locally on your machine. This means you can get banned from some services or get flagged from infrastructures if you start making thousands of requests to the same service.
    You need to always know what you are doing, and understand that gathering can go very fast in scale.

    For example, you can very easily happen to be making DNS resolution requests for 10 000 IPs.

    Know you infrastructure and your limits. Know how the tools used in the enrichers actually work. You can have a list of the available enrichers and tools [here](/docs/sources/available-enrichers).
</AlertDescription>
  </Alert>

If all those points are clear for you, let's start investigating !
