diff --git a/uncloud_django_based/uncloud/doc/README-how-to-configure-remote-uncloud-clients.org b/uncloud_django_based/uncloud/doc/README-how-to-configure-remote-uncloud-clients.org
index 7217e1f..b48886b 100644
--- a/uncloud_django_based/uncloud/doc/README-how-to-configure-remote-uncloud-clients.org
+++ b/uncloud_django_based/uncloud/doc/README-how-to-configure-remote-uncloud-clients.org
@@ -10,6 +10,7 @@
 | SSH -L tunnel            | All nodes can use [::1]:5432                              | SSH setup can be fragile             |
 | ssh djangohost manage.py | All DB ops locally                                        | Code is only executed on django host |
 | https + token            | Rest alike / consistent access                            | Code is only executed on django host |
+| from_django              | Everything is on the django host                          | main host can become bottleneck      |
 ** remote vs. local Django code execution
    - If manage.py is executed locally (= on the client), it can
      check/modify local configs
@@ -19,3 +20,9 @@
    - Remote execution (= on the primary django host) can acess the db
      via unix socket
    - However remote execution cannot check local state
+** from_django
+   - might reuse existing methods like celery
+   - reduces the amount of things to be installed on the client to
+     almost zero
+   - follows the opennebula model
+   - has a single point of failurebin