Skip to content

Commit 371c14d

Browse files
author
jdv
committed
updated page optimal setup
1 parent 6bd355b commit 371c14d

1 file changed

Lines changed: 220 additions & 15 deletions

File tree

‎crowdsec-docs/unversioned/console/premium_upgrade/optimal_setup.mdx‎

Lines changed: 220 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -4,23 +4,228 @@ title: Optimal Premium Upgrade Setup
44
description: Best practices for setting up your Premium upgrade
55
---
66

7-
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:
8-
- **Production:** Requires Premium features (longer data retention, heavy API limits, organization-wide blocklists).
9-
- **Dev / Test / Staging:** Can remain on the Free tier.
7+
import { FeatureCard } from '@site/src/components/premium-upgrade/feature-card';
108

11-
Because the Premium Upgrade applies to an entire **Organization**, the optimal strategy is to separate your Security Engines into different contexts before subscribing.
9+
<div className="p-6 rounded-xl bg-gradient-to-r from-primary/10 to-primary/5 border border-solid border-primary/20 mb-8">
1210

13-
When you first create a Console account, your workspace is your "Personal Account".
14-
As a Community account, you can create one extra organization for free.
11+
## 💡 Why Organize Before Upgrading?
1512

16-
We recommend the following setup:
17-
- If you have not already, create a new organization for your **Production** environment.
18-
- Keep your **Dev / Test / Staging** Security Engines in your **Personal Account**.
19-
- Move your **Production** Security Engines to the new **Production** organization.
20-
- Upgrade the **Production** organization to **Premium**.
13+
Premium upgrades apply to an **entire Organization**. You may not want Premium features for all environments—typically only **Production** needs extended retention, higher quotas, and advanced protection.
2114

22-
To split your Security Engines into different organizations, use either:
23-
- The [Transfer feature](/u/console/security_engines/transfer_engine) from the Security Engine page.
24-
- Or via `cscli`, re-enroll your Security Engines in the desired organization with the `--overwrite` flag to force moving them to the new organization.
15+
By organizing your Security Engines **before** upgrading, you save costs and keep your infrastructure organized.
2516

