Author here.<p>Not all RESTful APIs will fit into a framework like this, and the choice of RethinkDB limits its applicability to a narrower community, but I intend on supporting other document-based DBs in the future. I really like RethinkDB's API and ReQL in particular, and it seems like a solid foundation to build something a little out of the ordinary on.<p>What makes it different from other ORMs? It's a rethinking of ORM mechanics for a "document-based" backend system.<p>* JSON documents are validated using JSON-Schema (<a href="http://json-schema.org" rel="nofollow">http://json-schema.org</a>).<p>* It tries to make the exposure of non-CRUD operations relate as a method to a logical server-side object and have a consistent endpoint syntax. It also uses Python function annotations to generate request and response schemas for methods.<p>All API endpoints exist within a four-tiered path hierarchy of<p>* Suite - base level, serves as a collection of applications and repo for basic shared schemas<p>* Application - a bundle of collections representing a logical set of functionality, methods that bind at this level act like "library functions"<p>* Collection - a collection of documents sharing a common schema. Methods that bind at this level act like "class methods"<p>* Document - a single instance of a document schema, representing concrete data. Methods that bind at this level act like "instance methods" in traditional OO programming.<p>What helper features does it have?<p>* Reusable apps / collections.<p>* JWT based sample authentication app, auth.<p>* Automatically generated help from schema descriptions and python docstrings<p>* Self-describing schema endpoints for suites, applications, collections, documents, and their methods.<p>This is pre-release stuff, to be sure. I'm using it on personal projects, but it needs:<p>* More tests<p>* More docs for the Python side of things (I'm working on this first)<p>* A solid example application<p>* Automatic generation of JS API connectors