> ## Documentation Index
> Fetch the complete documentation index at: https://docs.auxia.io/llms.txt
> Use this file to discover all available pages before exploring further.

# SFTP

> Send files to Auxia with a direct SFTP transfer

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.

<CardGroup cols={2}>
  <Card title="Setup guide" icon="list-check" href="/data-ingestion/data-connections/sftp/setup-guide">
    Get connected with the Auxia team
  </Card>

  <Card title="All connectors" icon="plug" href="/data-ingestion/data-connections">
    Compare connection options
  </Card>
</CardGroup>

## Features

| Feature | Supported | Notes |
| - | - | - |
| Setup | Assisted | Set up with the Auxia team |
| Auxia-hosted server | ✅ | Nothing to host or run on your side |
| Data stays in your region | ✅ | Auxia runs SFTP servers per region |
| Fixed IP address | ✅ | Allowlist it in your outbound firewall if needed |
| SSH key authentication | ✅ | Public-key only — no passwords are created or stored |
| Per-sender isolation | ✅ | Each sender has its own user, scoped to its own folders |
| PGP-encrypted files | ✅ | Encrypt to Auxia's public key; Auxia decrypts on read |
| Overwrite or delete uploaded files | ❌ | Every upload needs a unique file name |
| Zip archives | ❌ | Send plain files where you can |

## 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](/data-ingestion/concepts/file-sources#one-folder-per-table).
* **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](/data-ingestion/overview#source-data-requirements) for requirements shared by all connectors.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.