As if multiple devices were on my own computer, file transfer is surprisingly simple.#
If you draw the transfer flow you want, INNORIX Platform will automatically repeat the transfer.#
No need dedicated tools for each cloud. Even AWS S3 can be transferred directly to other devices.#
Between different offices? No problem. Even devices on private IPs can transfer directly.#
Even if the network structure is complex, you can transfer with simple drag & drop in INNORIX Platform.#
| Classification | Situation | Reasons cannot directly connect | INNORIX Platform |
|---|---|---|---|
| Private IP environment ↔ Private IP environment | Office devices ↔ Devices in another office | The networks between the two offices are not routed (different subnets), VPN tunneling, etc., are required; direct connection is not possible | Auto-connect and transfer |
| Private IP environment ↔ Private IP environment | HQ internal network ↔ Branch internal network | HQ and branch networks are separated; private IPs are not routed to the Internet | Auto-connect and transfer |
| Private IP environment ↔ Private IP environment | DMZ internal devices ↔ Internal network devices | Security policies between DMZ and internal network block direct routing (allowing only specific ports) | Connect after simple network setup |
| Private IP environment ↔ Private IP environment | Factory OT network ↔ HQ IT network | OT network is isolated for security/stability; direct connection to external IT network is prohibited, physical network separation (air-gap) | Connect after simple network setup |
| Private IP environment ↔ External public IP environment | Internal firewall/protected devices ↔ External cloud devices | Firewalls/security policies block inbound connections; private IPs in NAT cannot be accessed from outside | Auto-connect and transfer |
| Private IP environment ↔ External public IP environment | On-prem servers ↔ Cloud virtual machines (inside VPC) | Cloud VPC resources do not have public IPs; direct access from outside is impossible, blocked by security groups/firewall | Auto-connect and transfer |
Distributing to or collecting from multiple regions from headquarters is also very easy.#
Collecting and distributing files through hubs is also possible.#
The tree structure allows for the distribution and collection of various files via two or more hubs.#
| Type | Source device | Hub1 | Hub2 | Target device |
|---|---|---|---|---|
| Distribution | AWS S3 | → AWS S3 10 devices (Hub1) | → Ubuntu 100 devices (Hub2) | → CentOS 5,000 devices |
| Distribution | Windows Server | → Ubuntu 30 devices (Hub1) | → RHEL 200 devices (Hub2) | → macOS 500 devices |
| Distribution | Ubuntu Server | → Rocky 20 devices (Hub1) | → Debian 50 devices (Hub2) | → Windows 1,000 devices |
| Distribution | RHEL Server | → AWS S3 5 devices (Hub1) | → Fedora 100 devices (Hub2) | → Ubuntu 2,000 devices |
| Distribution | Windows Server | → Debian 10 devices (Hub1) | → CentOS 200 devices (Hub2) | → RHEL 3,000 devices |
| Collection | CentOS 5,000 devices | → Ubuntu 100 devices (Hub1) | → AWS S3 10 devices (Hub2) | → AWS S3 |
| Collection | Windows 2,000 devices | → RHEL 50 devices (Hub1) | → Ubuntu 20 devices (Hub2) | → Windows Server |
| Collection | Debian 1,000 devices | → Rocky 30 devices (Hub1) | → macOS 10 devices (Hub2) | → RHEL Server |
| Collection | Fedora 2,500 devices | → Ubuntu 40 devices (Hub1) | → CentOS 30 devices (Hub2) | → AWS S3 |
| Collection | macOS 3,000 devices | → Windows 20 devices (Hub1) | → RHEL 50 devices (Hub2) | → Ubuntu Server |
Let’s compare all these features with the traditional ways.#
| Classification | Situation | USB, SSD, HDD | FTP | INNORIX Platform |
|---|---|---|---|---|
| Between various types of workstation, servers | macOS - Windows - Linux | Source device + target copy | Manual transfer after FTP server installation | Auto-connect and transfer |
| Between cloud object storage | AWS S3 - Azure Blob - GCP Storage - DELL object storage | Cloud device is not accessible. | Object storage is not accessible. | Auto-connect and transfer |
| Between various industrial devices | Ubuntu - RHEL - CentOS - Debian - Rocky Linux | Physical access is difficult | Manual transfer at all stages | Auto-connect and transfer |
| Private-network ↔ external-private-IP transfer | Devices inside the office building - devices inside each office | Source copy + logistics + target copy | Unable to connect | Auto-connect and transfer |
| Private-network ↔ external-private-IP transfer | H.Q. internal network - branch internal network | Source copy + logistics + target copy | Unable to connect | Auto-connect and transfer |
| Private-network ↔ external-private-IP transfer | Devices in DMZ - devices in internal network | Source copy + logistics + target copy | Unable to connect | Connect after simple network setup |
| Private-network ↔ external-private-IP transfer | Factory security network (OT network) - H.Q. IT network | Source copy + logistics + target cop | Unable to connect | Connect after simple network setup |
| Private-network ↔ public-IP connect | Devices blocked by internal firewall - devices opened externally | Cloud device is not accessible. | Unable to connect | Auto-connect and transfer |
| Private-network ↔ public-IP connect | On-premises servers - cloud VPC connect | Virtualization device (VM) is not accessible | Unable to connect | Auto-connect and transfer |
| Large file distribution | File distribution from server to hundreds of devices | Source copy + logistics + target copy x hundreds | Hundreds of manual transfers | Auto-connect and transfer |
| Large file collection | File collection from hundreds of devices to server | Source copy + logistics + target copy x hundreds | Hundreds of manual transfers | Auto-connect and transfer |
| Sequential transfer between devices | Sequential transfer between various research devices | Manual transfer at every stage | Manual transfer at all stages | Auto-connect and transfer |
| Tree-structure distribution | File distribution to final target devices via regional base devices | Too time-consuming and expensive to do | Unable to connect | Auto-connect and transfer |
| Tree-structure collection | File collection to final target servers via regional base devices | Too time-consuming and expensive to do | Unable to connect | Auto-connect and transfer |