Snowflake Financial Services San Francisco, California

Mercury

Real-time Analytics

replicate the company’s critical operational database into Snowflake fast enough to support trusted analytics, product decisions, and risk use cases without overloading production systems.

0 Replication incidents since the migration
1-3 Minutes of data latency to Snowflake, down from 30-60+ minutes
~2 Days to resync database, down from a week previously
~20 Hours per month of data engineering maintenance and firefighting removed

Reported impact

Business outcome

Mercury reduced data latency to one to three minutes, eliminated replication incidents after migration, cut full resync time from more than a week to about two days, and removed about 20 hours of monthly data-engineering firefighting.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Mercury uses Snowflake and Snowflake Openflow on Snowflake to replicate the company’s critical operational database into snowflake fast enough to support trusted analytics, product decisions, and risk use cases without overloading production systems. Mercury’s full operational database, the same system that runs its app, is continuously replicated into Snowflake rather than copied in slower batch windows. Snowflake Openflow handles the ongoing replication and snapshot sync process, and Mercury supplements it with internal observability so engineers can inspect pipelines and resolve issues without vendor hand-holding. Analysts, data scientists, and product teams consume the fresh data for fraud detection, product launch reporting, near-real-time ML inference, and new customer-facing features. Keeping ingestion, storage, transformation, and governed access on one platform reduces handoffs, improves concurrency, and makes it easier to reuse trusted data across teams and applications....

Data flow

the operational application database and replica snapshots flow into Snowflake and Snowflake Openflow; curated data and model outputs are then served to analysts, data scientists, product teams, and risk workflows.

Solution architecture

2 components · 2 layers
  1. Ingest
    • Snowflake Openflow Continuously replicates operational data into Snowflake using managed data flows.
  2. Storage
    • Snowflake Provides the centralized data platform that stores governed datasets and serves analytics or AI workloads.

Architecture clues

  • Openflow is Snowflake’s managed integration service built on Apache NiFi.
  • Team built an internal agent to monitor syncs directly through Openflow.
  • Uses a read replica for snapshot syncs to avoid extra production load.

Evidence from the source

A full database resync that used to take over a week now runs in about two days with Openflow
Data that should have loaded in minutes took up to two hours or simply failed to appear
I don’t think we’ve had it happen once
Snowflake Openflow continuously loads Mercury’s full operational database
Transparency Evidence & methodology 100/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Snowflake

    Mercury customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/mercury/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Oct 8, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 9, 2026 · Snowflake · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.