> For the complete documentation index, see [llms.txt](https://otomato-2.gitbook.io/otomato-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://otomato-2.gitbook.io/otomato-docs/introduction/why-otomato-exists.md).

# Why Otomato exists

#### The core problem in DeFi today

DeFi moves fast: borrowing rates spike overnight, new incentives launch everyday, point seasons end without notice, and protocols can be hacked while you sleep. Keeping a portfolio optimized has become a **full-time job**.

But the tools available today weren’t designed for that: dashboards are fundamentally passive. They require users to **constantly check** them just to confirm nothing has gone wrong.

They show information, they don’t surface what matters or when it matters. Users are expected to refresh, monitor, and manually piece things together across multiple apps and channels.

Information is also **fragmented**. Updates live on Twitter, Discord, Telegram, dashboards, etc. Even experienced users miss key events simply because they weren’t looking at the right screen at the right time.

{% hint style="info" %}
And even in a single channel, the signal-to-noise ratio is broken. Twitter doesn’t know the user’s positions, what they entered yesterday or exited two days ago, so it cannot prioritize the information that truly matters.
{% endhint %}

With everything scattered and nothing interpreting relevance, an intelligence gap forms: no system knows what a user holds or what matters to them right now.

**This is why DeFi needs an intelligence layer, and that’s exactly what Otomato provides.**