Netpump Data operates on a different level to SD-WAN applications. It can be used with or without SD-WAN overlays, resulting in additional performance improvements when used together. Netpump Data improves the efficiency of each individual network connection without altering the data or IP packet headers — making it completely transparent to SD-WAN and all other higher-level applications. Every connection under SD-WAN control simply works more efficiently. Unlike solutions such as Aspera and Hightail, Netpump Data allows direct origin-to-destination file transfers with no intermediary servers required.

No. Netpump Data's core capabilities and performance improvements do not involve file compression at all. The material performance improvements are a genuine increase in transmission efficiency for a given file size across a network connection.

Netpump Data utilises a number of proprietary features in addition to varying packet size. While optimal MTU size is typically determined for a single specific connection, Netpump Data's approach to chunking and re-stitching data delivers enhanced transmission efficiency well beyond what a simple MTU setting can achieve alone.

Yes. Netpump Data uses a proprietary process of "chunking" data files into optimal packet sizes for transmission, and must "restitch" the packets back together at the destination device to deliver the complete file without error. Only one installation is required per device — a device can function as both origin and destination with a single install.

Netpump Data delivers similar or superior file transfer times without requiring files to be first uploaded to dedicated servers. UDP-based applications also "crowd out" other applications running in parallel on origin or destination devices and do not operate within fair-use guidelines. Netpump Data overcomes the typical challenges of TCP/IP and delivers data faster on an open network than UDP does on a dedicated connection — while operating fairly alongside all other network traffic.

Netpump Data can be installed on remote devices in the same way as operating system and service upgrades are rolled out — by the customer on a controlled basis.

Major and minor updates to Netpump Data, should they arise, can be delivered to all managed devices across a network in a coordinated manner by the customer. Timing and implementation of updates is managed by the customer — not dictated by Pacbyte Software.

Yes. Netpump Data does not read the data or files being transferred. Encrypted files are delivered to the destination in exactly the same encrypted form they departed from the origin. Netpump Data can also add an additional layer of encryption to either encrypted or unencrypted files.

Very little. Overhead remains consistently below 2% on both origin and destination devices. At idle, Netpump Data uses 0% CPU. At maximum transfer speeds, approximately 2% CPU is used. Additional CPU usage due to increased I/O read/write activity will vary by system but remains low.

Yes. Even on a low-latency connection of 10ms, Netpump Data can improve connection efficiency by around 20–25%. High-latency networks deliver the most dramatic improvements — Netpump Data's multithreaded approach dramatically reduces the adverse impact of retransmission delays caused by packet loss.

At idle: 0% CPU on both origin and destination devices. At maximum transfer speeds: approximately 2% CPU for Netpump Data's own operation. Additional CPU usage due to increased I/O read/write activity will vary system to system.

The fully functional version of Netpump Data is around 40MB. Only one installation is required per device. A lightweight version of around 100KB is available for Java-based and specific application environments.

Yes. Netpump Data can be configured for use on cloud servers that provide subscriber access to their root directory — allowing installation of additional services. This is supported by many leading cloud providers, including AWS S3.

No. Netpump Data is a software-only solution that can be installed on almost any existing device meeting the minimum OS requirements. Bespoke versions can be developed for specific environments such as defence and intelligence.

No. Netpump Data simply chunks existing data files into smaller or larger packets for optimal transmission efficiency — there is 100% certainty of the file content and structure at the destination device.

Netpump Data operates on any network connection using TCP/IP — LAN, WAN, MPLS, VPN, radio, satellite, submarine cable and more. Applications have been developed for Linux, Windows and macOS.

Netpump Data will deliver similar performance improvements to those experienced on terrestrial communication links.

SSL creates a small amount of additional overhead as it is applied to each data packet. The SSL overhead is broadly a function of total file size. Consequently, the use of smaller data packets does not result in a material difference to this overhead, nor to the decryption processing load at the destination device.

