Pricing update sites #2507
Pricing update sites #2507
Conversation
WalkthroughThe PR updates documentation and pricing UI copy across many files: removes dated informational notes, deletes the Scale plan page and removes Scale-plan rows/mentions (SLA, transactions, backups, platform pages), replaces many "Pro and Scale" references with "Pro", "Paid plan", or "Enterprise" as appropriate, adjusts Free pricing copy (separating "Unlimited Sites" and "5GB bandwidth"), renames bandwidth row labels in comparison tables, and refines wording around custom roles and upgrade options. No exported/public API entities or application logic were modified. Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/routes/pricing/+page.svelte (1)
193-193: Inconsistent terminology: "API bandwidth" should be "bandwidth".Line 193 still uses "2TB API bandwidth" while the Free plan (line 117) and comparison table headers were updated to use just "bandwidth" without the "API" prefix. This creates terminology inconsistency across the pricing page.
Apply this diff to maintain consistency:
- <li><span>2TB API bandwidth</span></li> + <li><span>2TB bandwidth</span></li>
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
src/routes/docs/advanced/platform/compute/+page.markdoc(3 hunks)src/routes/docs/advanced/platform/phone-otp/+page.markdoc(0 hunks)src/routes/pricing/+page.svelte(1 hunks)src/routes/pricing/compare-plans.svelte(2 hunks)
💤 Files with no reviewable changes (1)
- src/routes/docs/advanced/platform/phone-otp/+page.markdoc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build
- GitHub Check: tests
🔇 Additional comments (5)
src/routes/pricing/+page.svelte (1)
116-117: LGTM! Free plan features updated correctly.The split of bandwidth into "Unlimited Sites" and "5GB bandwidth" as separate line items aligns with the comparison table changes and improves clarity.
src/routes/pricing/compare-plans.svelte (2)
41-41: LGTM! Terminology simplified appropriately.Removing "API" prefix from bandwidth labels improves clarity and aligns with modern API terminology where bandwidth encompasses all data transfer.
Also applies to: 48-48
327-327: LGTM! Free tier Sites quota updated.Changing from "1 per project" to "Unlimited" aligns with the pricing card changes and removes an artificial constraint on the free tier.
src/routes/docs/advanced/platform/compute/+page.markdoc (2)
7-7: LGTM! Documentation simplified.Removing the specific date reference and generalizing to "paid plans" makes the documentation more maintainable.
25-25: Verify Scale plan compute eligibility and ensure documentation consistency.The investigation confirms a genuine inconsistency: the compute documentation (src/routes/docs/advanced/platform/compute/+page.markdoc, line 25) now states only "Pro" customers can customize compute specifications. However, the pricing comparison table (src/routes/pricing/compare-plans.svelte, lines 341–343, 355–358) shows Scale with identical GB-hours ("1,000 GB-hour / month") and compute options ("Up to 4 CPUs - 4GB RAM") as Pro. Additionally, the blog post on compute capabilities references both Pro and Scale users with the same 1,000 GB allocation.
Verify whether:
- Scale plan customers can actually customize compute specifications (matching the pricing table), or
- Scale is limited to default specs (matching the updated documentation)
Then update all affected documentation consistently across:
- src/routes/docs/advanced/platform/compute/+page.markdoc (lines 25, 49–51)
- src/routes/pricing/compare-plans.svelte (comparison table)
- Any related blog posts or changelog entries
|
|
||
| {% info title="Note" %} | ||
| Only customers on either Pro or Scale are able to change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise). | ||
| Only customers on either Pro can change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise). |
There was a problem hiding this comment.
Fix grammar error: "customers on either Pro" is incomplete.
The phrase "customers on either Pro" is grammatically incorrect. The word "either" requires an "or" alternative (e.g., "either X or Y").
Apply this diff to fix the grammar:
-Only customers on either Pro can change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise).
+Only customers on Pro can change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Only customers on either Pro can change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise). | |
| Only customers on Pro can change their specification from the default 512MB & 0.5 CPU option. For custom compute options please contact our [sales team](https://appwrite.io/contact-us/enterprise). |
🤖 Prompt for AI Agents
In src/routes/docs/advanced/platform/compute/+page.markdoc around line 25, the
phrase "customers on either Pro" is grammatically incorrect; replace it with a
correct construction such as "customers on Pro" or "customers on either the Pro
plan or [another plan]" — update the sentence to read clearly (for example:
"Only customers on the Pro plan can change their specification from the default
512MB & 0.5 CPU option. For custom compute options please contact our sales
team.") so the grammar is fixed and the meaning remains unchanged.
| { | ||
| title: 'Sites', | ||
| free: '1 per project', | ||
| free: 'Unlimited', |
There was a problem hiding this comment.
We need to check in with the Engineering team on this first, since we get errors on creating more than 1 site in the console at the moment
…n-documentation-587e Find Appwrite scale plan documentation
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/routes/docs/advanced/platform/database-reads-and-writes/+page.markdoc (1)
6-8: Outdated informational note.The info box states that updated pricing "will take effect on April 10th, 2025," but since today's date is October 22, 2025, this note is outdated and may confuse users.
Consider either removing this note entirely or updating it to reflect that the pricing is currently in effect:
-{% info title="Note" %} -Updated pricing will take effect on April 10th, 2025. Check out this [blog post](/blog/post/announcing-database-reads-and-writes-pricing) for more information. -{% /info %}
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
src/partials/resource-limits.md(1 hunks)src/routes/docs/advanced/platform/+page.markdoc(1 hunks)src/routes/docs/advanced/platform/database-reads-and-writes/+page.markdoc(1 hunks)src/routes/docs/advanced/platform/fair-use-policy/+page.markdoc(1 hunks)src/routes/docs/advanced/platform/image-transformations/+page.markdoc(1 hunks)src/routes/docs/advanced/platform/roles/+page.markdoc(1 hunks)src/routes/docs/advanced/platform/scale/+page.markdoc(0 hunks)src/routes/docs/advanced/platform/uptime-sla/+page.markdoc(0 hunks)src/routes/docs/advanced/security/pci/+page.markdoc(1 hunks)src/routes/docs/products/databases/backups/+page.markdoc(2 hunks)src/routes/docs/products/databases/transactions/+page.markdoc(0 hunks)
💤 Files with no reviewable changes (3)
- src/routes/docs/advanced/platform/uptime-sla/+page.markdoc
- src/routes/docs/products/databases/transactions/+page.markdoc
- src/routes/docs/advanced/platform/scale/+page.markdoc
✅ Files skipped from review due to trivial changes (2)
- src/routes/docs/advanced/platform/+page.markdoc
- src/routes/docs/advanced/platform/roles/+page.markdoc
🧰 Additional context used
🪛 LanguageTool
src/partials/resource-limits.md
[grammar] ~50-~50: Ensure spelling is correct
Context: ...an-reaching-resource-limits %} When an orgnization switches from a paid plan to the Free p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build
- GitHub Check: tests
🔇 Additional comments (7)
src/routes/docs/advanced/platform/database-reads-and-writes/+page.markdoc (1)
38-40: LGTM! Plan consolidation accurately reflected.The heading update from "Pro and Scale Plans" to "Pro Plan" correctly reflects the removal of the Scale tier and aligns with the broader platform documentation updates in this PR.
src/routes/docs/advanced/security/pci/+page.markdoc (1)
7-7: LGTM!The terminology update from "Pro and Scale plans" to "paid plans" aligns with the PR's broader plan structure changes and maintains clarity.
src/routes/docs/advanced/platform/image-transformations/+page.markdoc (1)
29-29: LGTM!The update to reference the pricing page for details is a good approach for maintainability, avoiding duplication of pricing information across documentation.
src/routes/docs/advanced/platform/fair-use-policy/+page.markdoc (1)
43-43: LGTM!The terminology update from "Pro and Scale plan users" to "Paid plan users" is consistent with the PR's plan structure changes.
src/routes/docs/products/databases/backups/+page.markdoc (3)
11-11: LGTM!The update to specify backups are available for "Pro and Enterprise customers" aligns with the PR's removal of the Scale plan.
18-18: LGTM!The update to indicate that custom backup policies are an Enterprise plan feature aligns with the PR's plan structure changes.
43-58: Confirm whether image reuse and terminology naming is intentional.The referenced image files exist and paths are correct:
static/images/docs/databases/dark/scale-policies.png✓static/images/docs/databases/scale-policies.png✓static/images/docs/databases/dark/scale-custom-policies.png✓static/images/docs/databases/scale-custom-policies.png✓No new enterprise-prefixed images were created. The images will display correctly.
However, a terminology mismatch remains: the image captions/alt text say "Enterprise plan" while the filenames reference "scale-". This appears intentional (reusing existing assets), but please confirm whether:
- The "scale-" images are appropriate for the Enterprise plan section, OR
- The images should have been renamed to align with updated terminology
| ## Switching to Free plan and reaching limits {% #switching-to-free-plan-reaching-resource-limits %} | ||
|
|
||
| When an orgnization switches from Pro or Scale plan to Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period. | ||
| When an orgnization switches from a paid plan to the Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period. |
There was a problem hiding this comment.
Fix spelling error.
There's a typo: "orgnization" should be "organization".
Apply this diff:
-When an orgnization switches from a paid plan to the Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period.
+When an organization switches from a paid plan to the Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| When an orgnization switches from a paid plan to the Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period. | |
| When an organization switches from a paid plan to the Free plan, the organization's projects will be able to take advantage of the existing limits until the end of the current billing period. |
🧰 Tools
🪛 LanguageTool
[grammar] ~50-~50: Ensure spelling is correct
Context: ...an-reaching-resource-limits %} When an orgnization switches from a paid plan to the Free p...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
In src/partials/resource-limits.md around line 50, there's a spelling typo:
"orgnization" should be corrected to "organization"; update the word to the
correct spelling in that sentence so it reads "When an organization switches
from a paid plan to the Free plan, the organization's projects will be able to
take advantage of the existing limits until the end of the current billing
period."
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.)
Summary by CodeRabbit
Documentation
Updates