diff --git a/README.md b/README.md
index b28c3c6..ace4ad2 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,13 @@ Presently it can inject failures into **system calls** by attaching kprobes to t
 ## What's it for?
 Minderbinder aims to make it easy to generically inject failures into processes. At the moment you can write a config.yaml that describes the failures to inject and the processes to inject them into, start minderbinder, and see what happens. 
 
+<details>
+<summary>Video demo</summary>
+	
+[h265.webm](https://github.com/user-attachments/assets/73cc8c3e-c447-4e0f-95c4-2e15d3f5fe70)
+
+</details>
+
 ## Running Minderbinder
 Check out [config.yaml](config.yaml) for a complete example. Minderbinder supports two different interventions - `syscall` and `outgoing_network`:
 
@@ -81,4 +88,4 @@ func TestYourAPIHandler_DownstreamFailure(t *testing.T) {
 
 This gives us a mechanism to test our application and services resiliance in the face of failures. Traditionally we would do this either by extensively stubbing _all_ the interesting interfaces around the application and injecting failures, or, using some chaos engineering tool to inject failures into the entire aggregate system in a deployed cloud environment. Because Minderbinder leverages eBPF for the failure injection, the code needed for each supported language would be straightforward, as it would simply have to configure the native minderbinder component.
 
-t
\ No newline at end of file
+t