Supabase confirmed its own side of OpenAI's cross-platform login beta, closing a gap Firerun flagged when Vercel shipped the same feature in July.
Supabase added “Sign in with ChatGPT” as a beta login option on the supabase.com dashboard and inside the Supabase plugin in ChatGPT, the company confirmed in a post on its own blog (Supabase, “Sign in with ChatGPT is in beta on Supabase,” July 29, 2026). OpenAI then made the wider integration official on August 2, naming Supabase as one of six launch partners for the feature (OpenAI, ChatGPT Release Notes).
What shipped #
A “Continue with ChatGPT” option now sits alongside GitHub and email on Supabase’s sign-in page. Approve the request on the ChatGPT side and it drops a developer straight into the Supabase dashboard, no separate password needed. It runs the other direction too: the Supabase plugin inside ChatGPT (desktop, web and mobile) can be connected the same way, letting a developer manage projects from inside a chat session. Account linking is automatic when the emails match: a new user gets a Supabase account created on the spot, and an existing user’s ChatGPT identity is attached to their account as another sign-in method rather than replacing what they already have (Supabase blog, July 29, 2026).
Supabase frames the benefit narrowly: for developers already working inside ChatGPT Work or Codex, this removes a separate login step between the tool they’re prompting in and the backend that prompt is wired to. Most developers will keep signing in with GitHub or email; this is an added on-ramp, not a replacement for either.
The Vercel connection #
Firerun covered this same rollout from the other side on July 30, when Vercel added “Continue with ChatGPT” to Vercel and v0. At the time, OpenAI’s own release notes already listed six launch partners: Airtable, GitLab, HubSpot, Notion, Supabase and Vercel. Firerun could not find a Supabase-published post confirming its own side of the integration and said so. The post existed; Supabase had published it the same day Vercel’s feature went live, July 29, and Firerun’s research simply missed it. OpenAI’s own broader beta went live four days later, on August 2, formally naming both companies as launch partners.
As with Vercel, only a name, email address and profile picture are shared with the partner when a user signs in this way (OpenAI, ChatGPT Release Notes). Team-level protections, including Supabase’s own MFA and organization access controls, still apply on top of it.
Our take #
Two platforms Firerun covers now treat a ChatGPT account as a valid identity, next to Google, Apple, Microsoft and GitHub. Our take in July still holds: OpenAI’s claim on that role rests on a chat product, not an operating system, a device ecosystem or a code host, and it’s been in that business for barely a month. What’s changed is the sample size. One platform adding a beta login button is a curiosity; two, confirmed independently on both sides, looks like the default option OpenAI is angling to become for any developer tool with a ChatGPT plugin. Watch whether Netlify or a Firebase-adjacent tool follows next.
Key Takeaways #
- Supabase confirmed “Sign in with ChatGPT” as a beta login option on its dashboard and via its ChatGPT plugin, in a post published July 29, 2026.
- OpenAI’s own broader beta went live August 2, naming Supabase alongside Airtable, GitLab, HubSpot, Notion and Vercel as launch partners.
- Only a name, email and profile picture are shared with Supabase on sign-in; existing accounts are linked automatically by matching email.
- It follows Vercel’s version of the same feature: both companies’ posts landed July 29, but Firerun’s July 30 report on Vercel missed Supabase’s side until now.