From 4e4d96cc3d24257f362ad56e119c3ed8e693e634 Mon Sep 17 00:00:00 2001 From: jdv Date: Fri, 5 Dec 2025 15:42:10 +0100 Subject: [PATCH 1/3] premium upgrade page --- crowdsec-docs/sidebarsUnversioned.ts | 5 ++ .../unversioned/console/premium_upgrade.mdx | 48 +++++++++++++++++++ 2 files changed, 53 insertions(+) create mode 100644 crowdsec-docs/unversioned/console/premium_upgrade.mdx diff --git a/crowdsec-docs/sidebarsUnversioned.ts b/crowdsec-docs/sidebarsUnversioned.ts index a7df0c65..880a5fed 100644 --- a/crowdsec-docs/sidebarsUnversioned.ts +++ b/crowdsec-docs/sidebarsUnversioned.ts @@ -427,6 +427,11 @@ const sidebarsUnversionedConfig: SidebarConfig = { label: "🩺 Stack Health", id: "console/stackhealth", }, + { + type: "doc", + label: "🏅 Premium Upgrade", + id: "console/premium_upgrade", + }, ], remediationSideBar: [ { diff --git a/crowdsec-docs/unversioned/console/premium_upgrade.mdx b/crowdsec-docs/unversioned/console/premium_upgrade.mdx new file mode 100644 index 00000000..2dcfe2c6 --- /dev/null +++ b/crowdsec-docs/unversioned/console/premium_upgrade.mdx @@ -0,0 +1,48 @@ +--- +id: premium_upgrade +title: Premium Upgrade +description: Upgrade to CrowdSec Premium for enhanced security and commercial-grade features +--- + +import { Badge } from "@site/src/ui/badge"; + +## Why Upgrade to Premium? + +CrowdSec Premium features are designed for users who have **commercial usage** of the Console or organizations that want to **enhance the security posture** of their infrastructure. +While our Community Plan provides essential security monitoring capabilities, Premium unlocks advanced features that scale with your business needs and provide business-grade protection. + +Premium features bring the following benefits: + +- **Scalability**: + - Extra centralization and synchronization features + - Extended data retention + - Automatization and API access for large-scale deployments +- **Advanced Threat Detection & qualification**: + - Attack surge detection + - Premium proactive blocking with AI powered blocklists + - Background noise filtering + +Features comparison can be found in our [pricing page](https://app.crowdsec.net/pricing). + +## Optimal Premium Upgrade Setup + +When upgrading to a Premium plan, you may not want to upgrade every single Security Engine you monitor. It is common to have a mix of environments: +- **Production:** Requires Premium features (longer data retention, heavy API limits, organization-wide blocklists). +- **Dev / Test / Staging:** Can remain on the Free tier. + +Because the Premium Upgrade applies to an entire **Organization**, the optimal strategy is to separate your Security Engines into different contexts before subscribing. + +When you first a Console account your workspace is your "Personal Account". +As a community account you can create one extra organization for free. + +We recommend the following setup: +- If you have not already, create a new organization for your **Production** environment. +- Have your **Dev / Test / Staging** Security Engines remain in your **Personal Account** +- Have your **Production** Security Engines in the new **Production** organization. +- Upgrade the **Production** organization to **Premium**. + +To split your Security Engines into different organizations use either: +- The [Transfer feature](/u/console/security_engines/transfer_engine) from the Security Engine page. +- Or via `cscsli`, re-enroll your Security Engines in the desired organization with the `--overwrite` flag to force moving it to the new organization. + +After the transfer, the alerts will be reappearing in the new organization after a few minutes. From 9be4c3e3681d79756ee94e8c71ea0527f24c6198 Mon Sep 17 00:00:00 2001 From: jdv Date: Tue, 9 Dec 2025 09:46:14 +0100 Subject: [PATCH 2/3] typos fix --- .../unversioned/console/premium_upgrade.mdx | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/crowdsec-docs/unversioned/console/premium_upgrade.mdx b/crowdsec-docs/unversioned/console/premium_upgrade.mdx index 2dcfe2c6..638638cd 100644 --- a/crowdsec-docs/unversioned/console/premium_upgrade.mdx +++ b/crowdsec-docs/unversioned/console/premium_upgrade.mdx @@ -16,13 +16,13 @@ Premium features bring the following benefits: - **Scalability**: - Extra centralization and synchronization features - Extended data retention - - Automatization and API access for large-scale deployments -- **Advanced Threat Detection & qualification**: + - Automation and API access for large-scale deployments +- **Advanced Threat Detection & Qualification**: - Attack surge detection - - Premium proactive blocking with AI powered blocklists + - Premium proactive blocking with AI-powered blocklists - Background noise filtering -Features comparison can be found in our [pricing page](https://app.crowdsec.net/pricing). +A features comparison can be found on our [pricing page](https://app.crowdsec.net/pricing). ## Optimal Premium Upgrade Setup @@ -32,17 +32,17 @@ When upgrading to a Premium plan, you may not want to upgrade every single Secur Because the Premium Upgrade applies to an entire **Organization**, the optimal strategy is to separate your Security Engines into different contexts before subscribing. -When you first a Console account your workspace is your "Personal Account". -As a community account you can create one extra organization for free. +When you first create a Console account, your workspace is your "Personal Account". +As a community account, you can create one extra organization for free. We recommend the following setup: - If you have not already, create a new organization for your **Production** environment. -- Have your **Dev / Test / Staging** Security Engines remain in your **Personal Account** -- Have your **Production** Security Engines in the new **Production** organization. +- Keep your **Dev / Test / Staging** Security Engines in your **Personal Account**. +- Move your **Production** Security Engines to the new **Production** organization. - Upgrade the **Production** organization to **Premium**. -To split your Security Engines into different organizations use either: +To split your Security Engines into different organizations, use either: - The [Transfer feature](/u/console/security_engines/transfer_engine) from the Security Engine page. -- Or via `cscsli`, re-enroll your Security Engines in the desired organization with the `--overwrite` flag to force moving it to the new organization. +- Or via `cscli`, re-enroll your Security Engines in the desired organization with the `--overwrite` flag to force moving them to the new organization. -After the transfer, the alerts will be reappearing in the new organization after a few minutes. +After the transfer, the alerts will reappear in the new organization after a few minutes. From c5d84ba32648ae7dde81a77d4c5393413037a06f Mon Sep 17 00:00:00 2001 From: jdv Date: Tue, 9 Dec 2025 09:49:57 +0100 Subject: [PATCH 3/3] nano changes --- crowdsec-docs/unversioned/console/premium_upgrade.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crowdsec-docs/unversioned/console/premium_upgrade.mdx b/crowdsec-docs/unversioned/console/premium_upgrade.mdx index 638638cd..dc99f8e6 100644 --- a/crowdsec-docs/unversioned/console/premium_upgrade.mdx +++ b/crowdsec-docs/unversioned/console/premium_upgrade.mdx @@ -33,7 +33,7 @@ When upgrading to a Premium plan, you may not want to upgrade every single Secur Because the Premium Upgrade applies to an entire **Organization**, the optimal strategy is to separate your Security Engines into different contexts before subscribing. When you first create a Console account, your workspace is your "Personal Account". -As a community account, you can create one extra organization for free. +As a Community account, you can create one extra organization for free. We recommend the following setup: - If you have not already, create a new organization for your **Production** environment.