Secure file transfer automation

Automate secure file transfers. Keep every control.

Point the SFTP scripts, schedulers and cloud pipelines you already run at one governed Sharetru endpoint — eight ways in and out: five protocols, the web app, share links and a 60-endpoint REST API — and stop babysitting transfers, partner accounts and audit exports. Your 15-day free trial runs on yourcompany.sharetru.com.

Start free trial Request a demo

15-day free trial · Every protocol and the API included · FedRAMP Rev 5 (Class C) Certified option for CUI / ITAR

yourcompany.sharetru.comTransfer services

HTTPS — web app and REST APITLS 1.3 on Sharetru Federal · TLS 1.2 on Sharetru Commercial · SSO, MFA and API tokens

SFTP and SCP over SSHSSH keys or passwords · scripted system-to-system transfers

FTPS — implicit TLSTLS from the first byte · legacy FTPS clients, EDI and ERP jobs

FTPeS — explicit TLSTLS negotiated on the control channel · modern FTPS clients

FTP — plainCleartext, for legacy equipment · Commercial sites

Off

Switch any service off for the whole site. Pin any account to one protocol from one IP range.

The problem

Transfer automation that runs on passwords and tribal knowledge is a liability

Most teams already automate file transfer. The problem is how: credentials baked into scripts, partner accounts nobody offboards, and audit evidence assembled by hand before every assessment.

Three failure modes, one cause: the endpoint is not governed. Sharetru governs the endpoint and leaves your scheduler alone.

See how it works

Credential sprawl
Scripts with passwords in them

Fixed by SSH-key service accounts pinned to one IP range, one protocol and one folder — no password in the script.
Partner drift
Accounts nobody offboards
Vendors and subcontractors get access at kickoff. Six months after the contract ends, the account still works.

Fixed by inactive-user suspension and deletion that run on their own, and group membership you revoke from your own systems over the API.
Audit scramble
Evidence assembled by hand
Who moved what, when, from where? If the answer lives in three systems and a spreadsheet, every assessment costs a week.

Fixed by one file log and one admin log for every channel — queryable over the API, kept 3 to 72 months by plan and package.

Every way in. Every way out.

How many ways can files move into and out of Sharetru?

Eight, on one hostname, under one set of controls. Systems use SFTP, SCP, FTPS, FTPeS and — on Commercial sites — plain FTP. People use the HTTPS web app and share links. Your own software uses the 60-endpoint REST API. In a market that increasingly offers HTTPS in a browser and nothing else, that breadth is the point: your counterparties' legacy systems, EDI jobs and labs keep working without changes on their side, and every channel writes to the same audit log.

Channel	Encryption	Authentication	Built for	Status
HTTPS HTTPSweb app + REST APIInOut	TLS 1.2 on Sharetru Commercial; TLS 1.3 on Sharetru Federal	Web: password + OTP MFA, or SSO via SAML 2.0 / OAuth. API: `X-API-KEY` site token	People in a browser — upload, download, folder management — and your applications over the 60-endpoint REST API Chunked resumable uploads and byte-range downloads; examples in cURL, JavaScript, Python, C#, Java	Every plan
SFTP SFTP / SCPover SSHInOut	SSH transport with strong ciphers	SSH key pair (passwordless) or password	Scheduled system-to-system jobs; replacing on-prem SFTP servers; very large files Scriptable from any client, cron, PowerShell, OpenSSH sftp and scp	Recommended
FTPS FTPSimplicit TLSInOut	TLS from connection start	Username and password	Legacy FTPS clients and EDI / ERP integrations that require implicit mode Scriptable with WinSCP, curl, lftp	Legacy-friendly
FTPeS FTPeSexplicit TLS · AUTH TLSInOut	TLS negotiated on the control channel	Username and password	Modern FTPS clients and firewalls that expect explicit mode Scriptable with WinSCP, curl, lftp	Legacy-friendly
FTP FTPplain · Commercial sitesInOut	None — cleartext	Username and password	Legacy equipment that cannot negotiate TLS or SSH Switch it off site-wide unless a system requires it	Disable unless required

