diff --git a/content/AKS supports WASM out of the box.md b/content/AKS supports WASM out of the box.md
new file mode 100644
index 000000000..64e51cfba
--- /dev/null
+++ b/content/AKS supports WASM out of the box.md	
@@ -0,0 +1,6 @@
+# AKS supports WASM out of the box
+
+#research
+
+Investigate this further.
+
diff --git a/content/Pods will run WASM binaries, not containers.md b/content/Pods will run WASM binaries, not containers.md
new file mode 100644
index 000000000..5517854a7
--- /dev/null
+++ b/content/Pods will run WASM binaries, not containers.md	
@@ -0,0 +1,8 @@
+# Pods will run WASM binaries, not containers
+
+#publish 
+
+When configuring a RuntimeClass on a deployment, the only difference is that the pods are running WASM applications instead of containers.
+
+From the outside nothing appears to be different.
+
diff --git a/content/Sidecars become useless when running WASM.md b/content/Sidecars become useless when running WASM.md
new file mode 100644
index 000000000..2484ed4c0
--- /dev/null
+++ b/content/Sidecars become useless when running WASM.md	
@@ -0,0 +1,7 @@
+# Sidecars become useless when running WASM
+
+#publish
+
+
+Because you cannot mix containers and WASM in the same pod, you can't run sidecar containers on WASM applications in Kubernetes. This makes service meshes that rely on sidecars like Istio useless.
+
diff --git a/content/WASM.md b/content/WASM.md
new file mode 100644
index 000000000..157cd8e59
--- /dev/null
+++ b/content/WASM.md
@@ -0,0 +1,6 @@
+# WASM
+#research 
+
+- [[Pods will run WASM binaries, not containers]]
+- [[AKS supports WASM out of the box]]
+
diff --git a/content/index.md b/content/index.md
index 8fe4d2a94..38dc9cd57 100644
--- a/content/index.md
+++ b/content/index.md
@@ -32,6 +32,7 @@ If you wish to get in touch with me, take a look at https://mischavandenburg.com
 * Tech
 	* [[Kubernetes]]
 	* [[Containers]]
+	* [[WASM]]
 	* [[Consultancy]]
 	* [[Infrastructure as Code]]
 	* [[Software Development]]