chore: compute Instances entitlements

[ignaciodob]

This PR changes the way that we check if the user is allowed to change the compute instance of a project from checking if the user is on the Free Plan to an entitlement check.

Testing

• Head over to /project/_/settings/compute-and-disk
• Assert that an Org on the Free Plan cannot change the Compute Size.
• Assert that an Org on the Free Plan sees the "Compute and Disk configuration is not available on the Free Plan" notice
• Assert that an Org on the Pro Plan and above can change the Compute Size.

Optional testing with backend feature catalog changes

• Run your local backend local environment and local studio
• Modify this line to enabled: true to enable updating compute sizes on the Free Plan.
• Assert that you're able to select a compute size update on the frontend

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
studio-self-hosted	Ready	Preview	Comment	Oct 28, 2025 4:22pm
studio-staging	Ready	Preview	Comment	Oct 28, 2025 4:22pm

6 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
studio	Ignored			Oct 28, 2025 4:22pm
cms	Skipped			Oct 28, 2025 4:22pm
design-system	Skipped			Oct 28, 2025 4:22pm
docs	Skipped			Oct 28, 2025 4:22pm
ui-library	Skipped			Oct 28, 2025 4:22pm
zone-www-dot-com	Skipped			Oct 28, 2025 4:22pm

[supabase]

This pull request has been ignored for the connected project xguihxuzqibwxjnimxev because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coveralls]

coverage: 70.088%. first build
when pulling b17cd53 on chore/compute-instances-entitlements
into 406ada7 on master.

[github-actions]

Studio E2E Results

Note: No JSON report found or parse error.

Artifacts: https://github.com/supabase/supabase/actions/runs/18881577863

Last updated: Tuesday 28, October, 2025 16:22:31 (UTC)

[kevcodez]

Before starting to actually use entitlements in the frontend, let's ensure two things

• On a plan change or any change that would invalidate entitlements, we need to invalidate the react-query cache
• Have a higher stale time to avoid refetching (let's do 30m-60m)

[ignaciodob]

Before starting to actually use entitlements in the frontend, let's ensure two things

• On a plan change or any change that would invalidate entitlements, we need to invalidate the react-query cache
• Have a higher stale time to avoid refetching (let's do 30m-60m)

Addressed in #39905

[kanishkdudeja]

Tested and it works as expected.