Nightly multi-source ingestion
Scheduled jobs that connect to SFTP sites, SharePoint document libraries, Azure file shares, websites, REST APIs and email attachments, land the raw files, and keep every version. Nobody downloads a CSV by hand again.
We build the Databricks pipelines that pull data in nightly from fund administrators, custodians, SharePoint libraries, Azure file shares, SFTP sites, websites and APIs; clean and validate it; calculate what the business needs; and serve it to Power BI, internal workbenches and platforms like Foundation. When a file is late or malformed, the right person knows before breakfast.
The unglamorous plumbing that decides whether your reports, your AI and your investors can trust a number. Built as Databricks Workflows and notebooks, with lineage, tests and alerts, by engineers who have done it for investment funds and reinsurers.
Scheduled jobs that connect to SFTP sites, SharePoint document libraries, Azure file shares, websites, REST APIs and email attachments, land the raw files, and keep every version. Nobody downloads a CSV by hand again.
Schema checks, reconciliations and business rules run on every load. When data doesn't arrive, arrives late, or arrives malformed, an alert goes out with what failed and what to do; the job retries on a schedule you set.
NAV calculations, positions and exposure roll-ups, reconciliations between administrator and custodian, fee and performance figures: coded, tested and versioned rather than living in a spreadsheet only one person can run.
Bronze, silver and gold layers in the lakehouse: positions, prices, NAV, counterparties, deals and documents joined into one model with lineage, ready for reporting, workbenches, Foundation and AI assistants.
A typical night
This is the shape of the platform we run for an ILS manager and a reinsurer today: raw files land overnight, Databricks jobs validate and transform them, exceptions raise alerts, and by the time the team arrives the gold tables are refreshed and every downstream tool is reading the same numbers.
The same pattern scales from a handful of feeds to dozens, and the same tables feed Power BI, internal workbenches, Foundation and an AI assistant that can answer questions against the lakehouse.
Power BI
Good data deserves reporting that keeps up with it. We have extended our Power BI practice with the latest AI agents, which lets us turn a requirements conversation into a working, well-structured report in days, and iterate on it in front of you.
Every report ships with row-level security designed in from the start, so a fund analyst, a client and an executive each see exactly the slice they are entitled to from the same dataset. And because we integrate Power BI with source code repositories, every change is versioned, reviewable and deployable the same way as the pipelines beneath it.
Reports and semantic models drafted with AI agents, then reviewed and tuned by an engineer who knows the data. Days, not weeks.
One report, many audiences. Security rules live in the model and are tested with the data, not bolted on afterwards.
Reports and models stored in Git alongside the Databricks code: pull requests, history, rollback and repeatable deployment.
Reports read the same gold tables as the workbenches and Foundation, so there is one version of every number.
We run platforms of this shape for an ILS manager and a reinsurer today, and the pattern applies anywhere a business depends on nightly data from administrators, custodians, brokers, cedants or vendors.
Administrator and custodian feeds reconciled nightly; NAV, positions and exposure calculated and served to investor reporting and portfolio tools.
How we work →Bordereaux, cedant statements, policy admin and payment data consolidated for real-time payment and reporting tracking.
How we work →If the month-end process starts with somebody downloading files, there is a platform like this waiting to be built, usually in weeks.
Talk to us →SFTP sites, SharePoint document libraries, Azure file shares, websites, REST APIs, email attachments and databases such as SQL Server, on a nightly or more frequent schedule.
Validation runs on every load. If data does not arrive, arrives late or fails schema or business-rule checks, an alert goes to the right people with what failed and what to do, and the job retries on your schedule.
Yes. NAV, positions and exposure roll-ups, administrator-to-custodian reconciliations and fee calculations are coded, tested and versioned in Databricks rather than living in a spreadsheet one person can run.
Reports and semantic models read the same gold tables as your workbenches. We build them with AI assistance, design row-level security in from the start, and keep them in source control alongside the pipelines.
The highest-value feed is typically ingested, validated and landed in the lakehouse with alerts live within the first week.
Thirty minutes with a data engineer who has built this for funds and reinsurers. You'll leave with a feed inventory template and a scoped first pipeline.