Announces default deployment retention for Functions and Sites on Appwrite Cloud, effective November 5, 2026. Dated today, so users get two weeks of notice.

• Blog post default-deployment-retention: what changes on each plan, what Appwrite always keeps, how existing settings carry over, how to keep deployments for longer, and that self-hosted Appwrite is unchanged.
• Changelog entry 2026-10-21-1, linking to the post and reusing its cover.
• Cover: hand-built 2920x1644 cover, converted with generate:content-images. Manifests regenerated.

The post leads with storage: inactive deployments fill project storage, and many Free organizations reach their 2GB storage limit because of them. It says early and plainly that only inactive deployments are affected and that the active deployment is never deleted.

Plan values in the post

Enterprise starts from the Pro values, with a contact link for longer retention or a custom policy.

Behavior described

• The active deployment and any deployment a custom domain points to are never deleted.
• Functions and sites set to keep deployments forever move to the 30-day default.
• A retention window above the plan maximum is shortened to the maximum, and new values above it are rejected with deployment_retention_exceeded.
• A Server SDK update that leaves out deploymentRetention sets it back to 0, so the post tells readers to pass it on every update, and to use 1095 for the full 3 years (the Console presets stop at 2 years).
• On Free and Education, the 100 newest inactive deployments are kept; builds in progress and deployments behind a custom domain don't count.
• Age counts from when a deployment was created, so a long-running deployment is past the window as soon as a newer one replaces it. The post tells readers to set a longer window if they roll back to deployments like that.
• Deleting a deployment removes its source code, build output, and preview URL.
• Self-hosted Appwrite keeps retention off by default (0 to 36500 days).

Before merging

• Confirm November 5 is the enforcement date for every plan.
• The deployment retention sections in products/functions/deployments and products/sites/deployments still describe 0 as keeping deployments forever on every deployment. They also name an older Console path (Settings > Deployment retention; the card is now under Settings > Build > Retention). Update them on November 5, when enforcement starts, not before. The May announcement (announcing-deployment-retention) also says deployments can be kept forever; the new post doesn't link to it.

Test plan

• Rendered /blog/post/default-deployment-retention and /changelog on a local Console dev server: the table, carry-over list, FAQs, cover, and changelog card render correctly.
• bun run lint:content and bun run lint:removed-blog-links pass.
• Every internal link resolves in this branch.