Connectivity
Connect anything: SFTP/FTPS/FTP, WebDAV, HTTP(S), S3, SMB, and HL7/FHIR/X12 — with password or modern SSH-key auth.
Connect anything. Automate everything.
Managed file transfer,
with a receipt for every file
Relayrix is self-hosted managed file transfer software. Automate your SFTP, FTPS, S3 and HL7/FHIR/X12 transfers — and prove every one of them landed.
- Built for HIPAA compliance
- Encrypted in transit & at rest
- Self-hosted — your data never leaves your walls
What Relayrix does
Automation
Schedule, watch, or manual triggers run your workflows unattended.
Delivery receipts
What you sent, where it landed, and the exact second it got there. Every file, automatically.
Visibility
Every file you’ve ever sent, searchable in seconds, in a record nobody can quietly edit.
Built for HIPAA from the ground up
Not bolted on afterwards: AES-256 at rest, the strongest encryption both sides support in transit, per-person logins with role-based access, an audit trail nobody can quietly edit, and an integrity check on every file. All five technical safeguards in the HIPAA Security Rule.
Simplicity, self-hosted
One platform on your own infrastructure, with Test and Prod environments built in.
Healthcare-aware
Transform on the way through
Drop in HL7, FHIR, or X12 and validate or convert mid-flight — no separate engine, no extra hop. The transform runs as part of the same pipeline that moves the file.
HL7 v2 → JSONFHIRX12 EDICSV ↔ XMLOCRChecksum
Delivery receipts
They’ll still say it. Now you can settle it.
Every file Relayrix delivers is recorded the moment it lands — what went out, exactly where, and when. So when a partner says the file never came, you don’t argue. You pull up the receipt — and send it.
Timestamped to the second
What you sent, where it landed, and exactly when — with nobody having to remember to check.
“Sent” isn’t “received”
Anything can say sent. Relayrix goes back and checks the file is really sitting on their server before it counts as delivered.
Find any file, any day
Search months of transfers by filename in seconds — every run, every file, success or failure.
Proof that holds up
A record nobody can quietly edit, including you. Hand it to an auditor or drop it into a dispute and it stands.
SFTP automation
FileZilla and WinSCP were never meant to run production
Either a desktop client moves a file only when somebody remembers, or a pile of scripts behind cron jobs and scheduled tasks moves it until one stops and nobody notices. Relayrix runs the same transfers on a schedule, confirms they actually landed, and tells you when they don’t — so nobody has to sit at a keyboard dragging folders, and nobody has to ask “did that go out?”
Runs whether anyone’s there or not
Schedules and folder watchers fire the transfer at 2 a.m., over a holiday weekend, and while the one person who knows the process is on vacation.
Credentials that aren’t in a spreadsheet
Hosts, keys, and passwords live encrypted in one place, behind role-based access — not saved in five people’s clients and a shared doc.
A record, not someone’s memory
A client’s transfer log disappears when you close the window. Relayrix keeps a dated receipt for every file, going back as far as you like.
Same connections, same hosts
SFTP, FTPS, FTP, WebDAV, S3, SMB, HTTP(S), and local paths — password or SSH-key auth. Point it at the servers you already connect to and keep going.
How SFTP automation replaces a script and a scheduled task →
One platform, not a pile of scripts
One place to run them, watch them, and prove they finished
Every team has them: a cron job on a server nobody remembers, a script written by someone who left, a scheduled task that works right up until it quietly doesn’t. Relayrix runs every transfer in one place, so you can see at a glance what ran, what didn’t, and what still needs you — without logging into four servers to find out.
- Before: a dozen scripts across a half-dozen servers, each with its own credentials, its own schedule, and its own way of failing quietly.
- After: one platform, one history, one alert path — every transfer either succeeded or told you it didn’t.
- And when it changes: edit a pipeline in the UI instead of a script only one person understands — so a new host, a new folder, or a new schedule isn’t a code change.
Notifications
Notifications that reach you
You shouldn’t find out about a missed feed from the person waiting on it. Failures, partial transfers, and stale or late feeds are flagged the moment they happen. An alert can still be missed, so every file that failed stays on the dashboard until it’s dealt with.
- Automatic alerts — flagged before anyone downstream notices.
- Your rules, your channels — email or a Slack / Teams / webhook alert, with a re-alert cooldown.
- Needs attention — a failed file waits at the top of the dashboard until a later run delivers it or someone clears it, with their name on it.
- Health on every connection — see which server is refusing transfers and how many pipelines run through it, before the partner calls.
What teams get out of Relayrix
Honestly I put off replacing our old scripts for two years because I dreaded the migration. It took an afternoon. Now when a feed doesn’t land I get a message, not a phone call from the hospital.
With a small IT team, our file transfers were a constant draw on our time. The delivery receipts already resolved a dispute with a payer who insisted a file was never sent.
We were running transfers off a machine under someone’s desk. Moving to one place we could actually watch cut our failures way down.
The numbers behind the ROI
The case studies quote the outcomes; the dashboard shows the operational reality behind them.
Switching engines
An interface engine alternative — without the rip-and-replace
Run it alongside what you have and move one feed at a time. HL7, FHIR and X12 are handled here too, so nothing has to be switched off over a weekend.
| Capability | RelayrixSelf-hosted | Other commercial engines | What you’re doing now |
|---|---|---|---|
| What you pay each year | $4,500, flat | $20K–40K reported quotes · $100K+ at scale | Whatever you pay now, plus the staff time around it |
| What growth costs you | Nothing — unlimited feeds, both environments | Depends on the tier you’re licensed for | Another script to write and maintain |
| Alerts you when a file doesn’t arrive | On your deadline — “by 09:00, Mon–Fri” | A rolling count, not a deadline | No |
| A receipt proving the file landed on their server | Every file, every time | Partial | Not usually |
| Reports you can forward to your boss | Scheduled to your inbox | Written for whoever runs the system | No |
| Your partner never picks up half a file | Prevented by design | Varies | Not usually |
| An audit trail nobody can quietly edit | Yes — and provable | Message logs | No |
| Clinical messages and plain file drops, side by side | Both, same screen | Message-first by design | Files only |
| Healthcare formats (HL7, FHIR, X12) | Built in | Yes | Build it yourself |
| Who runs it day to day | Your existing team, using forms | An integration developer | Whoever wrote the scripts |
| Time to first live feed | Minutes | Days–weeks | Varies |
A receipt, not a log entry. We read the file back off their server and check it matches what we sent, byte for byte (SHA-256). Only then does it count as delivered.
Never half a file. Their system picks up files the moment they appear. The filename doesn’t appear until the whole file has landed — so a dropped transfer leaves them nothing, rather than half a batch they’ll process anyway.
A deadline, not a hunch. Not “it’s been quiet a while” — “the 6am claims file still hasn’t landed, and it’s 09:15 Tuesday.” Your time zone, right through the clock change.
Nobody new to hire. Setting up a feed is filling in a form, not writing code. Reported quotes for a commercial engine start around $20,000 for ten connections, plus roughly 20% a year in maintenance — before hiring anyone to run it.
Professional
$4,500 / year
Billed annually · self-hosted license · no per-connection metering.
- Unlimited pipelines & connections
- All connectors — SFTP/FTPS, S3, WebDAV, SMB, HTTP(S), Local
- HL7 / FHIR / X12 transforms included
- A delivery receipt for every file + an audit trail nobody can quietly edit
- RBAC, Test/Prod environments, email & Slack / Teams / webhook alerts
- Statistics & scheduled email reports — files, records, month-on-month comparison
- Email support & version updates
Reported quotes for commercial interface engines run $20–40K a year, and past $100K at scale. None of them publish list pricing, so treat those as estimates.
Not ready to buy? Start a 14-day free trial — the full product, no credit card, one trial per account.