26-
After the transfer, the alerts will reappear in the new organization after a few minutes.
17+
</div>
18+
19+
---
20+
21+
## Common Multi-Environment Setup
22+
23+
Most teams have a mix of environments with different security requirements:
24+
25+
<div className="grid grid-cols-1 md:grid-cols-2 gap-4 mb-8">
26+
27+
<div className="border-2 border-solid border-primary/30 rounded-lg p-6 bg-card">
28+
29+
### 🔥 Production Environments
30+
31+
**Needs Premium:**
32+
33+
- Extended alert retention (12 months)
34+
- Higher alert quotas (millions/month)
35+
- Organization-wide blocklists
36+
- CTI API access for SIEM integration
37+
- Threat Forecast blocklists
38+
- Multi-seat team access
39+
40+
</div>
41+
42+
<div className="border border-solid border-border rounded-lg p-6 bg-card">
43+
44+
### 🧪 Dev / Test / Staging
45+
46+
**Community is sufficient:**
47+
48+
- Basic alert monitoring (500/month)
49+
- Short retention (2 months)
50+
- Community blocklists (3k IPs)
51+
- Individual engine management
52+
- Single-user access
53+
54+
</div>
55+
56+
</div>
57+
58+
---
59+
60+
## Recommended Setup Strategy
61+
62+
<div className="grid grid-cols-1 md:grid-cols-3 gap-4 mb-8 text-sm">
63+
64+
<div className="border border-solid border-border rounded-lg p-6 bg-card text-left">
65+
66+
### 1️⃣ Create Production Organization
67+
68+
Create a new organization specifically for your Production environment.
69+
70+
**Community accounts** get **1 extra organization for free** (beyond your Personal Account).
71+
72+
[Learn about Organizations →](/u/console/organizations/intro)
73+
74+
</div>
75+
76+
<div className="border border-solid border-border rounded-lg p-6 bg-card text-left">
77+
78+
### 2️⃣ Organize Your Engines
79+
80+
- **Personal Account:** Keep Dev/Test/Staging engines here (Community tier)
81+
- **Production Org:** Transfer Production engines to the new organization
82+
83+
You can transfer engines in two ways:
84+
- Console: [Transfer feature](/u/console/security_engines/transfer_engine)
85+
- CLI: Re-enroll with `cscli`
86+
using `--overwrite` flag
87+
88+
</div>
89+
90+
<div className="border-2 border-solid border-primary/30 rounded-lg p-6 bg-card text-left">
91+
92+
### 3️⃣ Upgrade Production Only
93+
94+
Upgrade **only the Production organization** to Premium.
95+
96+
Your Dev/Test/Staging environments remain on Community tier with no additional cost.
97+
98+
✅ Alerts reappear in the new organization within minutes
99+
100+
</div>
101+
102+
</div>
103+
104+
---
105+
106+
## Step-by-Step: Splitting Your Engines
107+
108+
### Option 1: Transfer via Console UI
109+
110+
<div className="border border-solid border-border rounded-lg p-6 bg-card mb-4">
111+
112+
**Best for:** Quick transfers of individual or small batches of engines
113+
114+
1. Navigate to **Security Engines** page in Console
115+
2. Select the engine(s) you want to transfer
116+
3. Use the **Transfer** feature to move them to your Production organization
117+
4. Confirm the transfer
118+
119+
[Transfer Feature Documentation →](/u/console/security_engines/transfer_engine)
120+
121+
</div>
122+
123+
### Option 2: Re-enroll via `cscli`
124+
125+
<div className="border border-solid border-border rounded-lg p-6 bg-card mb-4">
126+
127+
**Best for:** Bulk transfers, automation, or infrastructure-as-code deployments
128+
129+
```bash
130+
# Get enrollment key from your Production organization
131+
# Console → Organizations → Production → Enrollment Keys
132+
133+
# Re-enroll the Security Engine with --overwrite flag
134+
cscli console enroll <ENROLLMENT_KEY> --overwrite
135+
```
136+
137+
The `--overwrite` flag forces the engine to move to the new organization, even if already enrolled elsewhere.
138+
139+
</div>
140+
141+
---
142+
143+
## Example Organizational Structure
144+
145+
<div className="border-l-4 border-solid border-primary p-6 bg-card mb-6">
146+
147+
**Before Organizing (All in Personal Account):**
148+
149+
- 10 Production servers (web, API, database)
150+
- 5 Staging servers
151+
- 3 Dev laptops
152+
153+
**After Organizing:**
154+
155+
**Personal Account (Community - Free):**
156+
- 5 Staging servers
157+
- 3 Dev laptops
158+
159+
**Production Organization (Premium - Paid):**
160+
- 10 Production servers
161+
- Full Premium features
162+
- Team collaboration with 3 seats
163+
- Extended retention and quotas
164+
165+
</div>
166+
167+
---
168+
169+
## Benefits of This Approach
170+
171+
<div className="grid grid-cols-1 md:grid-cols-2 gap-4 mb-8">
172+
173+
<FeatureCard
174+
title="Cost Optimization"
175+
metric="Save 60-80%"
176+
category="scale"
177+
description="Only pay for Premium where you need it. Dev/Test environments remain free on Community tier."
178+
/>
179+
180+
<FeatureCard
181+
title="Clear Separation"
182+
metric="Zero confusion"
183+
category="scale"
184+
description="Production and non-production environments are cleanly separated, reducing noise and improving security posture visibility."
185+
/>
186+
187+
<FeatureCard
188+
title="Flexible Scaling"
189+
metric="Grow as needed"
190+
category="scale"
191+
description="Add more organizations later (MSPs can create unlimited orgs). Start simple, expand when required."
192+
/>
193+
194+
<FeatureCard
195+
title="No Downtime"
196+
metric="Seamless transfer"
197+
category="monitoring"
198+
description="Alerts reappear in new organization within minutes. No disruption to security monitoring."
199+
/>
200+
201+
</div>
202+
203+
---
204+
205+
## When NOT to Separate
206+
207+
You may want **all** engines in a single Premium organization if:
208+
209+
- You need extended retention across **all environments** for compliance
210+
- Your team investigates attacks in staging/dev environments regularly
211+
- You want centralized allowlists and blocklists everywhere
212+
- You're an MSP managing multiple client environments (use [Multi-Organization](/u/console/premium_upgrade/features_overview) instead)
213+
214+
---
215+
216+
## Next Steps
217+
218+
<div className="p-6 rounded-xl bg-gradient-to-r from-primary/10 to-primary/5 border border-solid border-primary/20">
219+
220+
### Ready to upgrade?
221+
222+
1. **Organize** your Security Engines across Personal Account and Production Organization
223+
2. **Upgrade** the Production organization to Premium
224+
3. **Test** Premium features during your trial period ([Testing Guide →](/u/console/premium_upgrade/testing_premium))
225+
226+
<div style={{display: 'flex', gap: '1rem', marginTop: '1.5rem', flexWrap: 'wrap'}}>
227+
<a href="https://app.crowdsec.net/pricing" className="button button--primary button--lg">View Pricing →</a>
228+
<a href="/u/console/premium_upgrade/testing_premium" className="button button--secondary button--lg">Testing Premium →</a>
229+
</div>
230+
231+
</div>

0 commit comments

Comments
 (0)