>_ Nexoxa Bridge — SFTP · FTP · S3
FTP explicit and implicit TLS guide
Explicit vs implicit TLS — spelled out
NexoxaBridge supports ftp:// with ?secure=true for explicit TLS, ftps:// for implicit TLS on 990, and plain FTP for legacy hosts. Connection tester verifies AUTH before you queue transfers.
Free for up to 5 connections · Windows desktop
Your data stays yours
Local-first by default. Read how Bridge handles secrets.
100% local vault
Connection URLs, SSH keys, and SMTP secrets stay encrypted on your Windows machine — not in a Nexoxa cloud vault.
Zero vault telemetry
We don’t ship your credentials or query results to our servers. Account and billing stay separate from your connection vault.
Direct connection
Bridge talks straight to your databases, SSH hosts, and storage endpoints. No proxy that holds your passwords.
Built into the studio
1
Implicit FTPS
ftps://user:pass@host:990
2
Explicit TLS
STARTTLS on port 21 with secure=true.
3
Verify certs
Toggle strict TLS for production.
4
Test connect
AUTH check before first transfer.
Work faster in one place
Stop switching between CLI, clients, and dashboards.
ftp://?secure=true explicit TLS
Certificate verification toggle
Connection test on save
Same queue as SFTP
Related features
Explore more of the same workbench.
Frequently asked questions
Ready to try FTP FTPS TLS?
Free on the Microsoft Store for up to 5 connections. Credentials stay encrypted on your machine.