I see two potential target groups here. One focuses on the developer and tries to solve the data storage and synchronization procedure. In that field, I'm not sure what the benefits of your solution are. Could you elaborate on how it is different to CouchDB[1] or even Amazon's storage service[2]?

The other market I'm seing targets users of the CMS system, i.e. the people who actually maintain the data. In most data centric projects I've been working on, you could be sure that the client will at some stage ask, how (not whether) he can change the existing data and add datasets after development has finished. This usually involved creating a CRUD user interface, which was tedious and in almost all cases, was never used.

Your front page focuses a lot on the former target group (create general datastructures, update and query them) whereas I think you might be offering more value in the latter group ("see how simple it is to add another recipe into your cooking app"). If you could combine the client's desire to control his money and time investment while making the solution easy to integrate for the developer, that might be good enough.

[1] CouchDB for iOS devices - http://news.ycombinator.com/item?id=2310863

[2] Amazon S3 for iOS: http://aws.amazon.com/sdkforios/faqs/

[3] Earlier discussion on StorageRoom: http://news.ycombinator.com/item?id=1847115