Acquiring Magic Data
to build Trivinna in months
Production-ready agentic AI infrastructure that lets the CRE intelligence layer get built in months rather than years.
Trimont has the data, the clients, the relationships, and the brand to own the CRE intelligence layer of this market. What it needs now is the agent infrastructure to deliver that intelligence reliably, at scale, within the compliance constraints that institutional clients require. Magic Data is production-ready agentic AI: self-hostable, bring-your-own-model, schema-adaptive, observability-equipped, and proven at the data complexity Trimont operates at. Acquiring it does not buy a finished CRE product — it buys the foundation on which Trivinna's platform gets built in months rather than years, with access to an engineering team that knows exactly how it works.
01 The Case
Acquisition Thesis
Speed to Market
Trivinna is building the right product. The risk is time. Competitors — Smart Capital Center, Uptiq, MightyBot, Capitalize.io — are already live and signing institutional clients. Enterprise AI agent builds average 18–36 months and fail more than 70% of the time, because the infrastructure layer (orchestration, observability, schema management, model routing, audit trails) must be solved before any CRE-specific work begins.12345
Magic Data has already solved that layer. Trivinna's engineers start on day one building what only Trimont can: the CRE intelligence on top. The infrastructure that ships with the acquisition:
- Production-ready 24/7 agent infrastructure — orchestration, scheduling, and recovery already running continuously, not a prototype that needs hardening for production.
- Bring-your-own-model with monitoring and reporting — route to any model, with a full audit trail governance built in for institutional review.89
- Self-hostable deployment stack — the full stack runs inside Trimont or the customer's own VPC with no external data transfer, resolving the GLBA and counterparty data-residency exposure that most AI vendors can't.10
- Existing data-system integrations — connectors and semantic discovery already wired into the kinds of databases, warehouses, and loan systems Trimont's customers run, so onboarding new sources is likely configuration, not engineering.
The Data Environment Is a Precise Match
The Wells Fargo integration folded eight proprietary systems into Trimont's stack — thousands of tables, inconsistent schemas, new loans boarding continuously. This is exactly where generic AI tools break. Magic Data's semantic discovery engine maps entity relationships autonomously across hundreds of tables, no manual documentation required. The complexity describes both Trimont and their customers' environments today.67
Document Intelligence: A Near-Term Extension
CRE servicing runs on documents — rent rolls, operating statements, appraisals, insurance certificates, loan agreements — the raw material of every watchlist decision. The integration path for ingesting unstructured documents is short: the agent infrastructure and model routing already exist, so adding PDF and spreadsheet parsing is integrating proven OCR and extraction tooling, not a rebuild. Once live, the agents that monitor structured loan data extend straight to the borrower deliverables that trigger decisions — closing the loop from document receipt to covenant analysis.
02 Engineering Moat
What Is Non-Trivial to Rebuild
Beyond time-to-market, several components of Magic Data represent specialized engineering that is expensive to replicate correctly:
Agent memory
Persistent data context across continuous sessions, enabling agents to track loan-level anomalies over time without being re-prompted.
Thought-tree execution
Structured multi-step reasoning chains before acting, critical for financial data where single-pass outputs carry hallucination risk.
Schema-adaptive execution
Agents that do not break when underlying data systems are modified or new loan platforms are onboarded.
Observability infrastructure
Full reasoning-cycle audit logs traceable for regulatory review, built in rather than bolted on.
8
These are months of specialized infrastructure work with no client-facing differentiation. Magic Data ships them on day one.
03 The Comparison
With vs. Without Magic Data
|
Without Magic Data |
With Magic Data |
| Time to production agents |
18–36 months4 |
6–9 months |
| Engineering focus |
Infrastructure (orchestration, observability, schema management) |
CRE domain intelligence — covenants, watchlists, asset reports |
| Compliance deployment |
Third-party cloud risk review for each client |
Self-hosted VPC, resolved on acquisition |
| Data complexity handling |
Standard tools degrade past ~50 tables |
Proven at 500+ tables, 35+ sources |
| Document handling |
Build OCR + extraction pipeline from scratch |
Near-term extension on existing model routing layer |
| Model governance |
Build from scratch |
BYOM + audit trail, path to SR 11-7 compatibility 89 |
| Competitive timing |
Enter a crowded market |
Lead it |
04 Under the Hood
Technology & AI Infrastructure
The platform is a single self-hostable stack: a TLS ingress fronts four application services, backed by shared data services and a swappable model layer, connecting directly to existing customer systems.
Ingress
Nginx + TLS
Single secured entry point
App Services
Resources · Analyst · Utility · Workflows
Governance, AI analysis, code execution, automation
Data Layer
PostgreSQL · Redis · ChromaDB · S3
Operational, queue, vector & object storage
Model Layer
Selectable LLM
Self-hosted GPT-OSS:120b · frontier · or customer model
Customer Systems
DBs · Warehouses · Loan Systems
Connects directly — no migration
The entire stack runs via Docker Compose on one private network — fully self-hostable inside a customer's VPC, with no external cloud dependency required.
The hard part — the AI infrastructure
Wiring a model into an app is the easy 10%. The remaining 90% — running agents reliably, safely, and accountably in production — is what is already built and operating here.
Agent Orchestration
Analysis is split into independent runtime roles — an API surface, async execution workers, and a scheduler — so interactive traffic, long-running jobs, and recurring automation scale and operate separately. This is the orchestration layer most teams spend a year building.
api · worker · beat
24/7 Always-On Infrastructure
The scheduler and worker pool let agents run as autonomous monitoring, not just request-response. Covenant checks, watchlist scans, and recurring reports execute on a schedule and trigger downstream alerts — the system works while no one is watching.
scheduled · event-driven
Sandboxed Code Execution
A dedicated execution engine runs generated code and queries against customer databases and warehouses in an isolated runner, then reports results back into platform storage. Agents can compute, profile, and transform real data safely — without exposing the data tier directly.
isolated runner
BYOM Profiles + Audit Trail
Model endpoints are deployment-selectable — self-hosted, frontier, or customer-managed — with sessions, runs, and outputs persisted as audit-friendly state in PostgreSQL. The result is a path to governed, SR 11-7-compatibilityfor regulated institutional clients.
governed · auditable
Task-Level Model Routing
No single model handles everything. Planning, generation, and repair steps can each route to different models — letting governance-sensitive deployments standardize on an approved path while cost-sensitive ones tune spend, speed, and quality per task.
multi-model
Governed Context & Retrieval
Discovery jobs profile schemas and generate documentation, ERDs, and semantic context indexed in a vector store. Agents reason over governed, team-scoped context — not raw tables — which is what keeps analysis accurate past the complexity where generic tools break.
vector-indexed
The founding team is full of experienced senior engineering talent. It has working knowledge of the hardest architectural problems in production agentic AI — agent memory, non-deterministic execution, multi-model routing, observability at scale — earned through building and operating the system, not designing it on paper. Acquiring Magic Data gives Trivinna a first mover advantage to acquiring the talent, and it accelerates Trivinna's build in ways that cannot be replicated by hiring individual engineers into a greenfield project.
Backgrounds span
and more...
06 The Decision
Why Not Just Partner
A licensing agreement fails on three dimensions. It does not give Trimont data residency control — client data still routes through a vendor's cloud. It does not allow Trivinna to own and customize the intelligence layer in a way that creates defensible differentiation. And it does not transfer the engineering team's institutional knowledge of the architecture — the difference between a system that holds up under institutional client scrutiny and one that does not.1112
Acquiring Magic Data makes the infrastructure proprietary. It takes the replication option off the table for competitors. And it gives Trimont's growing AI team a foundation to build on from day one.
- Capitalize Unveils First AI Agents in Commercial Real EstateCapitalize launches first AI agents for CRE finance, helping 250+ firms tackle the $3T debt wave by maturity.
- AI for CRE Lending — UptiqAI platform for commercial real estate lending: property underwriting, rent roll analysis, credit memos.
- Commercial Lending Automation with AI Agents — MightyBotMightyBot automates commercial lending workflows including underwriting, draw reviews, covenant monitoring.
- Build vs Buy AI for Lenders: Complete 2025 ROI GuideLenders that buy solutions see 90% success vs. 30% building in-house.
- Smart Capital Center's CEO to Trimont: AI will determine the winners and losers in CREHow AI is redefining CRE servicing and asset management.
- Scale in a Volatile Market — Trimont (PDF)Trimont keynote, PERE Credit, Apr/May 2026.
- How to Create a Data Catalog in Minutes with Magic DataThe AI platform for data engineers — ingest, transform, automate, and report on data from any source.
- Beyond Build vs. Buy: How LLMs Are Reshaping Tech DecisionsTechnology decisions in financial services enterprises.
- AI Agents for Private CRE Lending in 2026 — GraphlineWhere AI agents fit in private CRE lending, how to measure ROI, and which capabilities matter.
- Self-Hosted AI Agent Platform You OwnYou own the source code, the runtime, the model, and the data inside.
- Build vs. Buy AI Agents: Lessons from 1,000 CompaniesDust shares insights from deploying AI agents across 1,000+ enterprises.
- Stanford AI Index 2026: AI Agents 66% Success, CRE ImpactAI agents jumped from 12% to 66% on real computer tasks but 89% never reach production.