Just a thought: just as the image/audio/video namespace functions help Nirvanix differentiate from S3, it occurs to me that having the (affordable) capacity to create and update zip archives from uploaded files could be a very useful function.
Example use case: collaborators upload various elements of a project, which - after creating or updating a zip archive via REST calls - users could then download as a single .zip (or tar?) file.
Just thought it might be worth discussing at your next roadmap meeting ;-)