How is iDBQuery used by asset managers?
Asset managers use iDBQuery to ask plain-language questions across portfolio, performance, risk and client data spread over many systems, getting cited answers in seconds without SQL. It builds one live model across sources and can run in your VPC or air-gapped, keeping proprietary positions and client data private.
Institutional asset managers pull data from portfolio-accounting systems, performance and risk tools, order-management exports and client reporting spreadsheets. iDBQuery unifies them into one live model and answers plain-language questions with each figure cited to its source.
Investment and operations teams ask:
- What is performance and tracking error by strategy versus benchmark this month?
- Show AUM and net flows by product, channel and client segment.
- Which portfolios are outside their mandate limits or risk bands?
- What management-fee revenue did we accrue versus bill by client?
- Compare exposure to a sector across every fund at once.
iDBQuery joins these without a pipeline, so a cross-fund question answers in one place, and the Analyst agent can investigate an open question, like what drove a performance gap, on its own and produce a shareable report for the investment committee.
Because positions and client data are proprietary and confidential, deployment leads: run in your own VPC or fully air-gapped, use the Embedded SDK or Desktop app to keep data local, and rely on query-in-place, RBAC and encryption. iDBQuery makes no certification claims; the differentiator is architectural, sensitive holdings and client records stay inside your walls while portfolio and ops teams get instant, verifiable answers.
Updated 2026-06-22