No. Netpump Data can operate on both closed and open network environments where TCP/IP is the underlying communication protocol.

Netpump Data operates as a service and will require permissions (inherited from the user) to pass through firewalls.

For most installations, the customer determines these settings. The data chunk size defaults to 10MB but is configurable down to 10KB. The default number of threads is 8 but can be configured higher or lower as appropriate. The same settings must be consistent between origin and destination devices.

No. The GUI is provided as a simple interface for testing. Most customer installations will have Netpump Data built into the operating environment as a service.

Yes. If Netpump Data is installed on both remote machines, control of file transfers between them can occur from a third location, using a common customer authorisation code.

Yes — transfers are made sequentially.

If there is a connection drop or crash, Netpump Data will resume the file transfer from the last data packet copied upon restarting — the entire file transfer does not need to commence again.

Various levels of logging are available from verbose to minimal (including fatal) and are maintained in a localised file.

No. Netpump Data requires a common customer authorisation code at both origin and destination devices. This code is set by the customer itself and is not disclosed to or accessible by Pacbyte Software or any third party.

Yes. Netpump Video does not alter the information sent across a network connection. Its operation is transparent to SD-WAN, MPLS and all other higher-level applications — these continue to work exactly as before, but with each connection operating more efficiently. Netpump Video is agnostic to the network or connection environment in which it is applied.

No. Netpump Video's core performance improvements do not involve file compression at all. For some video formats, further improvements can be achieved through an optional lossless compression add-in. Unlike predictive-based algorithms such as Raptor or Fountain, Netpump Video's algorithm guarantees 100% certainty of delivery of the full uncompressed file at the destination.

No — unlike Netpump Data, Netpump Video only requires the SDK library files to be compiled into the client player. The player will restitch and decompress packets at the destination device to deliver the complete video without error.

Netpump Video comes as an SDK with library files to plug into current players on all major platforms. Once the libraries are plugged in and manifest folders loaded, the current method employed by distributors may continue to be used. A transition to compressed format can be made in stages — some content may remain uncompressed while other content is compressed.

Yes. As Netpump Video is a delivery method only, DRMs are not affected in any way. For compressed files, decompression occurs on the client device before any DRM verification — compressed files are not affected by DRMs.

Dependent on the form of live video streaming, Netpump Video may offer support. Contact Pacbyte with details of the architecture and they will advise on an implementation method.

Yes. Netpump Video supports any configuration of Fixed Bitrate (FBR), Adaptive Bitrate (ABR), ABR Compressed, or Live Streaming.

Netpump Video is agnostic to video codecs — it is a delivery method only, to an existing player.

No additional overhead on a server. Overhead on a client device is reduced to approximately 7% (or 7.1% if compression is used). This is significantly less than the overhead experienced with VLC or other similar video decoder plugins.

Yes. Even on a low-latency connection of 10ms, Netpump Video can improve connection efficiency by around 20–25%. High-latency networks deliver the most dramatic benefits.

Typically around 50KB for the fully functional version installed on each client device.

For ABR, only a manifest (XML) file needs to be added to the root folder of each video. For ABR Compressed, additional temporary storage is required during the compression stage — original files may be deleted after compression. For FBR, a restructuring of files may be required but this will not increase current storage used.

The Netpump Video SDK ships with a simple tool to compress current H264 ABR TS content. Alternatively, Pacbyte can arrange for a third party to perform the compression.

No. Netpump Video is a software-only solution that can be installed on almost any existing device meeting the minimum OS requirements.

No. Netpump Video chunks existing data files into smaller or larger packets for optimal transmission efficiency — there is 100% certainty of file content and structure at the destination.

Netpump Video operates on any TCP/IP network connection. Applications have been developed for Windows, macOS, iOS and Android.

For SVOD and similar services, yes. Netpump Video can also operate on closed or open network environments where TCP/IP is the underlying protocol.

Netpump Video operates as a plugin to an existing video player and inherits the player's security settings.