RadFuzion R logo RadHub Connect

New

Every site on one hub. No VPN.

RadHub Connect links your RadFuzion servers across the internet through RadFuzion’s relay. Each server only dials out over HTTPS, everything is encrypted end to end between your servers, and adding a site takes one code.

mailBook a walkthroughgraph_2What RadHub does
RadHub Connect3 sites online
HubRelayLakeside ClinicNorth CampusWestside Ortho
cloud_doneLakeside Clinic and North Campus online
keyCode made for Westside Ortho
lockWestside Ortho joined · keys exchanged end to end
check_circleOn the hub — 3 sites, no VPN
0
ports opened
443
outbound only
E2E
encrypted

What you skip

Connecting a site used to be an IT project

The usual way

  • remove_circleA VPN tunnel to every site
  • remove_circleFirewall change requests and port forwarding
  • remove_circleStatic IPs or public DNS names per site
  • remove_circleBack-and-forth with each site’s IT team

With RadHub Connect

  • check_circleOne code per site
  • check_circleOutbound HTTPS only — nothing to open
  • check_circleWorks behind NAT and any firewall that allows outbound HTTPS
  • check_circleConnected in seconds

How it works

Three steps. About a minute.

Nothing to install at the site beyond RadFuzion itself, and nothing to change on its network.

  1. 1badge

    Name the site

    On your hub, type the site’s name and click RadHub Connect. You get a one-time code — no address, port or IP to look up.

  2. 2content_paste

    Paste the code

    On the site’s RadFuzion, paste the code and click Join the hub. The two servers exchange keys with each other, end to end.

  3. 3hub

    It’s on your hub

    Seconds later it shows in the hub’s list — online and encrypted. Sites you already have switch over the same way, with one button on their row.

lock

The relay passes your traffic. It can’t read it.

Your servers encrypt everything for each other before it leaves the building. The relay in the middle forwards bytes it has no key for — dashboards, settings and everything else stay readable only to the two servers that share them.

  • verified_userEnd-to-end encrypted between your two servers — a fresh key exchange every session (ECDH P-256), AES-256-GCM, replays rejected
  • verified_userOutbound HTTPS only — no inbound ports, no port forwarding, nothing new exposed at any site
  • verified_userEvery server signs in with its RadFuzion license and its own key — servers of other organizations can’t reach yours
  • verified_userOne-time codes that expire in 7 days; pairing secrets stored encrypted on each server
  • verified_userRemove a site and it’s cut off at once — or switch RadHub Connect off for a license from the customer portal
  • verified_userThe relay stores nothing — it only sees which of your servers talk, when, and how much

Everything RadHub does

Now across the internet

A site on RadHub Connect is a full member of your hub — the same monitoring and control as a server down the hall.

monitor_heart

Live monitoring

Health and throughput of every site on the hub’s dashboard, wherever the site is.

open_in_new

Remote control

Open and manage any site’s RadFuzion from the hub — no remote desktop, no jump box.

sync_alt

Configuration & rules

Push configuration and routing rules out to sites from one place.

fact_check

One audit trail

Review activity across every site from the hub, in one place.

auto_awesome

AI through the hub

Sites on locked-down networks can reach your AI provider through the hub instead.

alt_route

Mix and match

Direct and VPN connections keep working. One hub can have both kinds of site.

Built to stay out of the way

Imaging never waits on the relay

RadHub Connect carries hub traffic between your servers. Routing, forwarding and everything else each site does stays local — if the relay can’t be reached, sites keep working and reconnect on their own.

toggle_onOptional — off until you turn it on
wifi_offSites keep routing if the link drops
autorenewReconnects by itself, no one paged
dashboardSee your connected servers in the customer portal

FAQ

Questions IT will ask

Do we still need a VPN to each site?add

Not for RadHub. RadHub Connect carries the hub’s monitoring, remote control and configuration traffic between your RadFuzion servers through the relay, so there is no tunnel to build per site. If you already have VPNs, direct connections over them keep working — one hub can use both.

What does each site’s firewall need?add

Outbound HTTPS (port 443) to relay.radfuzion.com — the same kind of connection a web browser makes. Nothing inbound: no port forwarding, no static IP, no public DNS name.

Does patient data pass through RadFuzion’s servers?add

Only as end-to-end encrypted traffic between your own servers. Each pair of servers agrees on fresh keys for every session; the relay forwards bytes it has no key for, and stores none of them. It only sees which of your servers are talking, when, and how much.

Can someone else connect to our servers through the relay?add

No. Every server signs in with its RadFuzion license and its own key, and the relay only connects servers of the same organization. On top of that, a site can only talk to a server it was paired with using a one-time code — and you can remove a site, or switch RadHub Connect off for a license in the customer portal, at any time.

What happens if the relay is unreachable?add

Imaging keeps flowing. Routing, forwarding and everything else each site does stays local and never waits on the relay. Hub-to-site links reconnect on their own as soon as it is back.

Connect your next site in a minute

We’ll show RadHub Connect linking a hub and a site live — code, paste, connected — and answer your IT team’s questions on the spot.

mailBook a walkthrough