Hello Figma Team,
I would like to provide feedback regarding the Supabase integration flow in Figma, specifically around project creation and cost transparency.
I recently created Supabase projects directly through Figma. In the Figma UI, the flow presents a simple “Create Project” dialog that only asks for a project name. There is no visible indication that this action will immediately provision a continuously billed virtual Postgres server, nor that it may incur significant ongoing compute costs beyond a Supabase Pro subscription.
From a user perspective, the term “project” strongly implies a logical workspace or environment, not a dedicated server with hourly billing. As a result, I upgraded to a Supabase Pro plan solely because the number of projects exceeded the Free plan limit. Despite already being on a paid plan, I was later charged over $60 in additional compute fees, which was completely unexpected based on the information shown during the Figma-driven creation flow.
I want to emphasize that this was not intentional usage or production deployment. It was early-stage evaluation triggered by the Figma integration. The issue here is not Supabase’s pricing model itself, but the lack of explicit cost disclosure at the point where Figma initiates resource creation on behalf of the user.
At a minimum, I believe the integration flow should clearly communicate that:
-
Creating a Supabase “project” provisions a dedicated, continuously billed server
-
Charges begin immediately and are independent of actual database usage
-
Additional costs may apply even when the user is already on a paid Supabase plan
Without such disclosure, the current UX creates a high risk of unintentional and significant charges, especially for new users evaluating the integration.
I hope this feedback can help improve the clarity and safety of the Figma–Supabase integration and prevent similar issues for other users.
Thank you for your time and consideration.
Best regards,
Lenik