Elglide documentation

Guides for connecting sources, keeping data in sync, and running your tenant.

1Connect a source

Pick the network path your security team accepts, then connect a database, a file location or an API.

How your sources reach Elglide — a direct connection, an SSH bastion, or an agent inside your network.

Per-source type mapping: what is extracted verbatim, what is auto-cast, and how it lands in Snowflake.

CSV, JSON, XML and Parquet files read in place from a share, a bucket or an SFTP server — nothing is copied or moved.

Any JSON REST API, paged and incremental, with each endpoint landing as a table.

How each run moves less data than the last, and what happens when the source changes shape.

The Full → RowHash → Watermark → CDC ladder, and how a table qualifies for each step.

Enable your database's native change capture so a run reads only what changed.

What happens when a source column is added, dropped, retyped or renamed, and how to control it per task.

Audit rules, thresholds, auto-retry and alerts — check that what landed in Snowflake matches the source.

What Admins, Owners and Stewards can do, and the flat rate with its free allowance.

How Elglide compares on views, sync intelligence, retention, scale and cost, and what changed recently.