How it works

Each plan includes, with regards to a monthly timeline, a predefined amount of credits, cloud storage, and bandwidth:

Credits are used to execute scripts: Depending on the script value, a bunch of credits is deducted from your account each time a script is executed.
Cloud storage is used to store your images in the cloud: This action is not mandatory, but proffers a useful solution, if you want to perform multiple activities on the same image or to publish your images to CDN.
The bandwidth is the traffic: Your contents are generated when transferred from Ozwol (API responses, CDN traffic, etc.). However, data transfer to Ozwol is not recorded.

Once you have chosen and subscribed to a plan, you can use the service via three different approaches, with respect to your unique needs:
• Integrate your legacy solution with our RESTful API;
• Set up some hot-folders, where you can upload the files you need to process;
• Dynamically create contents and distribute it worldwide, under control.

Whatever are your needs, you can process your images by making use of special procedures which are called scripts, to analyze, edit and eventually publish them, if needed.

 

RESTful API

The client solution executes a POST request, sending the following information:
• An API key, to authenticate
• An image (encoded with base64) or an image reference (URI, another bucket, etc.)
• The name of the script to be run against the image
• The parameters required by the script

Once the image has been processed, Ozwol returns the results of the analysis, as a JSON file or a modified image, according to the type of script that has been executed. In the latter case, the resulting image can be downloaded or saved onto a different area (a project repository, a remote server, CDN).

The credit usage depends on the value of the script that has been executed (Data transfer to Ozwol is not recorded).

This approach is recommended if you need to integrate a legacy solution with Ozwol Engine, such as DAM (Digital Asset Management software), to execute advanced operations that cannot be provided by the solution.

 

Hot-folders

This approach integrates a simple and quick setup and therefore does not require any API integration.

By using the Ozwol back-end area, you can create a folder on your project repository and thus, set it as a hot-folder, by assigning one or more scripts. For each script, you must designate an output folder or a different destination (another bucket, a remote SFTP server, CDN).

Once everything has been appropriately configured, you can upload your files into the hot-folder, using software compatible with S3 or SFTP protocols, after which each loaded file is processed by the scripts associated with the hot-folder.
Script parameters, if required, can be operated, using the folder name or the file name. The results (in JSON files or images) are then saved onto the final destination which has been defined initially.

This activity happens in real time, but it is up to you to download the output results.

The credit usage depends on the value of the script that has been executed, but data transfer to Ozwol is not recorded.

This solution is recommended if you need to process stocks of files for a limited period, without having to integrate a legacy solution.

 

Worldwide distribute dynamically created contents

Images that are permanently stored in the bucket of the project can be edited in real time and easily published to CDN, to be used on websites, social and mobile apps.
The image URL will contain:
• The name of the script to run on the image
• The parameters of such script
• The name of the image, previously loaded into the bucket of the project (see Step 1 below)

This solution allows you to distribute and concurrently keep control of your images on all digital channels, tracking their usage and limiting their view using embargo and expiry date.

The credit depends on the value of the script that has been selected, but it is only deducted at the first time of running the script (see Step 2 below), as the resulting image is cached and reused with the subsequent calls (see Step 3 below). Data transfer to Ozwol is not recorded.

This approach is recommended, if you need to distribute large quantities of images globally in different formats, processed in real time, and, ensure that all images are adequately tracked and controlled.