diff --git a/experimental/ubuntu-browsh/Dockerfile b/experimental/ubuntu-browsh/Dockerfile
new file mode 100644
index 0000000..13f7a90
--- /dev/null
+++ b/experimental/ubuntu-browsh/Dockerfile
@@ -0,0 +1,14 @@
+ARG docker_registry=docker.io/alnoda
+ARG image_tag=18.04-0.7
+
+FROM ${docker_registry}/ubuntu-workspace:${image_tag}
+
+USER root
+
+RUN apt-get -y update \
+    && apt-get install -y firefox \
+    && cd /tmp && wget https://github.com/browsh-org/browsh/releases/download/v1.6.4/browsh_1.6.4_linux_amd64.deb \
+    && cd /tmp && apt install -y ./browsh_1.6.4_linux_amd64.deb \
+    && rm /tmp/browsh_1.6.4_linux_amd64.deb
+
+USER abc
\ No newline at end of file
diff --git a/experimental/ubuntu-browsh/README.md b/experimental/ubuntu-browsh/README.md
new file mode 100644
index 0000000..9b2bccf
--- /dev/null
+++ b/experimental/ubuntu-browsh/README.md
@@ -0,0 +1,45 @@
+# Ubuntu-Browsh
+
+Ubuntu-Browsh - is [Ubuntu-Workspace](https://github.com/bluxmit/alnoda-workspaces/blob/main/workspaces/ubuntu-workspace) with a terminal 
+text-based browser [Browsh](https://www.brow.sh/) installed.  
+
+Ubuntu-Browsh has was created to tackle a very specific use-case - ability to view WEB UIs of the internal applications running in the internal 
+network, that does not have ingress for public internet connections. In other words, if you are allowed to SSH to one servers inside the private 
+network, but cannot access WEB UIs of the applications inside this network. One of the reasons might be that these WEB UIs don't have restriction/auth 
+mechanism built in. Or the company policy forbids opening any accesses from the specific network to the internet access.  
+
+One of the particular use-cases this workspace was used for - is to view EMR WEB interfaces (Spark History server UI, YARN UI, Livy UI), 
+and check the Spark logs out. There here are other ways to do this, i.e. setting up SSH tunneling, installing browser plugins, creating 
+secure gateways with VPN. This way is jus the simplest, and does not require modification of infrastructure or local environment.  
+
+## Use inrivate network
+
+SSH to one of the servers in the private network, and execute 
+
+```
+docker run --name browsh-workspace -d alnoda/ubuntu-browsh
+```
+
+and ssh into the workspace 
+
+```
+docker exec -it browsh-workspace /bin/zsh
+```
+
+## Other cases 
+
+```
+docker run --name browsh-workspace -d -p 8026:8026 alnoda/ubuntu-browsh
+```
+
+Open your browser on http://localhost:8026 and open any website with Browsh
+
+> `browsh --startup-url google.com`
+
+## Tips
+
+Sometimes if you quit Browsh, and try to launch it again later, there might be an error saying that headless Firefox is already running. 
+Execute `ps aux` find pid of firefox process and kill it, i.e. `kill 988` 
+
+
+