Five services, eight channels, one hostname — all included in the free trial. Turn on what your counterparties need, switch off the rest with PATCH /api/site/file_services/, and pin any account to one protocol from one IP range.

Start free trial

The approach

What does Sharetru automate?

The three things that make file transfer risky. The transfer — SFTP, SCP, FTPS, FTPeS and HTTPS that any script or scheduler can drive. The administration — a 60-endpoint REST API for users, groups, folders, permissions, shares, network rules and logs. The policy — retention, user lifecycle, notifications and journaling that run without anyone remembering. Your scheduler stays. The risk leaves.

How one scheduled transfer runs

Your job server sends it. Sharetru checks it four times. The partner receives it. The log writes itself.

A scheduled export passes four controls before it lands. Nothing to install on either side — the scheduler is yours, the endpoint is governed.

Keep your scheduler. Lose the credential sprawl.

Keep cron, Task Scheduler, WinSCP or Azure Data Factory. Give each job a service account with an SSH key, pinned to one IP range, one protocol and one folder. No password in the script, nothing to install.

Provisioning becomes a pipeline.

Onboard a partner, create their folder, grant permissions and set a network rule from your HR or identity system over the REST API — and revoke all of it the day the contract ends.

Policies that never forget.

Inactive accounts suspend and delete themselves. Folders purge on your retention schedule. Every upload, download and share link over a transfer protocol or the web app notifies — and journals to a compliance mailbox.

Try it on your own Sharetru site — free for 15 days.Every protocol and the API included. Bring your existing SFTP script.

Start free trial Or request a demo

SFTP automation

How do you automate SFTP transfers with Sharetru?

Four steps, no new tooling. Create a service account with an SSH key, lock it to one origin, one protocol and one folder, and schedule the job wherever your jobs already run. Sharetru authenticates the connection, enforces the rule, logs the transfer and sends the notification — every run, without an operator.

nightly-export.sh · runs from cron on your job server

# Key-based SFTP push to a Sharetru site — no password stored
sftp -i ~/.ssh/sharetru_ed25519 -b - svc-finance@yourcompany.sharetru.com <<EOF
put /exports/gl-$(date +%F).csv /inbound/finance/
EOF

Two lines of standard OpenSSH. The same job works from WinSCP's scripting mode or a PowerShell scheduled task — swap the hostname for your site and the folder for the one the service account is scoped to.

Create a service account with an SSH key

Add the public key to the account so the script never stores a password. Lockout thresholds and dual authorization for new enrollments stay under your site policy.

Lock it to one origin, one protocol, one folder

A network rule limits the account to your job server's IP range over SFTP. Folder permissions grant read, write, delete or list-only separately, so a drop-folder account can write but never browse.

Schedule from where your jobs already run

cron and OpenSSH on Linux, Windows Task Scheduler with WinSCP or PowerShell, an Azure Data Factory SFTP connector, or a CI runner. Nothing to install on either side.

Verify without watching

Notifications fire on every upload, download, deletion and share link made over SFTP, FTPS, FTPeS, FTP or the web app — REST API actions do not send notifications, so verify those from the log. The file log is queryable over the API for the latest 90 days, with the rest of your retention window — 3 to 72 months by plan and package — kept as CSV in your site's log_history folder.

Start free trial Have us set up the first job

REST API

Does Sharetru have an API for file transfer and administration?

Yes — 60 endpoints over HTTPS, JSON:API conventions, an OpenAPI 3.0 reference at developer.sharetru.com, and generated examples in cURL, JavaScript, Python, C# and Java. Authenticate with an X-API-KEY site token. Uploads stream in resumable chunks of up to 10 MiB with Content-Range and an Idempotency-Key; downloads honor a byte Range header; rate limits answer with Retry-After. Move files and run the site from the same pipeline.

60endpoints across users, groups, folders, files, uploads, shares, permissions, network rules and logs

