Our Mission
To become the standard protection layer for on-chain finance.
Aquarius exists to solve one problem: on-chain finance has no protection layer.
TradFi has circuit breakers, margin call systems, risk desks, and compliance-aware escalation. DeFi has nothing equivalent. When positions approach liquidation, users are on their own — watching dashboards, scrambling for gas, and hoping they react in time.
This is not a tooling gap. It is an infrastructure gap.
If traditional finance comes on-chain — and it is — three things must be true:
Aquarius is the system that makes these three things true.
Aquarius is not a bot. It is not a dashboard. It is not a monitoring tool.
It is financial protection infrastructure — a composable layer that sits between protocol state and execution infrastructure, providing the risk intelligence that makes automated protection possible.
| Aquarius Is | Aquarius Is Not |
|---|---|
| Infrastructure layer | Point solution |
| Protocol-aware risk engine | Generic alert system |
| Deterministic escalation pipeline | Heuristic-based bot |
| Non-custodial execution framework | Custodial fund manager |
| Chainlink CRE extension | Chainlink competitor |
Every design decision prioritizes safety. If a feature weakens security assumptions, it does not ship. If uncertain between two approaches, we choose the safer option.
The primary surface of Aquarius is its API. The web interface is a consumer of that API — never the other way around. This ensures composability with any integration pattern: bots, DAOs, institutional dashboards, or protocol-native UIs.
Each protocol adapter is a bounded context with its own types, risk models, and chain bindings. Protocol-specific logic never leaks across boundaries. Adding a new protocol does not require modifying existing ones.
The core risk engine and escalation pipeline are fully deterministic. An optional LLM reasoning layer provides additional context but is never allowed to block or override the deterministic path.