Sentora's Front-to-Back Risk Infrastructure for Vault Curation
Sentora's Front-to-Back Risk Infrastructure for Vault Curation
From Diligence to Live Controls
From Diligence to Live Controls
From Diligence to Live Controls
An operational blueprint for how Sentora turns due diligence, risk policy, and live monitoring into one governed control system for institutional vault curation.
An operational blueprint for how Sentora turns due diligence, risk policy, and live monitoring into one governed control system for institutional vault curation.
Inside This Report
Inside This Report
Why Vault Risk Is Continuous
Why Vault Risk Is Continuous
Understand why a vault that is sound at onboarding can change its risk profile after deployment. The report maps how parameter authority differs across Aave, Kamino, Euler, and Morpho, and why liquidity migration, oracle changes, and security events move faster than standard review cycles.
Understand why a vault that is sound at onboarding can change its risk profile after deployment. The report maps how parameter authority differs across Aave, Kamino, Euler, and Morpho, and why liquidity migration, oracle changes, and security events move faster than standard review cycles.
The Front-to-Back Risk Architecture
The Front-to-Back Risk Architecture
Walk through the five layers of Sentora's operating chain: DDQ diligence, risk framework policy, translation into controls, live monitoring, and governance closure. Each layer is documented with production evidence from the Sentora Risk Application, in operation since January 2026.
Walk through the five layers of Sentora's operating chain: DDQ diligence, risk framework policy, translation into controls, live monitoring, and governance closure. Each layer is documented with production evidence from the Sentora Risk Application, in operation since January 2026.
From DDQ Intake to Enforceable Controls
From DDQ Intake to Enforceable Controls
See how research intake becomes a governed decision record: evidence-driven dossiers, numbered review cycles, AI-assisted question generation under analyst ownership, and a decision gate that defines the approved universe. Approved policy then becomes allowlists, client mandates, LLTV settings, borrow caps, and risk trigger thresholds.
See how research intake becomes a governed decision record: evidence-driven dossiers, numbered review cycles, AI-assisted question generation under analyst ownership, and a decision gate that defines the approved universe. Approved policy then becomes allowlists, client mandates, LLTV settings, borrow caps, and risk trigger thresholds.
Live Monitoring, Alerting, and Escalation
Live Monitoring, Alerting, and Escalation
Examine the monitoring surface in production: scheduled daily risk jobs, collateral and cap utilization surveillance, 17 alert modules with 458 threshold keys, real-time security ingestion through Hypernative, and the Risk Radar analytics layer computing economic risk signals block by block across more than 40 protocols.
Examine the monitoring surface in production: scheduled daily risk jobs, collateral and cap utilization surveillance, 17 alert modules with 458 threshold keys, real-time security ingestion through Hypernative, and the Risk Radar analytics layer computing economic risk signals block by block across more than 40 protocols.
Why DeFi and Institutional Readers Need This Report
Why DeFi and Institutional Readers Need This Report
Onboarding Review Is Only the First Control
Onboarding Review Is Only the First Control
Protocol parameters shift after approval, collateral composition varies across markets, and liquidity can exit faster than a committee can convene. This report gives allocators, risk committees, and curators a concrete model for keeping the approved universe current and framework limits enforceable throughout deployment.
Protocol parameters shift after approval, collateral composition varies across markets, and liquidity can exit faster than a committee can convene. This report gives allocators, risk committees, and curators a concrete model for keeping the approved universe current and framework limits enforceable throughout deployment.
A Model Grounded in Production Evidence
A Model Grounded in Production Evidence
The report documents a system that operates in production today: 25 DDQ dossiers, 671 diligence questions, 18 protocol vault configurations, and 21,931 report files. Every layer of the architecture is backed by operating counts from a live system rather than a design proposal.
The report documents a system that operates in production today: 25 DDQ dossiers, 671 diligence questions, 18 protocol vault configurations, and 21,931 report files. Every layer of the architecture is backed by operating counts from a live system rather than a design proposal.
A Defined Path from Alert to Action
A Defined Path from Alert to Action
Detection has value only when it leads to documented response. The report sets out a full escalation map, from logged informational events to breach alerts with 24-hour incident reports and Risk Committee escalation, including direct protocol communication channels and PagerDuty-backed incident response.
Detection has value only when it leads to documented response. The report sets out a full escalation map, from logged informational events to breach alerts with 24-hour incident reports and Risk Committee escalation, including direct protocol communication channels and PagerDuty-backed incident response.
