01, Financial Services AI Platforms
Databricks AI for Financial Services
What building and governing AI on Databricks actually looks like for wealth managers, banks, and insurers: portfolio analytics and advisor tooling, MCP-connected agents, and the model risk documentation SR 11-7 and SR 26-2 require.
Databricks financial services AI means building and governing machine learning and generative AI workloads for banks, wealth managers, and insurers on the Databricks Data Intelligence Platform: a unified lakehouse spanning data engineering, MLOps, and Mosaic AI agent tooling, layered with the model risk and compliance controls examiners expect under SR 11-7 and SR 26-2.
databricks ai financial
What Databricks AI for Financial Services Actually Means
Databricks financial services AI means building and governing machine learning and generative AI workloads for banks, wealth managers, and insurers on the Databricks Data Intelligence Platform: a unified lakehouse spanning data engineering, MLOps, and Mosaic AI agent tooling, layered with the model risk and compliance controls examiners expect under SR 11-7 and SR 26-2.
Databricks itself is infrastructure: Unity Catalog for data and AI governance, Delta Lake for the underlying storage layer, MLflow for experiment tracking and the model registry, and Mosaic AI for building, serving, and evaluating models and agents. None of that is finance-specific out of the box. It becomes financial services AI when the workloads running on top of it are wealth management personalization, credit and fraud models, treasury forecasting, or agentic workflows that touch account data.
Financial institutions gravitate to Databricks because a single platform can hold structured core-banking and portfolio data alongside unstructured content, such as advisor call notes, compliance filings, and client correspondence, under one lineage and access-control model. That matters more in a regulated environment than raw model accuracy, because an examiner or a model risk committee asking where a number came from needs a traceable answer, not a rebuilt pipeline assembled for the review.
The gap Kriv works in is what sits between a working Databricks deployment and an AI program a model risk committee or a bank examiner will actually accept: model inventory discipline, validation evidence for models that were not built the way traditional statistical models were, and a documented record of who, and what agent, can call which tool and dataset.
where wealth management
Where Wealth Management Firms Actually Use AI on Databricks
Wealth management firms running AI on Databricks tend to start in four places: portfolio and household-level analytics, advisor productivity tooling built on meeting and email content, suitability and KYC document extraction, and custodian data reconciliation using Delta Sharing. None of these require replacing the core portfolio accounting or CRM system Databricks sits alongside.
Portfolio and household analytics: combining custodian feeds, market data, and CRM records in Unity Catalog to surface next-best-action signals for advisors, model portfolio drift against target allocations, and household-level risk exposure across accounts that live in separate source systems.
Advisor productivity: using Mosaic AI to summarize client meetings, draft follow-up notes, and pull relevant portfolio context into a single advisor workspace, with every generated note traceable back to the source records it was built from rather than presented as an unattributed summary.
Suitability and KYC document extraction: turning scanned account applications, investment policy statements, and beneficiary forms into structured fields a compliance team can query and audit, instead of leaving that information locked inside PDFs and scanned images.
Custodian and clearing-firm reconciliation: Delta Sharing lets a firm receive custodian or clearing-firm data through a governed, open protocol rather than a proprietary point-to-point feed built separately for every counterparty, which matters for a wealth manager working across multiple custodians.
Kriv AI's Databricks wealth and portfolio accelerator packages the data model and access-control pattern behind the first two use cases, so the underlying Unity Catalog structure does not have to be designed from a blank page.
mcp powered financial
MCP-Powered Financial AI Workflows on Databricks
MCP, the Model Context Protocol Anthropic introduced in November 2024 as an open standard, gives an AI agent a governed way to call external tools and data sources instead of relying on a fixed set of hand-wired integrations. Databricks supports MCP by exposing Unity Catalog functions and Databricks Apps as callable tools inside its Mosaic AI agent framework.
In a financial workflow, that looks like an agent that, on a request from an advisor or an analyst, calls a Unity Catalog function to pull a client's current holdings, calls a second function to check a concentration or suitability rule, and drafts a summary, with each call logged against the same access controls that already govern direct table queries.
The practical shift MCP introduces is scope, not raw capability: an agent that previously only read from one approved dataset can now be connected to many tools at once, and can chain calls across them in a single request. That is useful for automating multi-step workflows, and it is also the reason MCP tool permissioning needs to be treated as seriously as data-table permissioning, not as a lighter-weight engineering configuration decided outside the model risk process.
Kriv AI treats MCP tool definitions as part of the model and agent risk inventory: each tool a financial services agent can call gets documented, scoped to the narrowest data access it actually needs, and put through the same validation and change-management process as a traditional model, rather than left as a configuration detail nobody outside the build team can see.
governance layer databricks
The Governance Layer Databricks Doesn't Ship With
Databricks provides the technical building blocks, an MLflow model registry, Unity Catalog lineage, and monitoring dashboards, but it does not provide a model risk management program. That program, and the documentation an examiner or a model risk committee expects to see, is separate work regulated financial institutions still have to build on top of the platform.
SR 11-7, issued by the Federal Reserve and the OCC in 2011, remains the foundational US framework for model risk management, built around effective challenge across three elements: model development, independent validation, and governance. Every model a bank runs on Databricks, including gradient-boosted risk scores and fine-tuned language models, is in scope for that framework when it informs a material business decision.
SR 26-2, the Federal Reserve's April 2026 letter revising the supervisory expectations first set out in SR 11-7, narrowed the formal definition of a model in ways that pull some generative and agentic tools outside strict SR 26-2 scope. That does not mean those tools go ungoverned; it means the obligation shifts to the institution's own risk framework and to guidance such as the NIST AI Risk Management Framework, rather than to a bright-line supervisory letter.
For wealth management and broker-dealer functions specifically, FINRA's Regulatory Notice 24-09 is explicit that existing supervisory, recordkeeping, and communications rules apply in full when a firm uses generative AI. There is no separate, lighter rulebook for an AI-assisted advisor workflow just because the output was drafted by a model.
In practice, the deliverable Kriv builds alongside a Databricks financial services implementation is a model and agent inventory that maps each system to SR 11-7 or SR 26-2 status, documents validation evidence appropriate to how it was built, whether that is a traditional statistical model, a fine-tuned LLM, or an MCP-connected agent, and sets a monitoring cadence a committee can actually review on a recurring schedule.
kriv ai databricks
What a Kriv AI Databricks Financial Services Engagement Includes
Engagements are scoped to the institution's actual Databricks footprint and regulatory posture rather than sold as a fixed package. Four phases recur across most of this work, in roughly this order.
1. Platform and workload assessment
Review of the current Databricks environment, Unity Catalog structure, MLflow registry contents, Mosaic AI agents in production or planned, against the financial workloads it actually supports, to establish what needs formal governance versus what is still exploratory.
2. Model and agent risk inventory
Every model, fine-tuned LLM, and MCP-connected agent is catalogued and mapped to SR 11-7 or SR 26-2 status, with gaps flagged against validation, documentation, and effective-challenge requirements.
3. Governance control implementation
Unity Catalog permissions, MCP tool allowlisting, and change-management workflows are built or tightened so access controls match the risk tier of each model and tool, instead of a single default applied everywhere.
4. Monitoring and audit readiness
Drift monitoring, a validation refresh cadence, and inventory documentation are set up so a model risk committee or examiner review starts from records that already exist, instead of ones assembled the week before the exam.
kriv ai s
Kriv AI's Rates for This Work
Rates depend on whether the work is platform and governance architecture, independent validation review, or fractional ongoing oversight of an existing Databricks AI program.
| Track | Hourly Rate | Typical Engagement | Minimum Engagement |
|---|---|---|---|
| Enterprise Databricks Governance | $200/hr floor | Model and agent inventory, SR 11-7/SR 26-2 gap mapping, control implementation | $8,000 |
| Advisory / Model Risk Review | $400-700/hr | Independent validation review, board or committee briefing | Scoped per engagement |
| Fractional Oversight | $300-400/hr | Ongoing monitoring, MCP tool governance, validation cadence management | Monthly retainer |
Sources
Cited sources
- SR 11-7, issued by the Federal Reserve and the OCC in 2011, remains the foundational US framework for model risk management, built around effective challenge across three elements: model development, independent validation, and governance.
- SR 26-2, the Federal Reserve's April 2026 letter revising the supervisory expectations first set out in SR 11-7, narrowed the formal definition of a model.
- the obligation shifts to the institution's own risk framework and to guidance such as the NIST AI Risk Management Framework
- Databricks Data Intelligence Platform: a unified lakehouse spanning data engineering, MLOps, and Mosaic AI agent tooling
- Databricks exposes Unity Catalog functions and Databricks Apps as MCP tools inside Mosaic AI
- FINRA's Regulatory Notice 24-09 is explicit that existing supervisory, recordkeeping, and communications rules apply in full when a firm uses generative AI
- MCP, the Model Context Protocol, is an open standard, introduced by Anthropic in November 2024
Straight answers
Frequently asked questions about Databricks AI for Financial Services
Does Databricks provide AI model risk management for financial services out of the box?
No. Databricks provides the platform, Unity Catalog for governance and lineage, MLflow for the model registry, Mosaic AI for building and serving models and agents, but it does not provide a model risk management program. Mapping models and agents to SR 11-7 or SR 26-2, documenting validation evidence, and setting a monitoring cadence is separate work that sits on top of the platform.
How do wealth management firms use AI on Databricks?
The most common starting points are portfolio and household-level analytics built from custodian and CRM data in Unity Catalog, advisor productivity tools that summarize client meetings and draft follow-ups, suitability and KYC document extraction, and custodian data reconciliation using Delta Sharing rather than point-to-point feeds.
What is an MCP-powered financial AI workflow?
MCP, the Model Context Protocol, is an open standard, introduced by Anthropic in November 2024, that lets an AI agent call external tools and data sources through a common interface instead of custom point-to-point integrations. Databricks exposes Unity Catalog functions and Databricks Apps as MCP tools inside Mosaic AI, so a financial agent can pull holdings data, check a compliance rule, and draft output in one governed sequence.
Does SR 26-2 apply to generative AI and MCP-connected agents built on Databricks?
SR 26-2, the Federal Reserve's April 2026 revision of SR 11-7, narrowed the formal definition of a model in ways that put some generative and agentic tools outside its strict scope. That does not remove the governance obligation; it shifts it to the institution's own risk framework and to guidance such as the NIST AI Risk Management Framework, and Kriv treats MCP tool access the same way it treats a model in the inventory regardless of formal SR 26-2 status.
What does Kriv AI do differently from Databricks's own professional services?
Databricks's own services teams build and tune the platform. Kriv's work is the governance layer around it: model and agent inventory mapped to SR 11-7 or SR 26-2 status, validation appropriate to how each model or agent was actually built, and MCP tool permissioning documented the same way a traditional model's access controls would be.
How much does a Databricks financial services AI governance engagement cost?
Enterprise Databricks governance engagements are priced at Kriv's standard enterprise hourly rate with a fixed minimum engagement size, shown in the rate table above. Independent model validation review and fractional ongoing oversight of an existing Databricks AI program are priced separately, based on scope and cadence rather than a fixed package price.
Do you work only with banks, or with wealth managers and insurers too?
All three. The Databricks patterns overlap heavily: Unity Catalog governance, MLflow validation, and MCP tool permissioning apply the same way whether the workload is a bank's credit model, a wealth manager's advisor tooling, or an insurer's underwriting or claims model.
Talk to the team that would do the work
Bring your requirements to a working session with the person who'll actually deliver.
Book a Discovery Call