Elglide vs. Snowflake Openflow
Snowflake Openflow and Elglide both land your operational databases in Snowflake. The difference shows up on the sources Openflow’s database connectors can’t reach: databases where log-based change capture was never an option, and views, which never appear in a write-ahead log at all.
When CDC isn’t an option
Log-based capture needs privileges and source-side changes
plenty of databases will never get. Elglide keeps syncing
incrementally with nothing but SELECT.
Views are first-class
Sync a database view the way you sync a table. A view emits nothing of its own to the WAL or redo log, so nothing log-based can see one.
Rows, not runtime-hours
$30 per 1M rows synced, the first 1M every month free, and the initial full load never billed — one line on the bill, metered live in-app. No always-on runtime to fund.
Elglide vs. Snowflake Openflow
| Features | Elglide | Snowflake Openflow |
|---|---|---|
| Getting to incremental | ||
| Source-side setup required |
✓RowHash and
Watermark need only SELECT. No schema changes,
no replication privileges, nothing created on your source
database.
|
PostgreSQL needs wal_level = logical (an
ALTER SYSTEM and an instance restart), a user
with the REPLICATION attribute, a publication,
and REPLICA IDENTITY configured per table. SQL
Server needs change tracking or CDC enabled; Oracle needs
XStream.
|
| When CDC can’t be enabled | ✓The table drops down the ladder — Watermark, RowHash, or Full — and keeps syncing. The cases that actually come up: a vendor-managed application database where a config change voids support, a managed instance where logical replication or the binlog was never switched on, no privilege to grant, or a DBA who won’t accept the WAL overhead. | ✗The database connectors are built on native change capture. Meet the prerequisites, or move that source to another tool. |
| Oracle licensing | ✓LogMiner. No additional Oracle license needed. | XStream. Oracle’s own documentation, quoted by Snowflake, makes Enterprise Edition “a prerequisite to license and use Oracle XStream” — so you take a 12- or 36-month embedded license through Snowflake, or bring your own GoldenGate entitlement. |
| Tables without a primary key | ✓Full mode always works and needs no key at all. A key matters only when you want to climb to an incremental mode. | The PostgreSQL connector “requires every replicated table to have a supported identity key configuration.” The SQL Server connector “only replicates database tables that contain primary keys.” |
| Delete detection | ✓RowHash catches physical deletes with no log access — a row missing from this run’s read is deleted in Snowflake on the same merge. Watermark catches soft deletes (a status flag set by an UPDATE). Physical deletes leave a watermark nothing to find, so a per-run count audit demotes the table back to RowHash automatically if they appear. | Deletes arrive on the change stream — which means every prerequisite above has to be satisfied first. |
| What counts as a source | ||
| Database views | ✓First-class. Full sync always; incremental via RowHash once a unique key is confirmed against the destination. | ✗A view writes nothing of its own to the WAL or redo log. Every database connector page describes table replication only. |
| Source coverage | Databases — SQL Server, PostgreSQL, MySQL/MariaDB, Oracle — plus files (CSV, JSON, XML, Parquet) from a folder. | ✓Much broader. Kafka and Kinesis, Salesforce, Workday, HubSpot, Shopify, Jira, Dataverse and Veeva, plus unstructured content from Box, SharePoint, Google Drive and Slack. If your sources live there, Openflow covers ground we don’t. |
| Deployment & freshness | ||
| Runs inside your network | ✓The hybrid agent runs on your side of the firewall and opens one outbound mutual-TLS connection — no inbound ports. Data goes straight from your database to your Snowflake; the control plane stays in our cloud. | ✓BYOC runs the data plane in your own VPC (generally available in AWS commercial regions), or Snowflake hosts it for you on Snowpark Container Services. Real parity. Both designs keep your data on your side; pick on operational fit, not on this row. |
| Schedule granularity | ✓Per table and per view. Each object carries its own cadence — a 1-minute schedule on the table that matters, nightly on the one that doesn’t, on-demand on the rest — with a pipeline-level default for everything you don’t override. | Connector-wide. “Merge Task Schedule CRON” is a single parameter per connector instance, and the tables it covers are chosen by an include list or regex, so every table in that connector shares one cadence. Different cadences mean separate connector instances to configure and pay for. |
| Freshness | Scheduled runs, not a live stream. Freshness is whatever cadence you set, down to a minute; nothing runs in between. Elglide does not do true streaming today — that is a later phase. If you need sub-second latency, say so and we will tell you straight. | ✓Continuous near-real-time capture, with the option to throttle destination merges on a CRON schedule. Openflow is ahead here. |
| Cost | ||
| What the bill is made of | ✓One line: $30 per 1M rows synced, the first 1M every month free, and the initial full load never billed — metered live in-app (see pricing). | Several lines: Openflow compute (per vCPU-second, 60-second minimum), warehouse credits for the initial snapshot and every CDC merge, Snowpipe ingest, telemetry per GB, and — on BYOC — your own EC2, EKS and storage bill from AWS. On the Snowflake-hosted deployment the management compute pool “continues to run and incurs costs, even if there are no runtimes running.” |
| Where Openflow wins | ||
| Native to Snowflake | A separate vendor, a separate contract, a separate bill. | ✓It is a Snowflake product: billed on your Snowflake contract, managed from Snowsight, supported by the same account team. For a Snowflake-first shop it is the incumbent default, and that counts for a lot. |
| Beyond databases | Databases and files. That is the whole product, and it is where our engineering goes. | ✓Built on Apache NiFi with hundreds of processors, covering streaming, SaaS applications and unstructured content — structured and unstructured text, images, audio, video and sensor data. |
Comparison based on Snowflake’s published Openflow documentation as of September 2026; Openflow ships quickly and capabilities may have changed since. Sources: About Openflow, Openflow connectors, PostgreSQL connector setup, SQL Server connector, Oracle connector, BYOC cost and Snowflake-deployment cost. Snowflake, Openflow, Snowsight, Oracle, GoldenGate, Apache NiFi and all other marks named here are trademarks of their respective owners and are not affiliated with Elglide.