This add-on is operated by GRIDBLAZE

Global Proximity based Storage As A Service


Last Updated: 19 March 2014

The GRIDBLAZE add-on is currently in beta.

Table of Contents

GRIDBLAZE is a supercharged object storage platform for user generated content like images and files. With over 15 storage nodes spread globally and smart routing, user uploaded files are uploaded at 4 times the speed to storage endpoints close to your users. In reverse, downloads are made blazingly fast as well, as data is already stored in close proximity to the requester.

The storage platform supports ingest and access through regular HTTP via POST and GET commands respectively. An alternative method to interact with storage will be through the OpenStack compatible API or web based file manager.

Provisioning the add-on

A list of all plans available can be found here.

To use GRIDBLAZE on Heroku, install the GRIDBLAZE add-on:

$ heroku addons:add gridblaze
-----> Adding GRIDBLAZE to sharp-mountain-4005... done, v112 (free)

To begin using the storage platform you will need to get an id that is automatically generated for each account. Each id will also have a corresponding key which should be kept secret.

$ heroku config | grep GRIDBLAZE
GRIDBLAZE_APPID:                h123i743
GRIDBLAZE_APPKEY:               98236498c027492910jal9777

These values will be used by your app at run time to generate a signature to authenticate uploads and access.

Direct uploads

Direct uploading uses a simple HTTP form post to upload files from users directly to the GRIDBLAZE storage platform, bypassing your application dynos on Heroku. Files will automatically be routed to the closest storage node to the user and kept in that location for future access.

HTML Upload Form Parameters

GRIDBLAZE requires that you generate a unique signature for every submitted upload. The signature is composed of the GRIDBLAZE app id and key and the following user-specified fields:

Parameter ? Value Description
appid Required ENV['GRIDBLAZE_APPID'] Your GRIDBLAZE application id.
appkey Required ENV['GRIDBLAZE_APPKEY'] Your GRIDBLAZE application key.
return_url Required http://www.domain.tld/uploadSuccess The URL web hook that GRIDBLAZE will call to confirm the successful upload and push the URL to access the file. It should be a full URL including "http://"
directory Optional /location/for/the/object/ The *nix style directory.
datetime Required The unix epoch formatted datetime when the page is generated as encoded in the signature. Note the upload has to happen within 24hrs of this date/time.
options Optional autogen | replace | reject | default This parameter value will be use if duplicates file on the same directory.
enable_auth Optional yes | no This parameter value will be use if the object need for authenticatoin at server for each download.
meta Optional {'name': 'myfile', 'type': 'just a file'} JSON encoded string of metadata of an object.
signature Required Digest::SHA256.hexdigest( appid + appkey + return_url + directory + datetime + option + enable_auth + meta ) Generated value out from other parameters above.

Generate Upload Signature

Create the signature as a hash of these fields, appended together and delimited by a .. Using Ruby as an example you can create a signature like this:

return_url ='http://www.domain.tld/uploadSuccess'
directory = '/'
datetime =
option = 'default'
enable_auth = 'no'
meta = "{'name': 'myfile', 'type': 'just a file'}"
signature = Digest::SHA256.hexdigest( appid + appkey + return_url + directory + datetime + option + enable_auth + meta )

NOTE : The sequence of the variable for generating the signature is sensitive, that you should follow.

appid + appkey + return_url + directory + datetime + option + enable_auth + meta

HTML form

The form action must be set as

The resulting HTML form generator should look like this.

<form action='' enctype='multipart/form-data' method='post'>
    <input type="hidden"  name="appid" value='<%= appid %>' id="appid" />
    <input type="hidden"  name="return_url" value='<%= return_url %>' id="return_url" />
    <input type="hidden"  name="directory" value='<%= directory %>' id="directory" />
    <input type="hidden"  name="datetime" value='<%= datetime %>' id="datetime" />
    <input type="hidden"  name="options" value='<%= options %>' id="options" />
    <input type="hidden"  name="enable_auth" value='<%= enable_auth %>' id="enable_auth" />
    <input type="hidden"  name="meta" value='<%= URI::encode(meta) %>' id="meta" />
    <input type="hidden"  name="signature" value='<%= signature %>' id="signature" />
    <input type="file"    name="file">
    <input type="submit"  name="upload" value="submit">

NOTE : For the ‘optional’ parameters if not set, you don’t have to include it in the HTML form generated.

Upload callback

After a user uploads a file to the storage network, GRIDBLAZE will call the return_url that you provided with the URL to access the file, the file size and any other form attributes that you sent along with the form post.

Form fields not specific to GRIDBLAZE will get resubmitted back to your return_url location, allowing GRIDBLAZE to handle the file submission and your application to handle the other aspects of the form in a way that provides seamless user experience.

Files uploaded to the GRIDBLAZE storage network will have URLs resembling the following format:

Here’s an example code of the return_url

post '/uploadSuccess' do # this will display the data


GRIDBLAZE API is built on top of the OpenStack Swift API and it’s compatible with Amazon S3 API. Connecting to the GRIDBLAZE API is done through the following host.

You can use Cyberduck, CloudBerry and other known class libraries (S3.php, Boto) to connect with GRIDBLAZE API or you can find more details on GRIDBLAZE API Document.

Connecting to GRIDBLAZE API will route requests to the closest API node. Unlike other APIs, our API servers are distributed to allow for lower latency and automated PUT routing to the closest node.

Managing storage

Managing and listing files stored on the GRIDBLAZE network can be done through the following means:

Web Based Object Manager

This is the simplest method and would only require you to login to the GRIDBLAZE command dashboard and select “Object Manager”. You will be able to upload/list/delete/rename all files stored on the GRIDBLAZE network associated with your app key. Files might be in different storage nodes but in the object manager, you will view all files in a single “disk view”.


This features is still under development however you are welcome to Alpha test it by connecting to our WebDAV server on:

Current issues are that of latency and speed which we are working to solve since WebDAV is not a very robust standard.

De-provisioning or removal

To remove GRIDBLAZE and stop using the storage service simply call the following command.

$ heroku addons:remove gridblaze


All GRIDBLAZE support and runtime issues should be submitted via on of the Heroku Support channels.