SFTP

Direct SFTP transfer suits teams that already move data as files — or use a tool that can only export to a server — rather than granting access to a cloud warehouse or bucket. You push files to an SFTP server hosted by Auxia, and Auxia ingests them on an agreed schedule, mapping them into Auxia’s unified tables like any other source.

​

Features

​

How it works

• Auxia hosts the server. Auxia runs managed SFTP servers per region, so your data stays in your region. Each server has a fixed public IP address.
• One user per sender. Each system that sends files gets its own SFTP user, scoped to its own folders. A sender can’t see or reach any other folder.
• SSH key authentication only. You generate the key pair and send Auxia only the public key — the private key never leaves your systems.
• Files can’t be overwritten or deleted once uploaded, so every upload needs a unique file name.
• Partial uploads are never read. A file becomes visible only when its upload completes, so you don’t need a .done marker file.
• Ingestion runs on an agreed schedule. Files are mapped into Auxia’s unified tables like any other source.

​

File requirements

• Unique file names. Include the date in each file name — and the time, if you send more than one file a day. For example: orders_20261002_060000.csv.
• Dates in the folder or the file name. Either a dated folder per delivery (orders/2026-10-02/) or a date in the file name works. Agree which one with the Auxia team.
• One feed per folder. Keep each kind of file in its own folder, the same way as for cloud storage sources.
• Plain files. Send uncompressed files where you can. Zip archives aren’t supported.

​

Limitations

• SFTP connections are set up with the Auxia team, not in the self-serve wizard.
• Auxia hosts the server — Auxia doesn’t connect out to a server you run.
• Uploaded files can’t be replaced. To correct data, upload a new file with a new name.
• See Source data requirements for requirements shared by all connectors.