From e004671346b107fe6704cb170c10cf6386e73c57 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?andr=C3=A9s=20gonz=C3=A1lez?= Date: Fri, 11 Apr 2025 14:02:35 +0200 Subject: [PATCH] :books: Update Recommended storage info (#6275) --- .../getting-started/recommended-settings.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/technical-guide/getting-started/recommended-settings.md b/docs/technical-guide/getting-started/recommended-settings.md index 7544ecc414..0993b22341 100644 --- a/docs/technical-guide/getting-started/recommended-settings.md +++ b/docs/technical-guide/getting-started/recommended-settings.md @@ -1,13 +1,11 @@ --- -title: 1.1 Recommended Settings +title: 1.1 Recommended storage --- -# Recommended settings +# Recommended storage -To self-host Penpot, you’ll need a server with the following specifications: +Disk requirements depend on your usage, with the primary factors being database storage and user-uploaded files. -* **CPU:** 1-2 CPUs -* **RAM:** 4 GiB of RAM -* **Disk Space:** Disk requirements depend on your usage. Disk usage primarily involves the database and any files uploaded by users. +As a rule of thumb, start with a **minimum** database size of **50GB** to **100GB** with elastic sizing capability — this configuration should adequately support up to 10 editors. For environments with **more than 10 users**, we recommend adding approximately **5GB** of capacity per additional editor. -This setup should be sufficient for a smooth experience with typical usage (your mileage may vary). +Keep in mind that database size doesn't grow strictly proportionally with user count, as it depends heavily on how Penpot is used and the complexity of files created. Most organizations begin with this baseline and elastic sizing approach, then monitor usage patterns monthly until resource requirements stabilize.