Free tools Windows power users keep installed
One-click scans. No signup required.
Snowflake announced an agreement to acquire data-integration company Datavolo on November 20, 2024, and completed the transaction five days later. The price was not disclosed in the announcement; Snowflake later reported approximately $106.8 million of acquisition-date fair-value consideration—about $87.7 million in stock and $19.1 million in cash. Datavolo’s technology is now most visible through Snowflake Openflow, a managed, NiFi-based layer for moving structured and unstructured data into Snowflake and related workloads.
What Snowflake actually bought
Datavolo was an open data-integration and dataflow company, not simply a generic data-management vendor. Snowflake described the deal as a way to move upstream into the “bronze layer” of the data lifecycle: the initial landing and ingestion stage before data is refined for analytics, applications or artificial-intelligence systems.
Datavolo was founded in 2023 by Joseph Witt and Luke Roquet, executives associated with Hortonworks and Cloudera. Its platform was built around Apache NiFi, an open-source project originally developed at the U.S. National Security Agency and widely used for secure data movement and processing. TechCrunch reported the company had raised $21 million before the acquisition.
In practical terms, data integration means moving and transforming information between systems. A dataflow adds routing, processing, monitoring and recovery as that information moves. Datavolo’s intended scope included database change-data capture (CDC), streaming events, SaaS systems and multimodal content such as documents, images, audio and video.
- Bronze layer: the initial landing zone for source data, usually before cleansing and modeling.
- Observability: visibility into flow health, lineage, throughput, failures and operational status.
- CDC: capture of inserts, updates and deletes from an operational database.
- Multimodal data: structured records alongside text, files, images, audio, video or sensor data.
Datavolo was not identical to Apache NiFi. It commercialized enterprise capabilities around NiFi-style dataflow management. Likewise, “built on Apache NiFi” does not mean every NiFi processor or Datavolo feature is automatically present in every Openflow account; availability depends on connector, deployment type, region and service status.
Timeline: announcement, closing and product follow-through
| Date | What happened |
|---|---|
| November 20, 2024 | Snowflake announced a definitive agreement to acquire Datavolo. Consideration was undisclosed and the transaction remained subject to closing conditions. Snowflake announcement |
| November 25, 2024 | Snowflake completed the acquisition. SEC filing |
| May 20, 2025 | Snowflake documented Openflow as a preview integration service built on Apache NiFi. Release note |
| By August 18, 2026 | Snowflake documentation described Openflow Snowflake Deployments as generally available in AWS, Azure and GCP commercial regions. Cost and availability documentation |
Why Snowflake wanted Datavolo
Move earlier in the data lifecycle
Snowflake historically captured much of its value after information had been extracted, loaded and made queryable. Datavolo offered a route into the movement and ingestion work that precedes those activities. Snowflake’s announcement framed this as expanding into enterprise data connectivity, pipeline management and observability.
Handle data needed for enterprise AI
AI systems require more than tables. Corporate documents, images, audio, video and event streams often sit in separate services and file systems. Snowflake said Datavolo would help bring structured and unstructured data into the platform for analytics, machine learning, Cortex features, applications and agents.
Rank #2
Reduce point-to-point integration
Reusable flows can replace some collections of single-purpose connectors. A common flow model can also standardize retries, routing, monitoring and security instead of forcing each source-to-destination link to be operated independently.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Potentially expand Snowflake consumption
This is strategic interpretation, not a disclosed deal target: if customers run more ingestion, container compute, storage and downstream AI workloads through Snowflake, the acquisition could increase usage-based revenue. Snowflake has not attributed a specific amount of revenue to Datavolo in the cited filings.
The transaction’s disclosed price—and why figures differ
Snowflake’s fiscal 2025 annual report reported approximately $106.8 million of acquisition-date fair-value purchase consideration, consisting principally of approximately $87.7 million in Snowflake stock and $19.1 million in cash. Annual report
Rank #3
Some coverage cites a figure near $170 million because certain employee-related equity was subject to vesting and accounted for separately as post-combination stock-based compensation. Snowflake’s quarterly filing explains that accounting treatment. Quarterly filing The cleanest description of the purchase consideration is therefore approximately $106.8 million, with the larger transaction-related figure requiring that employee-compensation qualification.
From Datavolo to Openflow
Openflow is the clearest visible product outcome of the acquisition, although Snowflake has not said that the entire service is unchanged Datavolo code. Snowflake describes Openflow as a managed, extensible integration layer built on Apache NiFi and connected to its broader data-engineering platform. Product overview
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDocumented use cases include:
- Ingesting unstructured content from services such as Google Drive and Box.
- Replicating database changes into Snowflake.
- Ingesting real-time events from platforms such as Kafka.
- Moving SaaS data for analytics.
- Creating custom flows with NiFi processors and controllers.
An Openflow Snowflake Deployment can host multiple runtimes, and runtimes can run multiple connectors. Creating the deployment itself has no separate fee, but active runtimes and associated infrastructure consume Snowflake resources. Deployment documentation
Rank #4
What customers gain
- Managed operations: Snowflake handles the service layer rather than requiring customers to run a complete NiFi environment.
- NiFi-style extensibility: The open-source heritage supports a broad processor and connectivity model, subject to Openflow’s supported packaging.
- Snowflake integration: Data can land close to Snowflake analytics, AI and application workloads, with Snowflake security and governance controls.
- One flow model for mixed data: Teams can address batch, CDC, streaming and file-based ingestion in a common environment where the relevant connectors are available.
Risks, limits and operating costs
Consumption is broader than a connector fee
Openflow costs can include compute pools, Snowpark Container Services, data ingestion, telemetry, storage and data transfer. A management component may continue consuming resources while a deployment remains active. Stopping runtimes can reduce runtime compute, but it does not make every related warehouse, ingestion, telemetry, storage or transfer charge disappear. Snowflake cost documentation
Database CDC may also require warehouse compute for initial snapshots and ongoing changes. Snowflake credits are charged per second with a 60-second minimum under the consumption table effective March 2, 2026; applicable prices vary by region, contract and deployment choice. Consumption table Snowflake lists Openflow BYOC at 0.0225 credits per vCPU-hour, but buyers should verify the effective rate and applicable commercial terms before budgeting. BYOC consumption table
Connector and data-quality boundaries
- A required source or destination may be unsupported, preview-only or restricted to a particular deployment.
- Schema drift can break transformations or create unexpected downstream structures.
- CDC and streaming flows need explicit offset, retry, replay and idempotency handling; duplicate delivery remains possible.
- A slow destination can create backpressure, queue growth, storage consumption and higher costs.
- Pipeline health does not prove that the data itself is complete, accurate or semantically correct.
- Private networking, secrets, roles and VPC placement require separate security validation.
Lock-in and portability
Centralizing ingestion and analytics in Snowflake can simplify operations while increasing vendor concentration. “Built on Apache NiFi” also does not guarantee identical release cadence, support, packaging or connector behavior to self-managed NiFi.
Who is Openflow a good fit for?
| Organization or use case | Assessment |
|---|---|
| Existing Snowflake enterprise with mixed structured and unstructured sources | Strong candidate if managed operations and direct Snowflake landing outweigh consumption costs. |
| Multicloud buyer seeking a neutral integration layer | Less attractive when portability and warehouse neutrality are primary requirements. |
| NiFi team wanting less infrastructure work | Potentially attractive, but verify processor, connector and deployment compatibility before migration. |
| SaaS or database replication buyer | Compare carefully with standardized managed-replication services; Openflow is broader than a simple connector subscription. |
| Highly regulated organization | Assess private connectivity, regional availability, secrets, role boundaries, auditability and data-residency requirements. |
| Cost-sensitive or highly bursty workload | Model idle management resources, runtime scaling, ingestion, telemetry, storage, transfer and downstream warehouse use before committing. |
Alternatives worth comparing
These products overlap with Openflow but are not interchangeable.
| Option | Typical reason to consider it | Key trade-off |
|---|---|---|
| Apache NiFi | Open-source dataflow control and self-managed portability. | Your team operates clusters, upgrades, security, scaling and high availability. |
| Fivetran | Managed SaaS and database replication with standardized connectors. | May be less suitable for deeply customized multimodal or event-driven flows. |
| Airbyte | Broad connector ecosystem and deployment flexibility. | Connector maturity, maintenance and total operating cost vary by source. |
| Informatica | Governance, legacy integration, cataloging and broad enterprise data management. | More suite-oriented and procurement-heavy than a focused ingestion layer. |
| AWS Glue | AWS-centered architectures using IAM, S3 and Lake Formation. | Less directly aligned with Snowflake-native governance and consumption. |
| Azure Data Factory | Microsoft and Azure data estates. | Compare networking, orchestration, connector depth and Snowflake transfer costs. |
| Google Cloud Data Fusion | GCP-heavy organizations with existing cloud-native tooling. | Evaluate how well it fits Snowflake governance and cross-cloud movement. |
How to evaluate an Openflow deployment
- Inventory every source and destination, including files, databases, SaaS systems and event streams.
- Classify each flow as batch, streaming, CDC or multimodal ingestion and verify connector status for the intended region and deployment.
- Define replay, deduplication, schema-evolution, backpressure and failure-recovery behavior before production.
- Model active-runtime, management, container, ingestion, telemetry, storage, transfer and downstream warehouse consumption.
- Test private networking, credentials, role boundaries, audit logs and data-residency controls.
- Run a side-by-side cost and portability review against NiFi, Fivetran, Airbyte or a cloud-native alternative where appropriate.
Bottom line
Snowflake did not merely buy another connector vendor. Datavolo gave it a credible way to control more of the path by which enterprise data reaches analytics and AI workloads. Openflow makes that strategy tangible, but the acquisition is valuable only when connector coverage, recovery design, deployment security and total consumption cost justify placing more of the data lifecycle inside Snowflake.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
