docs: add autoscaling to free tier

neondatabase · Jul 29, 2024 · 10c790f · 10c790f
1 parent 5169487
commit 10c790f
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/content/docs/ai/ai-scale-with-neon.md b/content/docs/ai/ai-scale-with-neon.md
@@ -24,7 +24,7 @@ In Neon, scaling vertically is a matter of selecting the desired compute size. N
 | 9                  | 9    | 36 GB | 604 MB               |
 | 10                 | 10   | 40 GB | 671 MB               |
 
-See [Edit a compute](/docs/manage/endpoints#edit-a-compute) to learn how to configure your compute size. Available compute sizes differ according to your Neon plan. The Neon Free Tier supports computes with 0.25 vCPU and 1 GB RAM. The Launch plan offers compute sizes up to 4 vCPU with 16 GB RAM. Larger computes are available on the Scale plan. See [Neon plans](/docs/introduction/plans).
+See [Edit a compute](/docs/manage/endpoints#edit-a-compute) to learn how to configure your compute size. Available compute sizes differ according to your Neon plan. The Neon Free Tier supports computes starting at 0.25 vCPU with 1 GB RAM, up to 2 vCPU with 8 GB RAM with autoscaling enabled. The Launch plan offers compute sizes up to 4 vCPU with 16 GB RAM. Larger computes are available on the Scale plan. See [Neon plans](/docs/introduction/plans).
 
 To optimize `pgvector` index build time, you can increase the `maintenance_work_mem` setting for the current session beyond the preconfigured default shown in the table above with a command similar to this:
 

diff --git a/content/docs/get-started-with-neon/production-checklist.md b/content/docs/get-started-with-neon/production-checklist.md
@@ -40,7 +40,7 @@ In a development environment, your application may function perfectly with a sma
 
 In Neon, your compute size determines the amount of vCPU and memory your database has to work with. Neon supports computes up to 10 Compute Units (CUs) in size. Larger computes provide more memory. The compute sizes that are available to you depend on your [Neon plan](/docs/introduction/plans):
 
-- **Free Tier**: 0.25 CUs (0.25 vCPU, 1 GB RAM)
+- **Free Tier**: Starting at a fixed 0.25 CUs (0.25 vCPU, 1 GB RAM), up to 2 CU (2 vCPU, 8 GRM RAM) with autoscaling enabled
 - **Launch**: Up to 4 CUs (4 vCPU, 16 GB RAM)
 - **Scale**: Up to 10 CUs (10 vCPU, 40 GB RAM)
 - **Enterprise**: Larger sizes

diff --git a/content/docs/introduction/extra-usage.md b/content/docs/introduction/extra-usage.md
@@ -15,7 +15,7 @@ This table provides an overview of plan fees with allowances for storage, comput
 
 | Plan       | Monthly Fee | Storage Allowance | Compute Allowance                                                                                     | Project Allowance |
 | ---------- | ----------- | ----------------- | ----------------------------------------------------------------------------------------------------- | ----------------- |
-| Free Tier  | $0          | 0.5 GiB           | Always-available default branch compute, 5 compute hours (20 _active hours_)/month on branch computes | 1 project         |
+| Free Tier  | $0          | 0.5 GiB           | 191.9 default compute hours (24/7 at 0.25 CU), 5 extra shared hours/month for branch computes | 1 project         |
 | Launch     | $19         | 10 GiB            | 300 compute hours (1,200 _active hours_)/month                                                        | 10 projects       |
 | Scale      | $69         | 50 GiB            | 750 compute hours (3,000 _active hours_)/month                                                        | 50 projects       |
 | Enterprise | Custom      | Custom            | Custom                                                                                                | Custom            |

diff --git a/content/docs/introduction/monitor-usage.md b/content/docs/introduction/monitor-usage.md
@@ -46,7 +46,7 @@ The peak usage triangle indicates the highest usage level reached for that metri
 - **Compute** usage is tracked in **compute hours**. A compute hour is 1 active hour for a compute with 1 vCPU. For a compute with .25 vCPU, it takes 4 _active hours_ to use 1 compute hour. On the other hand, if your compute has 4 vCPUs, it takes only 15 minutes to use 1 compute hour.
 
   <Admonition type="note">
-  On the Free Tier, the [default branch](/docs/reference/glossary#default-branch) compute is a 0.25 vCPU compute that is always available, so allowances do not apply to your default branch. You can run your 0.25 vCPU compute on the Free Tier 24/7. Only branch computes on the Free Tier have an allowance, which is the 5 compute hour/month allowance that Free Tier users see on the **Billing** page. On the Free Tier, this is actually 20 hours of usage because the compute size on the Free Tier is 0.25 vCPU. You cannot increase the compute size on the Free Tier.
+  On the Free Tier, [default branch](/docs/reference/glossary#default-branch) compute starts at 0.25 vCPU and can run 24/7, up to a total of 191.9 compute hours per month. Autoscaling up to 2 vCPU with 8 GB RAM is available for extra performance during peak times, though it may affect 24/7 availability depending on your usage patterns. Non-default branches share an additional 5 compute hour/month allowance.
   </Admonition>
 
 - **Storage** includes your data size and history. Neon maintains a history of changes to support branching-related features such as [point-in-time restore](/docs/reference/glossary#point-in-time-restore). The Launch plan supports up to 7 days of history retention, and the Scale plan supports up to 30 days. Keep in mind that history retention increases storage. More history requires more storage. To manage the amount of history you retain, you can configure the history retention setting for your project. See [Configure history retention](/docs/manage/projects#configure-history-retention).

diff --git a/content/docs/introduction/plans.md b/content/docs/introduction/plans.md
@@ -41,7 +41,7 @@ The Free Tier includes the following usage allowances:
 | **Branches**               | 10 branches                                                                                                                                            |
 | **Databases**              | Unlimited                                                                                                                                              |
 | **Storage**                | 0.5 GiB                                                                                                                                                |
-| **Compute**                | Always-available default branch compute, 5 compute hours (20 _active hours_)/month on branch computes. Free Tier computes have 0.25 vCPU with 1GB RAM. |
+| **Compute**                | 24/7 database at 0.25 CU. Autoscaling up to 2 vCPU with 8 GB RAM available. Your default branch includes 191.9 compute hours per month. All other branches share a 5-hour compute allowance per month. |
 | **Data transfer (Egress)** | 5 GB per month                                                                                                                                         |
 
 <Admonition type="tip" title="What are active hours and compute hours?">
@@ -68,7 +68,7 @@ The Free Tier includes the following usage allowances:
 For a complete list of features, refer to the **detailed plan comparison** on the [Neon pricing](https://neon.tech/pricing) page.
 
 <Admonition type="tip" title="Free Tier Compute Allowances">
-On the Free Tier, your default branch compute is always available — it will never be suspended, which means you can always access the data on the default branch in your Neon project. Branch computes have 20 [active hours](/docs/reference/glossary#active-time) (5 [compute hours](/docs/reference/glossary#compute-hour)) per month. If your branch computes exceed this allowance, they are suspended until the allowance resets at the beginning of the month. You can monitor branch compute hours on the [Billing page](/docs/introduction/manage-billing#view-the-billing-page) in the Neon Console. The compute hour allowance for branch computes resets at the beginning of each month. For instance, if you enrolled in the Neon Free Tier in January, the allowance for branch computes resets on February 1st.
+On the Free Tier, your default branch compute can run 24/7 at 0.25 CU. If you enable autoscaling, your compute can scale up to 2 vCPU with 8 GB RAM providing additional resources during peak times to improve performance. Note that enabling autoscaling may affect 24/7 availability depending on your usage patterns. Any new non-default branches you create share an additional 5 compute hours per month. If you exceed either compute allowance, that compute is suspended until your allowance resets at the beginning of the month. For example, if you signed up for the Free Tier in January, your compute allowance resets on February 1st. The compute hour allowance for your default branch is 191.9 hours per month.
 </Admonition>
 
 ## Launch