-
-
-
-
-
- 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-## Organizations
-
-
-
-
-
-
-
-
-
-
-
-
-## Individuals
-
-
-
-# Cloud
-
-If you do not want to self-host Coolify, there is a paid cloud version available: [app.coolify.io](https://app.coolify.io)
-
-For more information & pricing, take a look at our landing page [coolify.io](https://coolify.io).
-
-## Why should I use the Cloud version?
-The recommended way to use Coolify is to have one server for Coolify and one (or more) for the resources you are deploying. A server is around 4-5$/month.
-
-By subscribing to the cloud version, you get the Coolify server for the same price, but with:
-- High-availability
-- Free email notifications
-- Better support
-- Less maintenance for you
-
-# Recognitions
-
-
-
-
-
-
-
-
| 
|
-| 
| |
-
-# Repo Activity
-
-
-
-# Star History
-
-[](https://star-history.com/#coollabsio/coolify&Date)
+- WIP
\ No newline at end of file
diff --git a/RELEASE.md b/RELEASE.md
deleted file mode 100644
index bc159b0409..0000000000
--- a/RELEASE.md
+++ /dev/null
@@ -1,133 +0,0 @@
-# Coolify Release Guide
-
-This guide outlines the release process for Coolify, intended for developers and those interested in understanding how Coolify releases are managed and deployed.
-
-## Table of Contents
-- [Release Process](#release-process)
-- [Version Types](#version-types)
- - [Stable](#stable)
- - [Nightly](#nightly)
- - [Beta](#beta)
-- [Version Availability](#version-availability)
- - [Self-Hosted](#self-hosted)
- - [Cloud](#cloud)
-- [Manually Update to Specific Versions](#manually-update-to-specific-versions)
-
-## Release Process
-
-1. **Development on `next` or Feature Branches**
- - Improvements, fixes, and new features are developed on the `next` branch or separate feature branches.
-
-2. **Merging to `main`**
- - Once ready, changes are merged from the `next` branch into the `main` branch (via a pull request).
-
-3. **Building the Release**
- - After merging to `main`, GitHub Actions automatically builds release images for all architectures and pushes them to the GitHub Container Registry and Docker Hub with the specific version tag and the `latest` tag.
-
-4. **Creating a GitHub Release**
- - A new GitHub release is manually created with details of the changes made in the version.
-
-5. **Updating the CDN**
- - To make a new version publicly available, the version information on the CDN needs to be updated manually. After that the new version number will be available at [https://cdn.coollabs.io/coolify/versions.json](https://cdn.coollabs.io/coolify/versions.json).
-
-> [!NOTE]
-> The CDN update may not occur immediately after the GitHub release. It can take hours or even days due to additional testing, stability checks, or potential hotfixes. **The update becomes available only after the CDN is updated. After the CDN is updated, a discord announcement will be made in the Production Release channel.**
-
-## Version Types
-
-- Demo Notify => Send a demo notification to a given channel. -
-- php artisan app:demo-notify {channel} -
-*p?!IAt}F
z^^PR&lID`{QQ#x~KUPb
z2;`(;aY<#Zi