Fledge v0.7.2.1 "Perch"

Make account-plan allowances actionable: a subscription can explicitly unlock fixed-size server creation, with authorization, choices and limits enforced by the API.

A perch is a place for a bird to settle. In this release, an account plan can give a customer permission and a carefully bounded place to create a server of their own.

Highlights

• Account-plan server creation. A new self-service mode lets customers create fixed-size servers only when a qualifying account plan explicitly grants May create servers.
• Plan-scoped choices. The existing template, location, resource and effective-limit rules still apply. Customers cannot change the fixed memory, CPU or disk size in this mode.
• Server-plan behavior stays distinct. The existing server-plan-only mode is for buying or claiming preset servers; it does not advertise or permit self-created servers.
• Entitlements follow subscriptions. Trialing, active and payment-grace (past_due) account plans grant access. Suspended, canceled and terminated subscriptions do not. Ending a plan does not delete customer-owned servers.

Added and changed

• Added Account plans to Settings → Customers & billing → Server access. It is separate from Server plans and Free choice.
• Account-plan creation requires both an explicit plan-level selfCreate grant and no effective customer-level denial while limits are enforced. The global limits switch and warn-only mode retain their existing behavior.
• The feature API now reports whether the signed-in customer can create servers; the Servers page uses that result for its create action.
• The server options API now reports the mode, whether a plan is required, and whether customers may rename their servers. It does not offer create templates in Off or Server plans mode.
• In account-plan mode, server resources come from the released template defaults. Plan allowances continue to constrain templates and locations; the normal placement, account, rate and limits checks still run on the server.
• Existing customers' created servers remain customer-owned when an account-plan subscription ends; they are not removed as if they were subscription-provisioned server-plan servers.
• Administrator Settings is grouped into top-level sections, with customer/billing and panel settings split into tabs. Switching tabs preserves unsaved form state, and existing billing and store links select their section.
• No database migration or node-agent feature change is required. The version stamp is updated across the application and release artifacts.

Upgrade

1. Back up PostgreSQL and follow the regular upgrade guide.
2. Existing Off, Server plans and Free choice settings remain unchanged. To enable account-plan creation, publish the templates and locations you want, define fixed resource defaults, enable May create servers on an account plan, and select Account plans in self-service settings.
3. Review the account plan's limits and customer overrides. Ending the qualifying subscription revokes the grant but does not delete servers already created.

Verified

• API TypeScript check.
• Web TypeScript check and production build.
• Updater API smoke test.
• API unit tests (35) and Rookery settings tests (8).
• Billing integration test against disposable PostgreSQL (508 assertions), including purchase-to-creation, no grant, fixed resources, location restrictions, customer-level denial, payment grace, suspension, cancellation and termination.
• Rookery integration suite against disposable PostgreSQL (282 assertions).
• Documentation generation and VitePress production build.

Known limits

• Account-plan self-creation uses published template defaults; per-customer custom resource sizing is available only in Free choice mode.
• The plan grants access to create, not ownership under the subscription. Existing self-created servers are not automatically deleted or resized if the plan ends.