Snowflake Financial Services Marbella, Spain and New York, USA

RavenPack

Enterprise Knowledge Search · Real-time Analytics

Delivering multi-petabyte financial data to clients across regions and clouds through FTP and ETL pipelines was too slow, siloed, and expensive for RavenPack's growing analytics and AI business.

14x lower egress costs
15 regions
2 new data products launched
multiple petabytes of data

Reported impact

Business outcome

RavenPack launched new data products, cut global egress cost 14x, and gave investment professionals near-real-time access to financial intelligence through both direct sharing and agentic research workflows.

  • Cost Reduction
  • Revenue Growth
  • Scalability
  • Speed to Market

Solution

RavenPack standardized data delivery on Snowflake so client sharing, internal analytics, and AI products all run from one financial repository. Premium market, news, jobs, and alternative datasets are centralized in Snowflake on AWS, replacing fragmented regional pipelines and manual FTP delivery. Snowflake then feeds both direct client sharing and Bigdata.com, RavenPack’s financial research platform, where AI agents pull curated datasets to answer market questions. The same architecture also supports Annotations training datasets for customers building their own large language models. Because RavenPack already runs heavily on AWS, Bigdata.com agents can use AWS Bedrock for reasoning while pulling trusted data from Snowflake, and zero-ETL sharing keeps access fast for clients. Egress Cost Optimizer routes data across 15 regions without dataset duplication, giving RavenPack near-real-time distribution, simpler integration, and a lower-cost path from raw data to AI-ready insight.

Data flow

Multi-petabyte financial and alternative datasets land in Snowflake on AWS, where RavenPack publishes them directly to clients and to Bigdata.com. Bigdata.com agents use AWS Bedrock and Snowflake data together, while Snowflake sharing and Egress Cost Optimizer distribute the same source data across 15 regions at lower cost.

Solution architecture

4 components · 4 layers
  1. Compute
    • AWS Bedrock Provides model inference for Bigdata.com agents that use Snowflake data to answer financial research questions.
  2. Storage
    • Snowflake Acts as RavenPack's central repository for premium financial and alternative datasets that power sharing and AI products.
  3. Serving
    • Bigdata.com Serves financial research experiences and agents that draw governed datasets directly from Snowflake.
  4. Orchestration
    • Egress Cost Optimizer Routes shared data efficiently across regions so RavenPack can control global distribution cost.

Architecture clues

  • Bigdata.com agents are powered by AWS Bedrock but draw their data from Snowflake.
  • One data source is shared across 15 global regions with optimized egress routing.
  • Snowflake zero-ETL sharing replaces manual FTP and API-heavy delivery.

Evidence from the source

Already, that helps us reduce our costs 14-fold.
As soon as new data is processed, RavenPack's clients can access it instantly
Bigdata.com financial research agents are largely powered by AWS Bedrock, but can easily draw data from Snowflake
RavenPack relies on Snowflake to power a centralized data repository that drives both internal and external data sharing
with Snowflake zero-ETL data sharing, RavenPack can create more efficient data sharing pipelines
Transparency Evidence & methodology 90/100 reference value · 82% confidence · 2 sources

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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references 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

    RavenPack customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/ravenpack/
    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
  2. RavenPack

    Company | RavenPack

    First-party
    https://www.ravenpack.com/company/

    The company page states 'We are 200 team members'.

    Source type
    Official company website
    Supports
    • Company size

Date evidence

  • First archived Sep 1, 2025 · 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 Aug 3, 2026 · Snowflake · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.