File Transfer
Embedded File Transfer
Introducing INNORIX Embedded Transfer, which connects file transfer capability while leaving your existing application's screens and logic exactly as they are.
EMBEDDED CAPABILITY
Make file transfer a feature of your application.
Building a single upload button isn't hard. But things change once your real service has to handle multi-GB/TB files, huge numbers of files, long-running transfers and unstable networks.
That's because your application would have to implement and operate Progress, Resume, Retry, Parallel Transfer, Recovery, Integrity, Concurrency and Transfer Result all on its own.
INNORIX Embedded File Transfer connects Enterprise File Transfer as a product feature, while keeping your existing application's screens and business logic exactly as they are.
Your Application · Upload Files
INNORIX Transfer
EXPERIENCE FIRST
Build File Transfer into your existing product's Experience.
The center of Embedded File Transfer isn't the API itself.
What matters is making the experience of sending and receiving files part of the product, inside the Workflow that already exists in your customer portal, research system, manufacturing system, content service or internal business system.
BEFORE
WITH INNORIX
Rather than switching to a separate Transfer Tool, users can select files, check progress and continue using the result, all inside the Application they're already using.
ROLE SPLIT
Your application handles the business, INNORIX handles the file transfer.
This isn't about moving your existing Application's Business Logic to INNORIX.
Each system keeps doing what it does best, and only the File Transfer Engine gets connected.
The Application decides who is sending what and why, and INNORIX delivers the selected files to the actual Target and returns the result.
UI CONNECTED
Connect the Transfer capability you need to your existing UI.
You can build the Transfer Experience you need to fit your product's UX.
Customer Portal
Research System
In both cases, the actual Data Movement is handled by the INNORIX Transfer Engine, but the Experience shown to the user is built to fit that Application's purpose.
DATA MOVEMENT
Connect a range of Data Movement, not just Upload.
Embedded File Transfer isn't limited to adding a single Browser Upload. Since the Application requests the Data Movement it needs and INNORIX executes the actual Transfer, you can connect a variety of Sources and Targets.
The Application is the starting point of the task, and INNORIX executes the Data Path you need.
CONTROL / DATA SPLIT
Separate Control and Data Movement into their own roles.
Just because the Application requests a Transfer doesn't mean the large-scale Data itself has to move through the Application Backend.
Business / Control
Data Movement
Source
Target
The Application manages the user and business status, and INNORIX manages the Transfer between Source and Target.
This structure lets Business Logic and Data Movement scale independently of each other.
LARGE FILE
Deliver large files as a feature of your existing product.
Once an application starts handling large files, a simple Request/Response approach quickly makes the user Experience and operational requirements more complex.
You can apply INNORIX's Large File Transfer Capability directly to Embedded Transfer.
Rather than implementing the Transfer Protocol and Recovery Logic itself, the Application can use the completed Transfer Result as its business status.
HIGH VOLUME
Handle huge numbers of files through the same Interface.
Your Application can handle not just a single large file, but a Dataset made up of thousands or millions of files.
Even when it looks like a single Dataset or Project to the user, the Transfer Layer can manage the processing and results of each individual file.
WORKFLOW EVENT
Connect the Transfer Event to your existing Workflow.
File transfer is usually not the end of a task, but the starting point of the next Process.
For example, when a user submits a Dataset for analysis, the Application can start an INNORIX Transfer, receive the completion result, and then run the existing analysis system.
It's the existing Application that decides and runs the next Business Process, while INNORIX delivers the Transfer's status and completion result.
STATUS SYNC
Use Transfer completion as your Application Status.
What matters to the Application is a clear status it can use for business, not the internal workings of the File Transfer.
UPLOADING → READY
Connecting the Transfer Result to the Application's Business Workflow lets users understand the current business status without checking a separate Transfer Log.
INTEGRATION MODE
Choose the Integration method that fits your product.
Not every Application needs to show File Transfer the same way.
You might show Progress directly, as in a Customer Portal, or run the Transfer in the background, as in an Enterprise System.
Whatever the Integration method, it uses the same INNORIX Transfer Engine.
ONE ENGINE
Connect the same Transfer Engine to web, desktop and business systems.
INNORIX DevKit
INNORIX Transfer
What matters more than the Application's form factor is which files your task needs to deliver where.
The same Transfer Capability can be reused across multiple Applications, reducing the need to build a separate File Transfer Engine for every product.
API FLOW
Start a Transfer through the API and get the Result back.
DevKit provides the Interface for connecting Embedded File Transfer to your Application.
The API isn't the point of this product — it's how the Application connects to the Transfer Layer.
BACKEND SPLIT
Operate the Backend and the Transfer Engine each in their own domain.
The Application Backend keeps performing its existing role.
Splitting the roles this way lets your Application development team focus on Product Logic and the user Experience, while the Transfer Layer specializes in handling large-scale, high-volume Data Movement and Recovery.
PLATFORM OPS
Transfer Operation continues on the INNORIX Platform.
Just because a Transfer is Embedded in an Application doesn't mean its operation has to be scattered across each Application too.
Application A · B · C · D
INNORIX Platform
Transfers occurring across multiple Applications can be viewed from the Platform.
Users perform their own tasks in each Application, while the operations team manages the entire Transfer Infrastructure from a single operating area.
SHARED LAYER
Multiple applications share a single Transfer Layer.
As more Applications in an organization need File Transfer, each system can end up with its own separate Upload, Download, Retry and Transfer Logic.
Portal · Research App · Factory App · Media App · AI Platform
INNORIX Transfer Layer
Each Application's UI and Business Logic stay independent, while Data Movement can use a common Transfer Layer.
This structure lets you reuse the same Transfer Capability whenever a new Application is added.
SCOPE GROWTH
Expand from one Transfer feature to full Data Movement.
You can start by adding just one Upload to your Application.
As your business grows, you can connect a wider range of Data Movement on the same Transfer Layer.
INNORIX DevKit
- Large File
- High-Volume
- Server-to-Server
- Object Storage
- Distribution / Collection
- Automated Transfer
- AI Data Delivery
When a new Transfer Requirement comes up, you expand the Transfer Capability you need within the same Integration, rather than adding a separate transfer method for every Application.
MANY VIEWS
A feature to your Application, Infrastructure to your operations team.
Embedded File Transfer looks different depending on who's using it.
This structure is the biggest difference between Embedded File Transfer and simply offering an API.
Instead of teaching users a new Transfer Product, it builds File Transfer Capability into the product they already use.
CORE SCOPE
The core scope of Embedded File Transfer
API and SDK, Embedded UI and Headless Integration are the DevKit's Integration Methods for delivering this experience.
At its core, Embedded File Transfer is, from start to finish, about "delivering Enterprise File Transfer as a single product feature inside your existing Application."
GET STARTED
Make file transfer part of your product.
Connect INNORIX Transfer Capability to Upload, Download and Data Movement, while keeping your existing UI and Business Logic as they are.
Users send and receive files inside the Application they already use, developers connect Transfer through the API and SDK, and the operations team manages the Transfers from every Application in a single Platform.
Keep your product's Experience as it is.
Let INNORIX handle the File Transfer.
Want to add file transfer to your application?
We'll help you review the file transfer features and integration method your existing application needs.
- Review of Web, Desktop, and business system environments
- Proposal for API and SDK integration approach
- Guidance on applying it to your existing UI and Workflow