Your legacy vendor only speaks SFTP. You shouldn't pay $216/month to receive their files.
AWS Transfer Family is $216/month before you transfer a single byte. Bridglet replaces it at $15/month — with a cleaner API, no VPC configuration, and no IAM policy debugging at midnight.
Legacy SFTP is not going away
EDI systems, healthcare data partners, financial regulators, and older SaaS vendors all mandate SFTP. You don't get to choose the protocol — you only choose how expensive it is to support.
EDI & Financial Systems
ERP systems, payment processors, and banking partners have been using SFTP for two decades. These integrations aren't being rewritten for REST APIs anytime soon.
Healthcare & Compliance
HIPAA data partners, insurance clearinghouses, and lab systems often mandate SFTP by contract. Secure file transfer is a compliance requirement, not an option.
SaaS Data Exports
Older SaaS vendors (ad platforms, CRMs, logistics tools) still push reports via SFTP because it works and their customers expect it. You need a reliable place to receive them.
Connect Bridglet to your pipeline
Three patterns that cover most data engineering workflows. Start with polling — migrate to webhooks when you're ready.
A cron job hits the Bridglet REST API on a schedule, checks for new files in a directory, and downloads them into your pipeline. Simple, reliable, works with any orchestration tool.
Bridglet fires a webhook the instant a vendor uploads a file. Your Lambda or Cloud Function receives the event and starts processing immediately, with zero polling overhead or wasted API calls.
Set a retention window per directory. After your pipeline has processed the file, Bridglet automatically purges it on schedule — keeping your staging area clean without manual intervention.
Where Bridglet fits in your stack
Bridglet is the ingestion layer. It receives files from SFTP-speaking vendors and hands them off to your pipeline via REST API or webhook.
Replace your $216/month SFTP setup.
Start at $15/month. No credit card required to create your first directory. Migration takes less time than your next AWS console session.