TPRM Software for the AI Age
TPRM software that handles complex workflows, multi-party assessments, and custom scoring without requiring professional services or technical expertise
Feature Comparison
| Fluvial Feature | Generic TPRM | Fluvial |
|---|---|---|
| Basic Surveys | ✅ | ✅ |
| Full API Exposure | ❓ | ✅ |
| Hierarchical Weighting | ❓ | ✅ |
| Pairwise Comparison Scoring | ❓ | ✅ |
| User Customised Workflow | ❓ | ✅ |
| Per-project Workflow | ❓ | ✅ |
| LLM Backed Pairwise Comparison | ❓ | ✅ |
| GraphQL Data Querying | ❓ | ✅ |
| Agentic AI with MCP Server | ❓ | ✅ |
| CEL Access Policies | ❓ | ✅ |
| On Premises (Docker) Deployment | ❓ | ✅ |
The Waterbed Theory of Complexity
Complexity is an inevitable feature of mature business software. Different software architectures can reduce complexity in one area, only to find it popping up somewhere else.
Fluvial knowingly pushes complexity onto the user, providing great levels of process and data processing customisation. Until recently, this would demand extensive training, documentation and probably a consulting integration business.
AI changes this assumption. Agentic AI can make API calls on behalf of the user. AI Chat can write expression language policies to change the system’s behaviour. RAG assisted features can automate data processing.
Read our blog post for a fuller discussion of what happens when the computer stops being the bottleneck.
Data Flow Meets Workflow
Fluvial supports an end-to-end data flow which corresponds to many research-orientated processes - TPRM, Risk Ratings, Due Diligence, Vendor Selection. Most organisations use multiple tools to support this process, adding complexity, expense and a risk of errors.
flowchart TD
surveys[Surveys] --> |Publish| respondentA
surveys --> |Publish| respondentB
respondentA(Respondent A):::external submitA@--> |Submit| aggregate[Analysis]
submitA@{ animate: true }
respondentB(Respondent B):::external submitB@--> |Submit| aggregate
submitB@{ animate: true }
dataFeeds(Data Feeds):::external pullFeeds@--> |Pull| mappings
pullFeeds@{ animate: true }
aggregate --> mappings[Mappings]
mappings --> documents[Data Documents]
documents generatePdf@-->|Generate| pdf(Risk Rating PDF):::external
generatePdf@{ animate: true }
documents updateProfile@-->|Update| profile(Vendor Profile):::external
updateProfile@{ animate: true}
documents webhook@-->|Webhooks| integrations(External Integrations):::external
webhook@{ animate: true }
classDef external fill:#d3dfe3,stroke:#3d545c,stroke-width:2px
Fluvial supports each step of the process and ensures that data flows smoothly from one to the next.
1. Build Surveys
Build rich questionnaires and issue to respondents.
2. Analysis - Weighting and Scoring
Use hierarchical sections, tags, multiple weighting sets, multiple scoring sets, pairwise comparison and llm-assistance to produce the deepest and most justifiable assessment of responses.
3. Mappings
Fluvial Mappings merge input from respondent’s data, analysis, scores and data from external data sources. These data points are then mapped to fields in Fluvial Data Documents.
4. Data Documents
Data documents power Fluvial’s “headless CMS” functionality. These are structured documents that aggregate the data from the previous steps. Reports of any type (Dashboards, Web pages, PDFs) can then be generated in batch or on demand.
Workflow & Automation
Questionnaire and Data Documents can be linked to custom workflows in order to model any business process or regulatory framework. Arbitrary statuses can be assigned and linked to permissions to control access and functionality. Triggers can be set to call external or Fluvial API endpoints on transition. Custom guard policies can be applied to any step.