> ## Documentation Index > Fetch the complete documentation index at: https://developers.techwolf.ai/llms.txt > Use this file to discover all available pages before exploring further. # SFTP TechWolf supports SFTP for file-based integrations: a TechWolf-hosted server, and customer-hosted servers. This page covers both, and describes the behaviour of customer-hosted connections configured in the Console. # TechWolf-hosted SFTP server TechWolf operates an SFTP server that maps each user's root directory to a directory in TechWolf's S3 infrastructure. Several integrations use it to exchange files with TechWolf. ## Server details | Region | Server address | Static IP addresses | Port | | ------ | -------------------- | ---------------------------- | ---- | | EU | eu3.sftp.techwolf.ai | 13.38.145.100, 15.188.45.53 | 22 | | US | us3.sftp.techwolf.ai | 52.203.212.226, 54.83.27.174 | 22 | Use the static IP addresses for allowlisting when a customer's source system requires network-level access rules. ## Access Customers can request access from TechWolf. TechWolf provides credentials specific to the integration, either a username and password or a username and SSH key, depending on the integration's security requirements. # Customer-hosted SFTP server A customer can use their own SFTP server. It is configured from the **SFTP Configuration** page in the Console by the customer, an implementation partner, or TechWolf Professional Services. This configuration flow currently applies only to **input** integrations on **customer-hosted** servers. It does not cover the TechWolf-hosted SFTP server above, nor file-based [exports](/integrations/file-based-output/overview). SFTP Configuration overview with one connected server For background on how SFTP works (keys, host-key pinning, connection flow), see [How SFTP works](/integrations/reference/sftp/how-sftp-works). For the trust model and recommended practices, see [Security](/integrations/reference/sftp/security). For step-by-step setup instructions, see [Self-service SFTP setup](/integrations/reference/sftp/self-service-setup). # Behaviour of a customer-hosted connection The points below describe behaviour that affects day-to-day use of a customer-hosted SFTP connection configured in the Console. * **Files are pulled once.** Each filename is pulled at most one time per server and recorded in the pull log. Re-uploading the same content under a new filename is required if a re-pull is needed. * **TechWolf never deletes files on the customer SFTP server.** Retention of data on the SFTP server is the customer's responsibility. * **Schedule.** Pulls run on a cron schedule, evaluated in UTC. The default is every 30 minutes (`*/30 * * * *`). After a missed tick (for example after a worker outage), the next tick fires as soon as possible rather than waiting another full interval. * **Host-key pinning is enforced.** Once a connection's host-key fingerprint is locked, a mismatching fingerprint on the server side aborts every future connection until an operator re-tests and re-locks. * **Folder mappings** route a remote path on the SFTP server to a destination subpath that file-based input integrations consume. See [File Organization](/integrations/reference/file-structure). * **Disable versus delete.** Disabling a server pauses all pulls but keeps mappings, keys, and history. Deleting a server is irreversible and removes its pull history. * **Per-mapping toggle.** Mappings can be paused individually without touching the rest of the connection. * **The file browser is read-only and independent of the scheduler.** Browsing a remote folder never marks files as pulled. * **Pull history.** Each successful pull is logged with its filename and timestamp, and is available on the **History** tab of the server.