diff --git a/lib/frontends/__init__.py b/lib/frontends/__init__.py
new file mode 100644
index 0000000..e69de29
diff --git a/lib/frontends/frontends.py b/lib/frontends/frontends.py
new file mode 100644
index 0000000..e4a3491
--- /dev/null
+++ b/lib/frontends/frontends.py
@@ -0,0 +1,12 @@
+'''
+Just the frontends.py stub... ;)
+
+If linspector is being started without a frontend "enabled" it just is doing stuff like: polling, alerting, logging etc.
+
+Frontends a absolutely no requirement for running Linspector.
+'''
+
+
+class Frontends():
+    def __init__(self, **kwargs):
+        return
\ No newline at end of file
diff --git a/lib/frontends/https.py b/lib/frontends/https.py
new file mode 100644
index 0000000..a347895
--- /dev/null
+++ b/lib/frontends/https.py
@@ -0,0 +1,6 @@
+'''
+A HTTPS frontend to the current Linspector instance.
+
+A Webserver listening for requests to give information about the internal state of linspector.
+(maybe providing a JSON API to the instance too...)
+'''
diff --git a/lib/frontends/lish.py b/lib/frontends/lish.py
new file mode 100644
index 0000000..21398ec
--- /dev/null
+++ b/lib/frontends/lish.py
@@ -0,0 +1,12 @@
+'''
+The Linspector Interactive Shell...
+
+This  will become an interface to Linspector at "start" time. Think about MidnightCommander... and then run
+Linspector in a screen session and not as daemon, why not? BTW.: Daemonization is at this point of development
+cancelled, because it makes no sense to daemonize everything. Linspector is a user software which will run in any
+screen session perfectly.
+'''
+
+class LishFrontend(Frontends):
+    def __init__(self, **kwargs):
+        return
\ No newline at end of file