Conversation
Document the increase from 15m to 45m for Sites and Functions builds on Appwrite Cloud for Pro+ organizations, with Free and Starter remaining at 15m. Made-with: Cursor
Add a Compute comparison row (15m Free, 45m Pro+) and surface the same limits on the Free and Pro pricing cards. Made-with: Cursor
Made-with: Cursor
Add a Build timeouts section to Compute (Free 15m, Pro/Scale 45m, Enterprise custom) with links to execution vs request timeouts and self-hosted env vars. Cross-link from Functions, Sites, and deployments. Made-with: Cursor
Greptile SummaryThis PR documents and surfaces the build timeout increase from 15 minutes to 45 minutes for Pro/Scale/Enterprise plans across the changelog, compute docs, functions/sites docs, and pricing pages. All plan values are consistent across files except for one content error in the changelog entry.
Confidence Score: 4/5Safe to merge after fixing the "Starter" plan reference in the changelog entry. One P1 content inaccuracy: the changelog mentions a non-existent "Starter" plan, which will confuse users once published. All other changes are accurate and consistent across files. src/routes/changelog/(entries)/2026-04-17.markdoc — incorrect "Starter" plan name on line 7. Important Files Changed
Reviews (1): Last reviewed commit: "docs: document Cloud build timeouts by p..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| date: 2026-04-17 | ||
| --- | ||
|
|
||
| We have raised the **maximum build duration** for [Sites](/docs/products/sites) and [Functions](/docs/products/functions) on Appwrite Cloud from **15 minutes to 45 minutes** for organizations on the **Pro plan and above**. Free and Starter organizations keep the **15-minute** build limit, so the longer window is an explicit benefit of upgrading when your workloads need it. |
There was a problem hiding this comment.
The text says "Free and Starter organizations keep the 15-minute build limit," but Appwrite's current plan tiers are free, pro, scale, and enterprise — there is no "Starter" plan. This appears in the compare-plans.svelte type definition and every data row. Mentioning a fictitious tier in a published changelog will confuse users who search for it.
| We have raised the **maximum build duration** for [Sites](/docs/products/sites) and [Functions](/docs/products/functions) on Appwrite Cloud from **15 minutes to 45 minutes** for organizations on the **Pro plan and above**. Free and Starter organizations keep the **15-minute** build limit, so the longer window is an explicit benefit of upgrading when your workloads need it. | |
| We have raised the **maximum build duration** for [Sites](/docs/products/sites) and [Functions](/docs/products/functions) on Appwrite Cloud from **15 minutes to 45 minutes** for organizations on the **Pro plan and above**. Free plan organizations keep the **15-minute** build limit, so the longer window is an explicit benefit of upgrading when your workloads need it. |
| - [Express builds](/changelog/entry/2024-08-10) for quicker deployments, resulting in reduced wait times and smoother workflows | ||
| - Longer [build timeouts](/docs/advanced/platform/compute#build-timeouts) (45 minutes vs 15 minutes on Free; Enterprise is custom) | ||
| - Customizable [build and runtime specifications](/docs/advanced/platform/compute) for CPU and memory on each function | ||
| {% /info %} No newline at end of file |
There was a problem hiding this comment.
The diff shows \ No newline at end of file for this file (and the same applies to src/routes/docs/products/sites/deployments/+page.markdoc). POSIX tools and some linters expect a trailing newline; adding one keeps the files consistent with the rest of the repo.
| {% /info %} | |
| - Customizable [build and runtime specifications](/docs/advanced/platform/compute) for CPU and memory on each function | |
| {% /info %} |
1 participant
What does this PR do?
(Provide a description of what this PR does.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)
Related PRs and Issues
(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)
Have you read the Contributing Guidelines on issues?
(Write your answer here.)