Confidential client, name withheld under NDA

Bacancy Technology Built Insurance Data Lakehouse on AWS for Reinsurance Firm the client

Quick answer: An AWS data lakehouse lands every cedent file raw in Amazon S3, maps it into one curated model and keeps lineage on every figure. Bacancy Technology built it for a UK reinsurance firm, so actuaries and pricing teams query one source.

Outcomes deliveredDelivered February 2025 to July 2025 by a team of 5
6 weeks

Manual data wrangling removed per cycle

Curated data ready to query on landing

100%

Curated figures traceable to source

Lineage back to the cedent file

10+

Treaty years queryable at once

No restoring archived data

0

Private data copies left

All teams query 1 curated lakehouse

Client name withheld under NDA. To honour our non-disclosure agreement and compliance obligations, we describe this client by industry and region only. The project scope, technology and outcomes are shared without details that could identify them.

About the Client

The client is a UK reinsurance firm whose pricing and accumulation work depends on data from its cedents, the insurers that pass risk to it. Each cedent sent bordereaux, claims extracts and exposure files in its own layout. Teams spent weeks shaping data by hand before any treaty could be priced.

Bacancy Technology built a data lakehouse on AWS that holds every cedent file, cleans it once and serves one curated model. Actuaries, pricing teams and BI dashboards now query the same source, with 100% of curated figures traceable to the original file.

Client type
Reinsurance firm
Industry
Insurance
Location
UK
Team
5 resources
Timeline
February 2025 to July 2025
Project size
Non-disclosable

Four data problems slowing treaty pricing

Scattered cedent files, private copies and archived history made every pricing and reporting cycle slow and hard to defend.

Dozens of cedent formats

What was happening

Bordereaux, claims extracts and exposure files arrived in a different shape from every cedent.

Business Impact: Weeks of manual wrangling came before any analysis could start.

Numbers drifted between teams

What was happening

Actuaries and pricing teams each pulled and reshaped their own copy of the data.

Business Impact: Reconciling two reports often took longer than producing them.

Older treaty years went dark

What was happening

The old warehouse could not hold the volume, so older treaty years were archived off.

Business Impact: Multi-year exposure questions waited on data restores.

Hard to prove data lineage

What was happening

Copies and manual edits made it hard to trace figures back to their source.

Business Impact: Every regulatory and rating agency cycle became a scramble.

Challenges & Solutions

Our engineers solved each problem as one layer of a single AWS data lakehouse.

Challenge 1: Landing cedent data from dozens of sources

Every cedent formatted bordereaux, claims and exposure files its own way.

Solution: Our AWS developers made Amazon S3 the single landing zone for every cedent file. AWS Glue catalogues each file on arrival so it can be queried at once, and the raw original is never changed.

Challenge 2: Giving every team the same clean data

Actuaries and pricing teams kept private copies, so their numbers drifted apart.

Solution: Our data engineers built a curated layer with PySpark and Apache Iceberg that maps every cedent file into one shared model. Claims link to the right treaties and exposure lines up across years.

Challenge 3: Keeping treaty history queryable

Older treaty years were archived off and had to be restored before multi-year analysis.

Solution: Our team kept full history in the lakehouse instead of archiving it. Actuaries and pricing teams query the curated layer directly in Amazon Athena and Amazon Redshift, across 10+ treaty years at once.

Challenge 4: Proving where every number came from

Regulators and rating agencies expect figures that trace back to source, which copies and manual edits made hard.

Solution: Our engineers built governance in from the start with AWS Lake Formation. Every file keeps its lineage from landing, access is controlled by role, and any figure traces back to its original cedent file. This is what our insurance IT services are built on.

How the Platform Works

The client reinsurance data lakehouse dashboard

Core Features

  • S3 landing zone for raw cedent dataBordereaux, claims and exposure files land raw and stay untouched.
  • Curated cedent data modelEvery cedent mapped to one shared model for treaties, claims and exposure.
  • Direct query accessActuarial, pricing and BI teams query the same curated layer.
  • Built-in lineage and role accessEvery figure traces to its source file, with access controlled by role.
  • Full history retentionOlder treaty years stay queryable instead of being archived off.

The stack behind the lakehouse

Storage
Amazon S3 | Amazon S3 Glacier
Table format
Apache Iceberg
Cataloging and ETL
AWS Glue
Data processing
Python (PySpark) | Apache Spark
Query engine
Amazon Athena | Amazon Redshift
Governance and access
AWS Lake Formation
Business intelligence
Amazon QuickSight
Cloud
Amazon Web Services (AWS)

Ready to start?

2500+ projects delivered by Bacancy Technology

Get access to an experienced team of developers and engineers from Bacancy Technology, handpicked to ace your goals. Kickstart within 48 hours, no-risk trial.

Book A 30 Min Call
14+Years of business experience
1458+Happy customers
30+Countries with happy customers
1050+Agile-enabled employees

More Case Studies

View All Case Studies