ENTERPRISE WEB FILE TRANSFER
Raise your website's file transfer quality, while development and operations stay simple
INNORIX EX is an enterprise file transfer solution that embeds into your existing website to add large-file and high-volume upload and download capability.
It keeps your website's design and workflow exactly as they are, while helping uploads and downloads stay reliable even when large numbers of users connect at once. From event and API integration to real-time monitoring and transfer history, it keeps complex development and operations simple.
TRANSFER INFRASTRUCTURE
From Your Web Server to Object Storage,
One Engine.
Keep the web server you run today. EX's high-performance upload and download fit in beside your existing authentication, database, storage paths and business logic. There is no new service to build and no storage layout to change.
When you need more scale, extend the transfer path to object storage. Authentication and business processing stay with your web service, and the files move directly between the user and object storage. The web server is relieved of relaying files, and one EX engine supports both ways of transferring.
- Existing storage path/data/projects/Done
- DatabaseBusiness dataDone
- Post-processingBusiness logic keptDone
CUSTOMIZABLE UI
The Attach UI,
in the Design and Behaviour You Want.
Large files as a list, photos as thumbnails, video with a preview. Even on one web page, every attach area can have its own design and behaviour. File types, counts and size limits are set per area, so each attach screen is built for the job it serves.
Switch between list, icon and folder views and the selected files and their transfer state stay as they were. Show progress beside each file, or in a mini transfer window and notifications. Pick a ready-made UI to apply quickly, and build the parts you need yourself with events and the API.
Project File Upload
Choose files or drag them here
- Backup_2026.zip48 GBDone
- Dataset_Package.tar120 GB78%
- Simulation_Data.bin64 GB46%
Photo Upload
Video Upload
- Travel_Footage.mp412.8 GB88%
- Event_Video.mov28.5 GB42%
- Product_Clip.mp416.1 GB42%
HIGH-SPEED & RESUMABLE TRANSFER
Large Files Fast,
Interrupted Transfers Resumed.
Files of tens of gigabytes and huge numbers of small files are each transferred the way that suits them. EX uses the performance your network and storage have available, and spares users the chore of splitting or compressing files beforehand and merging them again after receipt.
If the network drops mid-transfer, it does not start over. The data already delivered is kept and the transfer carries on from the remaining range; if only some files in a batch failed, only those are processed again. Users pick up interrupted work without developers having to build retry and resume logic themselves.
File Transfer
- Transferring
- Disconnected
- Resuming
- Done
- Backup_2026.zip64 GBDone
- Simulation_Data.bin48 GBDone
WORKFLOW AUTOMATION
File Transfer and Business Processing,
One Automation.
Issue a project number before the upload, register the file in the database when it lands, then ask an external system to inspect it. The work that belongs before and after a transfer joins it in one flow. When it suits you, the transfer and the business processing can run at the same time.
What matters more is that each result is managed on its own. If the file arrived but only the DB save or the API call failed, there is no need to upload the file again. Configure only the failed step to run again, and cut the needless transfers and duplicated work.
- BeforePermission checkPermission confirmed
- TransferringScreen state updates
- ReceivedFile receipt confirmedFile received
- Post-processingDB save, API callPost-processing done
Business Processing
Project IDPRJ-2026-084
- DB saveRegister business dataDone
- API callRequest external inspectionDone
DOWNLOAD MANAGEMENT
Downloaded Files,
Straight to Where They Belong.
Users no longer dig a file out of the downloads folder and move it somewhere else. Through EX Agent a file can be saved to the default folder, to a path the user picks, or straight into a working folder the developer specifies. Large files received over and over can be filed automatically in a fixed place.
When a file of the same name already exists, apply the policy you want: overwrite, automatic numbering or ask the user. One download button takes care of receiving the file, where it is saved and how it is named, the way your service needs.
Save location
- Default download folderSaves to the browser's default download folder.
- User picks the pathChoose where to save on every download.
- Folder set by the developerSaves automatically to the specified location.
Documents / Projects / 2026
Same file name
- OverwriteReplaces the existing file.
- Auto numberingSaves as (1), (2) and so on.
- Ask the userConfirms on every save.
- Project_Data.zipExisting file
- Project_Data (1).zipNewly saved file
DELIVERY CONFIRMATION
From Download to Confirmed Save,
Automatically.
A click on the download button does not mean the file arrived. EX joins the transfer event to the actual save result the Agent confirms, and records automatically whether the file reached the user's device intact.
Who received which file and when, and who has not yet, can be managed alongside your business data. Because business state changes and notifications run on the actual receipt rather than on a download request, there is far less need to ask each user whether the file came through.
Download Receipt
- Download requested09:20:12
- Receipt confirmedAgent confirmed
- Confirmed at
- 2026.10.15 09:28:34
- Save result
- Saved intact
- Business status
- Received
PLATFORM INTEGRATION
From the Web to the Next Machine,
Every Move of the File Traced.
A file uploaded to your website does not have to stay on the web server. Connected to INNORIX Platform, the upload result goes into a Dataset, and on successful verification the next transfer runs automatically: to an analysis server, an AI system, another machine or object storage.
And where the file went is never lost. Who submitted it, which machines it passed through and where it was last confirmed are all in File Trace. The upload on your website becomes the starting point of automated file movement across your systems.
- Web UploadUser submission09:10:12Received
- DatasetProduction Data09:12:03Auto-registered
- Auto TransferRuns after verification09:15:27Transferred
- Analysis ServerData processing09:18:04Processed
- Object StorageResults archive09:25:18Saved
Project_Data.zip48 GB, 2026. 10. 15. 09:10:12
- Submitted by
- Jihoon Kim
- Job ID
- PRJ-2026-084
- Current location
- Object Storage
- Last confirmed
- 2026. 10. 15. 09:25:18
Faster than an explanation: try it yourself.
Connect the devices and build the distribution flow.
Add flowCancelSave draftSave & active
Flow canvas
0 devices · 1 step
Configuration
Start when
NowSchedule
Every day · 02:00
Source
HQ-BUILD-01
Target
Choose targetGET STARTED
Now put it to work in your application.
TECHNICAL FAQ
Frequently Asked Questions
Can INNORIX EX be added to an existing website?
EX upload and download can be integrated while the existing web service keeps its UI and its workflow. How it is connected in practice depends on the web server and the development environment.
Does EX support large numbers of concurrent users?
It can be configured to handle file transfers from many users at once. The scale it supports depends on server specification, network, storage and transfer settings, so the actual load-test conditions have to be confirmed.
Can files be uploaded straight to object storage without passing through the web server?
In supported configurations the existing web service handles authentication and business processing while the file data is transferred directly between the user and the object storage.
Can the file attachment UI be changed to the design we want?
You can use the ready-made transfer window, or build an attachment screen that fits your web service with the Custom UI and its events and APIs.
Can a database record or an API call be run once an upload finishes?
Transfer results can be connected to your business logic so that follow-up processing runs. The actual events and integration interfaces have to be confirmed against the developer documentation.
Can a downloaded file be saved to a specified folder?
In supported EX Agent environments the save path and the policy for identical file names can both be configured.
Can we confirm that a user actually received a file?
In supported Agent environments the download request event and the confirmation that the file was actually saved are distinguished, and both can be reflected in your business system.