Jungle vs Nezumi for Heroku vs djangae

A WSGI middleware that provides a clean way via which your Django app is plugged into App Engine.;A hook to allow App Engine's deferred tasks and mapreduce handlers to run through the same environment.;The ability to use use the Datastore as the database for Django's models. See The Database Backend for details. You can also use App Engine's NDB, or you can use Google Cloud SQL (via the standard django MySQL backend) instead of or along side the Datastore. Or use all 3!;djangae.contrib.gauth which provides user models (both concrete and extendable abstract versions), an auth backend, and a middleware;which allow you to authenticate users using the App Engine's built-in Google Accounts authentication, and also allow you to use Django's permissions system on the Datastore (i.e. without being caught out by the Many-To-Many relationships).;A runserver command which fires up the App Engine SDK to serve your app (while still using Django's code reloading).;The ability to run management commands locally or on the remote App Engine Datastore.;A shell command that correctly sets up the environment/database. (Note, we should support this set up for any custom commands as well, see TODO.md).

Two-factor Authentication - Nezumi is the only app that fully supports the new Heroku Two-factor authentication. Sign in securely, even from your mobile device.;Multiple Accounts - Most users have to manage multiple Heroku accounts, so Nezumi was built around multiple account support. Add and manage as many accounts as you need.;Scale Immediately - Whether your site just hit Hacker News or your background job queue has filled up, Nezumi lets you scale your processes right from your mobile device.;Anytime, Anywhere - Check your logs, scale your processes, and even add collaborators. Nezumi is with you on the go so you can manage you app, no matter where you are.