Earlier quoted context omitted.
Why the /sigh? Is it because you don't agree that backend development is complex? Or do you feel differently about the front-end being the part that really matters? Personally, I'm impressed by this. It seems to me a compromise between MeteorJS/FireDB and "traditional" stacks. It also comes with its own environment to organize my code? Something about that is a little appealing. Maybe limiting too, but appealing.
Probably the /sigh because it looks like a great framework if the problem you're trying to solve is to build the simplest possible TODO-list app.
Actually, the example apps don't really do the platform justice. We (at deployd) use it in consulting projects for building big APIs with complex roles and business requirements. The design of deployd is driven more from lessons learned designing those APIs than from our experiments in TODO-lists.