Supabase stays available, and existing Supabase Make apps keep working. Rolling out on all plans. Useful when a PM needs to click something that saves a record. Easy to oversell in a design-system roadmap.
The system you govern is still the library, the guidelines, and the package. Payload does not name your tokens. It does not stop a second button. It does not replace the review in the repo.
Where I would put it
If a squad wants to try it, let them try it on a prototype, with the code layer started from a repo you trust. Do not schedule a Q1 migration of production data onto a canvas backend because the demo looked fast.
I have spent 16 years on the seam between the file and the repo. The expensive failure is still the interpretation, repeated, every time a squad cannot trust the component. A working prototype does not fix that. A package the agent can see, and a person who can say no, does.
I checked the Figma release notes and the Config India 2026 help article on 18 Oct 2026. Plans, betas, and the 4 Nov credit window come from those pages. If your admin console disagrees, trust the console.