10 MiBmaximum upload chunk — resumable, idempotent, duplicate-safe

5languages with generated examples: cURL, JavaScript, Python, C#, Java

90 daysof file and admin log entries queryable through the API

Example workflow

Push a nightly export in, pull partner files out — over HTTPS

No SFTP client, no interactive login. A staged upload streams the file in; a single call streams it back out. Both directions are idempotent and resumable, so a retried job never creates a duplicate.

Your system → Sharetru Upload

POST/api/uploads/ — open a session: destination path, exact size, one destination mode (overwrite or create_new), a new Idempotency-Key.
PATCH/api/uploads/{id}/ — stream sequential chunks of up to 10 MiB, each with a Content-Range. A duplicate chunk is accepted as a retry.
POST/api/uploads/{id}/complete/ — finalize with a new Idempotency-Key; Sharetru verifies the length, moves the file into place and returns the File resource.

Sharetru → your system Download

GET/api/files/ — list with filtering, sorting and pagination to find what arrived.
GET/api/files/{id}/ — stream the bytes; send a Range header for resumable pulls.
GET/api/files/{id}/stat/ — read metadata without downloading content.

Onboard and offboard in one call

Add a user to the right group when a contract starts; remove them when it ends. Optional manager rights let a partner lead run their own team.

POST / DELETE · /api/group_members/

Provision folders, permissions and network rules

Create the folder, grant user or group permissions, and limit connections by IP range and protocol — from the pipeline that provisions the account.

POST · /api/folders/ · /api/permissions/ · /api/network_rules/

Pull the audit trail into your SIEM

Uploads, downloads, moves and deletions in the file log; every admin action in the administrative log. Filter, sort, paginate.

GET · /api/file_log/ · /api/admin_log/

Start free trial Read the API reference

Choose your platform

Sharetru Commercial or Sharetru Federal?

Same protocols, same API, same automation — two platforms. Sharetru Commercial uses FIPS 140-2 validated encryption for regulated commercial data. Sharetru Federal is FedRAMP Rev 5 (Class C) Certified (the new name for FedRAMP Moderate) with FIPS 140-3 validated encryption, built for CUI and ITAR data.

Sharetru Commercial

Regulated commercial data

For healthcare, financial services, manufacturing, engineering and IT teams moving files under HIPAA, SOC 2, GLBA/SOX/PCI or GDPR.

FIPS 140-2 validated encryption; TLS 1.2 on HTTPS
SOC 2 Type II Attested; HIPAA Support Package available
SFTP, SCP, FTPS, FTPeS and HTTPS — plus plain FTP for legacy equipment
Core and Complete plans, both with Platform API access; SSO on Complete; 15-day free trial
Audit log retention of 3 months on Core and 6 months on Complete — 72 months with the HIPAA Support Package

Start free trial

Sharetru Federal

CUI, ITAR and the defense industrial base

For contractors, primes and agencies that need a FedRAMP Rev 5 (Class C) Certified service a C3PAO can verify in the FedRAMP Marketplace.

FedRAMP Rev 5 (Class C) Certified IaaS, PaaS and SaaS
FIPS 140-3 validated encryption — the current federal standard
Built for CUI and ITAR data; supports CMMC Level 2 and NIST SP 800-171 evidence
Encrypted services only — SFTP, SCP, FTPS, FTPeS and HTTPS; runs in parallel with Microsoft GCC / GCC High
12 months of audit log retention; add the HIPAA Support Package when you need both, and export logs to meet ITAR's five-year recordkeeping rule

Request a Federal demo

Audit log retention3 moCore6 moComplete12 moSharetru Federal72 moHIPAA Support Package5 yrITAR — export logs to your archive

FAQ

Questions teams ask before they automate

Does Sharetru support both human and system-to-system transfers?

Yes. People use the HTTPS web application, secure share links and guest accounts; systems connect over SFTP, SCP, FTPS, FTPeS or the REST API with service accounts that authenticate by SSH key or API token. Both run on the same site under the same folder permissions, network rules and audit logs.

