Security and trust overview
FileAgent is self-hosted: your files move directly between your systems and stay inside your network. Here's the model, and how to deploy it safely.
Last updated July 17, 2026
#Self-hosted by design
FileAgent runs entirely on a host you control. Your files move directly between your sources and destinations — file contents are never sent to or stored by our services. The only outbound internet FileAgent needs is HTTPS for license validation and update checks. This keeps your data path inside your own network and trust boundaries.
#You own your data and storage
- You choose the host and the source and destination systems.
- Files, logs, and any archive copies live on storage you control.
- There's no FileAgent cloud holding your data.
#Layered protections
- HTTPS-only console with your own certificate (see Certificates).
- Encrypted credentials and data at rest on the host (see Credential & data protection).
- Access control — per-user accounts and roles, with job-scoped access, SSO, LDAP, IP allowlisting, and session controls on higher plans (see Security settings).
- An operational audit trail of every run (see Auditability).
#Fails closed
FileAgent is designed to fail closed rather than run insecurely. If the protected secret material it needs is missing, it stops rather than silently operating without it. That's why the host and its protected data should be backed up and restored together (see Backup & recovery).