Stream data from SFTP to Materialize
Move data from SFTP to Materialize in minutes using Estuary. Stream, batch, or continuously sync data with control over latency from sub-second to batch.
- No credit card required
- 30-day free trial


- 200+Connectors
- 5500+Active users
- <100msEnd-to-end latency
- 7+GB/secSingle dataflow
How to integrate SFTP with Materialize in 3 simple steps
- 1
Connect SFTP as your data source
Set up a source connector for SFTP in minutes. Estuary supports streaming (including CDC where available) and batch data capture through events, incremental syncs, or snapshots — without custom pipelines, agents, or manual configuration.
- 2
Configure Materialize as your destination connector
Estuary supports intelligent schema handling, with schema inference and evolution tools that help align source and destination structures over time. It supports both batch and streaming data movement, reliably delivering data to Materialize.
- 3
Deploy and Monitor Your End-to-End Data Pipeline
Launch your pipeline and monitor it from a single UI. Estuary guarantees exactly-once delivery, handles backfills and replays, and scales with your data — without engineering overhead.

SFTP connector details
The SFTP capture connector in Estuary captures files from an SFTP server and loads their contents into Estuary collections. It can continuously discover and ingest newly added files from a configured directory and its subdirectories, making it useful for automated file-based data pipelines.
- Incremental file capture based on file modification time
- Recursive capture from subdirectories within the configured SFTP directory
- File filtering with regular expressions to capture only matching files
- Supports Avro, CSV, JSON, Protobuf, and W3C Extended Log formats
- Supports ZIP, GZIP, and ZSTD compression, with automatic compression detection
- Automatic file format and schema detection for most captures
- Multiple directory bindings within a single capture task
- Password or SSH key authentication
- Optional Ascending Keys mode for environments where files are written in strict lexicographical path order
By default, Estuary captures existing files and then incrementally captures newly added files according to their modification timestamps. If a file’s modification time changes, it may be captured again. For controlled file-naming schemes, Ascending Keys mode can instead process newly added files based on lexicographical path ordering.

Materialize connector details
The Materialize connector in Estuary streams data from Estuary collections to Materialize as Kafka-compatible messages using Dekaf. Materialize connects directly to Estuary as a Kafka source, enabling continuously updated SQL views and real-time analytics without requiring a separate Kafka cluster.
- Kafka-compatible streaming from Estuary collections to Materialize
- Direct integration with Materialize’s Kafka source connector
- No separate Kafka cluster required between Estuary and Materialize
- Avro message format for structured streaming data
- Confluent Schema Registry-compatible endpoint for automatic schema discovery
- UPSERT envelope support in Materialize for maintaining the latest state of keyed records
- Configurable Kafka topic names for individual Estuary collection bindings
- Kafka or CDC deletion modes for controlling how deletions are represented
- Optional strict Kafka-compatible topic naming
- SASL/SSL authentication using the Estuary materialization name and an authentication token
Materialize connects to Estuary’s Dekaf endpoint using SASL_SSL with the PLAIN mechanism. After configuring the Kafka connection and Schema Registry connection, you can create a Materialize source using Avro and ENVELOPE UPSERT, then build continuously updated materialized views with standard SQL.
Estuary in action
See how to build end-to-end pipelines using no-code connectors in minutes. Estuary does the rest.
Spend 2-5x less
Estuary customers not only do 4x more. They also spend 2-5x less on ETL and ELT. Estuary's unique ability to mix and match streaming and batch loading has also helped customers save as much as 40% on data warehouse compute costs.

SFTP to Materialize pricing estimate
Estimated monthly cost to move 800 GB from SFTP to Materialize is approximately $1,000.
Data moved
Choose how much data you want to move from SFTP to Materialize each month.
GB
Choose number of sources and destinations.
Why pay more?
Move the same data for a fraction of the cost.



What customers are saying
Getting started with Estuary
Free account
Getting started with Estuary is simple. Sign up for a free account.
Sign upDocs
Make sure you read through the documentation, especially the get started section.
Learn moreCommunity
Join the Slack community for the easiest way to get support while getting started.
Join Slack CommunityEstuary 101
Watch the Estuary 101 webinar for a guided introduction to using Estuary.
Watch

Frequently Asked Questions
Is this integration suitable for production workloads?
Yes. Estuary pipelines are designed for production use, with exactly-once delivery semantics, automated backfills, and continuous operation at scale.
Can I control where my data runs and is processed?
Yes. Estuary offers multiple deployment options, including fully managed SaaS, private deployments, and bring-your-own-cloud (BYOC). This allows teams to control where their data plane runs and meet security, compliance, and networking requirements. Learn more about Estuary's security and deployment options.
Can I build this SFTP to Materialize integration manually?
Yes, it's possible to build a manual pipeline using custom scripts, scheduled jobs, or open-source tools. However, manual approaches typically require ongoing maintenance, custom error handling, schema management, and operational overhead. Estuary simplifies this by providing a managed pipeline with built-in reliability, scaling, and monitoring.
Related articles
sftpMarch 5, 2026How to Connect SFTP/FTP to Redshift: 2 Easy Steps

sftpMarch 5, 2026SFTP/FTP to BigQuery: How to Transfer Your Data in Minutes

DekafMarch 6, 2026How to Stream MongoDB Data to ClickHouse in Real Time

DekafDecember 12, 2025How to Move Data from Snowflake to ClickHouse: Real-Time, No-Code Guide

DekafMarch 5, 2026How to Integrate Salesforce with ClickHouse in Real Time (No Code, No Kafka)

TutorialMarch 6, 2026How to Replicate MySQL to ClickHouse in Real Time Using CDC (In Minutes)

DataOps made simple
Add advanced capabilities like schema inference and evolution with a few clicks. Or automate your data pipeline and integrate into your existing DataOps using Estuary's rich CLI.






































