Snowflake Financial Services Tel Aviv, Israel

Fireblocks

Real-time Analytics

Fireblocks needed to query billions of rows across 15 data domains, unify customer and internal analytics, and expose digital-asset insights securely without relying on manual analyst workflows or risking data leakage.

$10T transactions
15 unique domains
2 Full-time analysts’ worth of capacity saved per month with AI-powered efficiencies
2,000 analysis queries per month

Reported impact

Business outcome

Fireblocks now handles 40-50% of analysis queries through AI agents, saves the equivalent of two full-time analysts per month, gives customers secure self-service answers about wallets and assets, and strengthens retention with more personalized analytics.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth
  • Risk Reduction

Solution

Fireblocks rebuilt its analytics stack on Snowflake running on AWS so both internal teams and customers can query digital-asset data at scale without exposing one another's data. On-chain telemetry, wallet and asset activity, revenue data, Salesforce analytics, and Zendesk insights are loaded into Snowflake across 15 data domains to create one governed data foundation. On top of that foundation, the team built Fire Genie in a 45-day hackathon so customers can ask natural-language questions about wallets and assets through an API; RBAC and row-level security restrict each tenant to its own data. Fireblocks then reused the same approach internally with Cortex Agents and semantic views so product teams can go from a Jira ticket to the relevant product metrics, while Streamlit apps publish live shared reports instead of screenshots. The result is an AI-assisted analytics environment that scales to billions of rows, preserves security, and frees analysts to focus on deeper insight.

Data flow

Asset, wallet, revenue, Salesforce, and Zendesk data from 15 domains flows into Snowflake on AWS, where it is secured with RBAC and row-level security. Cortex Agents with semantic views power Fire Genie and an internal natural-language analytics agent, while Streamlit surfaces live shared reports and APIs return customer-specific answers about wallets, assets, and product behavior.

Solution architecture

3 components · 3 layers
  1. Compute
    • Cortex Agents Powers the external Fire Genie assistant and the internal natural-language analytics agent over Fireblocks semantic views.
  2. Storage
    • Snowflake Stores and governs the cross-domain wallet, asset, revenue, and support data that powers Fireblocks analytics.
  3. Serving
    • Streamlit Lets internal teams build and share live analytics reports instead of static screenshots.

Architecture clues

  • Fire Genie was built in a 45-day hackathon and exposes customer-specific analytics through an API.
  • RBAC and row-level security are used so customers can query only their own data.
  • Semantic views help internal agents link product questions and Jira work items back to the right metrics.

Evidence from the source

At first, I didn’t think we’d be able to do this without a massive risk of data leaks.
But then in a 45-day hackathon, we developed our AI agent, Fire Genie, on Snowflake.
Fireblock’s internal agent now powers over 2,000 analysis queries per month, roughly 40-50% of all queries.
This saves the equivalent of two full time analysts’ worth of capacity every month.
With billions of rows of data across our platform, asking even basic queries was taking up to 20 minutes.
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
    2 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
    5 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

    Fireblocks customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/fireblocks/
    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 Apr 18, 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 Aug 3, 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.