Does Sharetru include a built-in job scheduler?

No, by design. Sharetru is a governed endpoint rather than a proprietary workflow engine. You trigger transfers from the scheduler you already run — cron, Windows Task Scheduler, PowerShell, WinSCP scripts, Azure Data Factory or your own code against the API — and Sharetru enforces authentication, network rules, permissions, retention and logging on every transfer.

Can Sharetru replace a legacy on-premises SFTP server?

Yes, and nothing needs to be installed. Point existing clients and scripts at your yourcompany.sharetru.com hostname, migrate users and keys, and retire the server. There is no file-size limit, bandwidth is unlimited, and SFTP, SCP, FTPS and FTPeS are all available — plus plain FTP on Commercial sites — so counterparties keep working without changes.

Which SFTP and FTPS clients work with Sharetru?

Any standards-compliant client. Sharetru documents FileZilla, WinSCP, Cyberduck, ForkLift and CoffeeCup Free FTP, and automation teams commonly use OpenSSH sftp and scp, curl, PowerShell and the Azure Data Factory SFTP connector. The web application runs over HTTPS in Chrome, Firefox, Safari, Edge, Opera and Brave.

Does Sharetru integrate with our identity provider?

Yes. Single sign-on uses SAML 2.0 or OAuth with Microsoft Entra ID (Azure AD), Okta, Duo, Auth0, OneLogin or any compatible provider, and multiple identity providers can be configured at once. One-time-passcode MFA, account lockout thresholds, IP address restrictions and dual authorization for new user enrollment are built in.

Is plain FTP still supported?

Yes, on Sharetru Commercial sites, for legacy equipment that cannot negotiate TLS or SSH — and it can be switched off for the whole site. Sharetru Federal sites run the encrypted services only. Sharetru recommends SFTP or FTPS/FTPeS for anything sensitive. HTTPS runs TLS 1.2 on Sharetru Commercial and TLS 1.3 on Sharetru Federal.

Is the API included in every plan?

Platform API access is listed on both the Core and Complete plans. A site administrator activates it under Settings → Security → Service Activation and generates a site API token; requests then authenticate with the X-API-KEY header and Accept: application/vnd.api+json.

What runs automatically without writing any code?

Inactive user suspension and deletion, scheduled suspension on a future date, folder-level file retention, email notifications for every upload, download, deletion and share link made over a transfer protocol or the web app (REST API actions do not send notifications), Bcc journaling of every notification to a compliance mailbox, and automatic admin and file logging with retention from 3 to 72 months by plan and package — all configured in the admin console.

How long are audit logs retained?

Retention is 3 months on Core and 6 months on Complete. Sharetru Federal extends it to 12 months and the HIPAA Support Package to 72 months; the two packages can be combined when you need HIPAA and FedRAMP coverage together. Through the API, the most recent 90 days of file and administrative log entries are queryable; the rest of the window is kept as CSV files in your site's log_history folder. For ITAR's five-year recordkeeping requirement, export the logs to your own archive.

Which platform do I need for CUI or ITAR data?

Sharetru Federal — FedRAMP Rev 5 (Class C) Certified, with FIPS 140-3 validated encryption — for CUI, ITAR and CMMC Level 2 evidence. Sharetru Commercial, with FIPS 140-2 validated encryption, covers HIPAA, SOC 2 Type II, GLBA/SOX/PCI and GDPR use cases. Both expose the same protocols, API and automation.

Get started

See it run on your workflow, or start your free trial.

Every new signup includes a 15-day free trial with every protocol and the API included. Prefer a walkthrough? Bring your ugliest transfer script and we'll show the SFTP, API and policy layers against it — and where they take work off your team.

Request a demo See plans and start a trial

Replacing a self-run server, an MFT platform or a process that grew on its own? Talk through how you move files today, 30 minutes, no slides. Prefer to read first? The API reference.