Skip to content

Announce new default build spec #3098

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adityaoberai wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Announce new default build spec #3098

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/routes/changelog/(entries)/2026-07-14.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
layout: changelog
title: Upgraded default build resources for Sites and Functions
date: 2026-07-14
---

We have upgraded the default build specification for Appwrite Sites and Functions on Cloud. Every deployment build now runs with **2 CPU cores and 2GB of memory**, replacing the previous 0.5 CPU and 512MB default. Lower build specifications have been removed.

The new default applies to all plans, including Free, and requires no configuration changes. Expect faster dependency installs, compilation, and bundling across your sites and functions. Runtime specifications are unaffected by this change.

@greptile-apps greptile-apps Bot Jul 13, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Free plan GB-hour consumption not mentioned

The changelog says the change "requires no configuration changes," which is accurate, but it omits the billing side-effect for Free plan users. Build GB-hours are calculated as memory (GB) × build duration. Moving from 512 MB (0.5 GB) to 2 GB quadruples the GB-hour rate during builds — even if builds finish faster, users whose builds are memory-bound rather than CPU-bound may not see proportional speed gains and could exhaust their 100 GB-hour Free plan budget faster than before. A brief note (e.g., "Free plan build GB-hour consumption may increase; faster builds typically offset this") would set correct expectations.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: src/routes/changelog/(entries)/2026-07-14.markdoc
Line: 9

Comment:
**Free plan GB-hour consumption not mentioned**

The changelog says the change "requires no configuration changes," which is accurate, but it omits the billing side-effect for Free plan users. Build GB-hours are calculated as memory (GB) × build duration. Moving from 512 MB (0.5 GB) to 2 GB quadruples the GB-hour rate during builds — even if builds finish faster, users whose builds are memory-bound rather than CPU-bound may not see proportional speed gains and could exhaust their 100 GB-hour Free plan budget faster than before. A brief note (e.g., "Free plan build GB-hour consumption may increase; faster builds typically offset this") would set correct expectations.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code Fix in Codex


{% arrow_link href="/docs/advanced/billing/compute" %}
Learn more about compute specifications
{% /arrow_link %}
25 changes: 14 additions & 11 deletions src/routes/docs/advanced/billing/compute/+page.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,19 +10,22 @@ These options help you tune performance and cost: for example, a large install o

# Specifications {% #specifications %}

Appwrite Cloud offers the following specification tiers. The same tiers are available for **build** and **runtime** independently on each function or site:

| Memory | CPU cores | Hourly usage |
|--------|-----------|--------------|
| 512MB | 0.5 | 0.25 |
| 512MB | 1 | 0.5 |
| 1GB | 1 | 1 |
| 2GB | 2 | 4 |
| 4GB | 2 | 8 |
| 4GB | 4 | 16 |
Appwrite Cloud offers the following specification tiers. You can set **build** and **runtime** specifications independently on each function or site:

| Memory | CPU cores | Hourly usage | Available for |
|--------|-----------|--------------|-------------------|
| 512MB | 0.5 | 0.25 | Runtime |
| 512MB | 1 | 0.5 | Runtime |
| 1GB | 1 | 1 | Runtime |
| 2GB | 2 | 4 | Build and runtime |
| 4GB | 2 | 8 | Build and runtime |
| 4GB | 4 | 16 | Build and runtime |
| 4GB | 8 | 32 | Build and runtime |
| 8GB | 4 | 32 | Build and runtime |
| 8GB | 8 | 64 | Build and runtime |

{% info title="Note" %}
On Appwrite Cloud, **Pro** plan organizations can change build and runtime specifications from the default 512MB and 0.5 CPU. The Free plan uses the default. For custom compute options, contact our [sales team](https://appwrite.io/contact-us/enterprise).
On Appwrite Cloud, **Pro** plan organizations can change build and runtime specifications from the defaults: 2GB and 2 CPU for builds, and 512MB and 0.5 CPU for runtime. The Free plan uses the defaults. For custom compute options, contact our [sales team](https://appwrite.io/contact-us/enterprise).
{% /info %}

# Build timeouts {% #build-timeouts %}
Expand Down
2 changes: 1 addition & 1 deletion src/routes/docs/products/functions/functions/+page.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ These are terminal commands that will be executed in the runtime containers in t

## Resource limits {% #resource-limits %}

Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while your deployment is being built and packaged; the runtime spec applies to each function execution. Both use the same CPU and memory tiers on Cloud. This lets you align compute with heavy dependency installs or compilation without over-provisioning every invocation.
Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while your deployment is being built and packaged; the runtime spec applies to each function execution. On Cloud, builds run on at least 2 CPU cores and 2GB of memory. This lets you align compute with heavy dependency installs or compilation without over-provisioning every invocation.

On Appwrite Cloud, customizing specifications requires the **Pro** plan. See [Compute](/docs/advanced/billing/compute) for tiers, GB-hours, and pricing.

Expand Down
2 changes: 1 addition & 1 deletion src/routes/docs/products/sites/develop/+page.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ The default timeout is set at `15 seconds` and the maximum value possible is `30

# Resource limits {% #resource-limits %}

Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while dependencies are installed and your site is built for deployment; the runtime spec applies when your site serves traffic, including server-side rendering (SSR). Both use the same CPU and memory tiers on Cloud.
Under **Settings** - **Resource limits**, you can set **build** and **runtime** specifications independently. The build spec applies while dependencies are installed and your site is built for deployment; the runtime spec applies when your site serves traffic, including server-side rendering (SSR). On Cloud, builds run on at least 2 CPU cores and 2GB of memory.

On Appwrite Cloud, customizing specifications requires the **Pro** plan. See [Compute](/docs/advanced/billing/compute) for tiers, GB-hours, and pricing.

Expand Down
Loading