diff --git a/content/2021-11-05-aio-deprecation.md b/content/2021-11-05-aio-deprecation.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d07115e7acfaea4a436ffb9a52765b98fddeba2
--- /dev/null
+++ b/content/2021-11-05-aio-deprecation.md
@@ -0,0 +1,36 @@
+Title: Deprecation: All in One Container
+Date: 2021-11-05 13:48
+Category: Announcement
+Slug: deprecation-all-in-one-container
+Authors: Georg
+Summary: The All in One Container Deployment method is now deprecated and wont be supported in the future.
+
+After several discussions and some consideration we decided to deprecate the All-In-One-Container Docker
+deployment method. The reasons for this will be explained in this blog post. But at first I want to make
+sure you don't panic! You are probably running the All-In-One-Container for your Funkwhale instance. But we 
+won't let you alone with this!
+
+## We will support your migration!
+
+At first, there will be builds of the AIO-Container for the next releases, at least the 1.3 series will 
+still be available for you without any change. Secondly, we will provide a guide how to migrate your
+installation to the multi container deployment. Thirdly, if you are experiencing any troubles with this,
+we will provide some support using our chat rooms or forums. Hopefully this way we can manage this together :)
+
+## Reasons
+
+There are several reasons for this decision and I'll try to explain them here.
+
+Funkwhale has a quite broad feature set and several deployment methods. Its hard to maintain all this. We do 
+think its important to cover as much use cases as possible, but there are some limits. The AIO-Container
+previously was maintained by @thetarkus. Sadly they seemed to stop working on this and with some of our updates
+the builds failed. We took over the project to make sure the builds are working again, but we don't have the 
+resources to maintain this in the long-term. We want to focus on proper support of the multi container and ansible
+setup and spend more time on improving Funkwhale itself.
+
+On a technical level the AIO-Container is somehow against the idea of a Docker deployment. Usually each services
+lives in its own container, which allows scaling and is quite robust against a fail of the hole stack. This method
+is supported by our multi container setup and works quite well.
+
+If you have any questions or want to help creating a migration guide, get in touch in our 
+[Forum](https://forum.funkwhale.audio/d/60-all-in-one-container-deprecation).