Automation and quick setup

Simple to configure, you define destination servers together with their priorities and weights for delivery queues. File transfers can also be automated for single servers. You can review your settings at any time.


High-Speed concurrent Delivery

MomaBLAST uses a flexible scheduler with advanced queuing policies which allows you to have excellent performances and real time file deliveries. For partners who don’t need to receive files in real time, you can assign a lower priority in order to save on the service cost.


Auto-recovery of connection errors

You don't ever need to worry about connection problems. If an error occurs, MomaBLAST automatically applies the most adequate solution to fix it and resend the files as soon as possible. And everything will always be reported.


Delivery Monitoring and Stats

MomaBLAST provides you with real time data to track your file's delivery time for each destination server. It also provides historical data on average waiting times, bandwidth used and connection speed.


Priced for every enterprise

MomaBLAST plans fit with every needs: entry level is quite affordable and you pay only for what you use.

Flusso Lavoro

Bespoke workflow solutions

Thanks to its layered architecture, MomaBLAST is ready for customization according to your needs. Specific transport protocols can be implemented in order to create interface to your partner's destination server. Advanced policies can be specified in order to manage content distribution correctly. Do not hesitate to contact our support team for more information about customization.

MomaBLAST at work

The first thing you have to configure in MomaBLAST is the list of destination servers with the whole set of parameters needed to successfully open a connection (address, username, password, path...). Usually a destination server is an ftp server but other application protocols can be implemented. Any destination server must be part of one or more pools of servers. Each pool has a unique name referenced by the feeders. The feeders are the means by which files enter the MomaBLAST engine. A feeder can be an “http” interface to a specific endpoint, an ftp connection to MomaBLAST ftp daemon or a MomaPIX client configured for syndication. As soon as a file arrives, it is bound to a pool and the scheduler will manage its distribution according to the policy and the channels’ availability. The creation of dynamic destination folders is possible. Every step of the distribution process will be reported in a real-time dashboard. The existing status will be reported in some statistical and historical distribution tables of data as well.

MomaBLAST concepts are better understood if some fundamental terms are explained:

Destination server

It's a server to which you wish to distribute content. Any destination server must be configured with the whole set of parameters needed for opening a connection and can be described by a priority level and a weight number. The scheduler will use priority and weight to organize the use of the available channels.


It's a named list of destination servers. The name of the pool is its unique identifier and is used by the feeders in order to add files to the proper queue. A destination server can be part of one or more pools.


It's the means by which files enter the MomaBLAST engine. Three kinds of feeders exist: “HTTP” feeder, “FTP” feeder, and MomaPIX feeder. A feeder must always be bound to a pool of servers. This binding is performed by the pool identifier.


It's the set of rules used by the scheduler for dequeuing and distributing files. Policy is based on priority and weight. First, the high-priority server is taken care of. Servers with the same priority are cyclically managed according to their weights.


It's a connection to a distribution server. Each channel transports one file at a time. As you use more channels, more files are distributed. To maximize throughput, a minimal ratio between destination servers and channels is expected.


It's the engine’s core. Among its responsibilities we can outline some of its fundamental jobs: dequeuing files, reacting to configuration changes, applying policy rules, managing connection errors, optimizing the use of channels, and reporting status activity.