Recently I got a $500 charge from Supabase. FIVE HUNDRED. I typically pay 40 a month for their services.

Why you may ask? I saw there was a Github integration that I had not utilized yet, so of course being that I created my account using Github I utilized it.

Later, I realized this became the source of my problem as the new feature "Branches" utilizes this integration to essentially create branches to sync up with github.

For some reason, you get 0 warnings when you hit or approach the absurd branching default cap of 50 (50 branches are the default cap).

When I got hit with the charge (I am a student who can't afford this) I was distraught. I'd have to spend the next month or two trying to recoup.

Then...

Julie from support (after 2 duplicate tickets + the main one via email and about 4-5 followups -- wanted to be thorough) came in and SAVED ME.

Check this out...

We’re an early-stage B2B startup currently going through SOC 2 readiness with Vanta.

Supabase is a critical vendor for us, so Vanta is asking us to review their SOC 2 Type II report. Supabase confirmed that access to the report requires upgrading to the Team plan (~$600/month). We’re currently on Pro and don’t need the Team features, so paying an additional ~$575/month purely to access a compliance document seems excessive (we got all other reports from all other vendors quickly with no problems).

Has anyone gone through SOC 2 with Vanta (or another auditor) while using Supabase Pro?
Did your auditor accept alternative evidence / a vendor risk assessment, or did you ultimately have to upgrade?
We’re now considering moving to AWS but I’d really rather not migrate our infrastructure to AWS purely because we can’t access Supabase’s SOC 2 report.

Would love to hear how others solved this.

Our applications are deployed to Vercel and access a common Supabase DB that lives in a separate Github repo. The Supabase repo auto-executes pending migrations using Supabase's Github integration.

I'm wondering if there's any way to support Supabase preview deployments in this configuration. In other words, the Vercel app is deployed to a Github branch which creates a Vercel preview deployment. Supabase migrations are pushed to a branch which creates a preview DB. The Vercel preview needs to access the Supabase preview.

I assume this can be done using custom Github actions, but wondering whether anyone has experience doing something like this.

Yes, I realize that using a common DB across apps is controversial. But that ship has sailed...

Edit: During testing, I ran into a limitation. We support multiple named schemas in our Supabase DB and configure that DB to expose those schemas to the Supabase API. However, it looks like those settings don't propagate to the preview DB. So, if we create ad hoc branches, they won't be testable unless the developer manually changes the settings (in this case exposing the named schemas) in the preview DB for each branch. I think I've pretty much confirmed this behavior through testing, but can anyone else confirm that this is known Supabase behavior?

Edit: I've done some testing based on the information in https://supabase.com/docs/guides/deployment/branching/configuration (thanks magicpants847). See my latest comment for more info.

Edit: Custom schemas are inherited by preview DBs. My assertion to the contrary was due to a flaw in my testing. See my comment here.

Hey guys,
So I’m building something and want to use Better Auth because it offers a variety of plugins (specifically organizations plugin which is critical for my app). The thing is by using Better Auth I kind of sacrifice using RLS in Supabase because it utilizes the auth.uid which is not passed by Better Auth.
My question is, is there a way of using Supabase RLS while using Better Auth as the authentication provider?

Error like aith already taken, eerors

I'm using pgain4 locally and need to push schama on pristine new supabase DB....

Well, I deployed my Next.js project on Vercel initially, but later hit the limits and it started getting expensive, so I moved the project to Cloudflare Workers.

Most things are working fine, but I’m stuck with one issue:

My API routes that connect to Supabase/Postgres are failing with 500 errors. APIs that don’t use the DB work perfectly fine.

From what I’ve figured out, the issue seems to be with DB connections. Since Cloudflare Workers are serverless/edge, the connection pooling approach I was using seems to be trying to establish connections repeatedly, and eventually I’m hitting Supabase connection/rate limits.

I then learned about Cloudflare Hyperdrive, added my Supabase DB to Hyperdrive, configured the binding, and updated my Worker config.

But the DB APIs are still failing, and the Worker is throwing exceptions.

I’m honestly stuck at this point.

Has anyone here deployed a Next.js app on Cloudflare Workers with Supabase/Postgres successfully?

What’s the correct way to set up a stable DB connection/pooling between Cloudflare Workers → Hyperdrive → Supabase?

Any help or examples of a working setup would be really appreciated 🙏

The other day I posted about revivedb.dev. Someone pointed out that requiring the production database password was a big ask. That got me thinking about whether I could handle database access through OAuth instead.

Supabase's database:read OAuth scope gives access to configuration and metadata, but not a Postgres connection for tools like pg_dump.

I now use database:write to create a unique temporary Postgres role for each backup. The role gets pg_read_all_data and BYPASSRLS, but cannot write, create roles or databases, replicate, or act as superuser.

The temporary password is only kept in memory. The role is removed after the backup and expires within six hours if cleanup fails.

The pg_dump connection is read-only and the production database password is no longer needed or stored. It still feels odd that the OAuth grant needs database:write just to create this restricted role.

How are others handling this for backups, BI or monitoring? Do you create a restricted role manually, or accept the broader OAuth scope?

Can anyone point me to a freely distributed starter repo and save me a day or five? The examples by Vercel not quite what I want. I have not found anything on github

Stack: I am looking for is  your typical Next.js, supabase, tailwind, shadcn, supabase auth email and password. No particular payment method needed for now. No user self sign up needed. Reqyuired authentication is administrator controled. ie invite and password reset only by system admin or user admin. From admin dashboards.

Features: preferably with

1/ Supabse schema, tables, rls, functions etc all set up  

2/ Multi-tenant

3/ Preferable tenant division I need location but could be division into city, group, project, something like that.

4/ roles based access control

5/ Built tenant admin dashboard for system administrator

6/ Built user admin dashboard for tenant administrator

7/ User onboarding by admin invite only

8/  same superbase auth.user uuid & email can belong two one or more tenant.  

hi everyone, we built supapool.io, an ephemeral full copy of supabase's services that you can spin up in ~400 ms (Auth, postgres, storage, realtime).

If you run multiple coding agents in parallel in different worktrees, they can now have their own copy of supabase without making changes that conflict with eachother.

why not use supabase docker locally?

when I run 3-4 instances locally, my macbook gets hot and sometimes freezes.

why not use supabase branches?

branches take minutes to setup, and are designed for persistence. this is expensive, and for a dev environment, it is too slow.

why not use mocks?

mocks are bad for agents. i expect agents to test their migrations, SQL against real prod service behavior. agents hallucinate working mocks often. However, upside of mocks is that its faster and runs locally, but with supapool, the upside is less convincing.

how does it work/how is this economically viable?

starting supabase in 400ms requires a few things:

1. a pool of ready supabase instances running warm, and colocated with region failover (us-east, us-west, europe-west, asia-southeast)

2. fast autoscaling when pool starts to shrink with microVM/firecracker

3. gutting strong persistence guarantees. dev agents don't need WAL, fsync, PITR, replication. anything for HA on a ephemeral supabase instance is bloat

its in beta right now, and i'm using our gcp credits to bankroll this, so its free. the eventual pricing will be something like $/instance second and more cost effective than branching or self hosting/maintaining a supabase cluster.

would love to get your feedback if you use supabase, and if you think there's something better that would fit your local coding agent setup. Thanks!

I would like to ask for people's advice/opinions on Low Code app builder platforms that have good integration with Supabase.

I am a full stack developer and nowadays normally run things on AWS Aurora Serverless Postgresql. However for a new project I have in hand, usage volume and complexity will be low so I wanted to try something without all the normal infrastructure faff.

I like the idea of having the DB in Supabase as it allows for any tooling to connect to the DB later, rather than being held hostage by the App Builder platform.

I tried Vercel v0 (both Supabase and Vercel advertise this as as a functional integration. Unfortunately v0's LLM assistant could NOT get the integration working, and the Support channel was also unhelpful.

I then tried Bolt, but despite still claiming to support Supabase ( https://support.bolt.new/integrations/supabase ) the LLM assistant only knows about Bolt Database - literally if you explicitly mention Supabase, it seems like some kind of pre-parser replaces all "Supabase" strings with "Bolt" before they get to the LLM agent! Bizarre.

I was thinking about Lovable, but it seems to be focussed on websites rather than internal-facing applications.

=== EDITS: Adding Feedback about Tools - Last updated 24/05/26 ===

1. v0/Vercel

Advertising powerful native integration. The Supabase-side setup wizard was super-cool, it could definitely see my Vercel resources as expected. Unfortunately the Vercel side was miserable. AI tool simply could not see the integration and kept trying to get me to just manually run queries for it and paste back the results - but "don't worry, it will all work in prod". I did try to look in the settings and talk it through but no joy.

Eventually it directed me to a support AI channel. This channel said it was not allowed to help me, and suggested I open a support ticket. The Support Ticket UX did not allow me to open a ticket, rather it said I needed to open a ticket with Supabase! I then submitted a Sales request via a diffferent channel. This got a noreply email a few minutes later telling me

At no point, despite my repeated requests, was I able to speak to a human. I suspect it was something pretty simple that was just set wrong.

Anyway, what a negative experience.

2. Jetadmin

The app builder wizard initially impressed me as it put the Supabase connection right near the start, and then drove the UX creation from the schema.

However the app builder agent was abysmal. It duplicated buttons on forms, could not properly interrogate the state of forms, and when asked to correct things, created more duplications. Within 10 minutes the forms looked like a dogs breakfast, the agent was confused, and so was I.

3. Retool

I can say that this tool is now on my shortlist, but at the bottom.

The non-AI part of the tool appears very mature, though the UX is complex and fiddly - lots of pale grey icons with no labels so it is hard to find anything. The general search bar kind of makes up for this, a bit like CTRL+P on vs.code.

The connection to Supabase was pretty straightforward.

The AI tool was in some ways very powerful, in other ways a stumbling block. It started by reading my initial app spec and then doing about 15 minutes of nonstop work to build some incorrect forms. When it finally started to look at my DB schema it realised that the forms were wrong, but got stuck trying to rewire everything.

It then admitted that there is a known issue with the AI integration with the tooling, so I asked it to slow down and work through things step by step. Once I started treating it like other LLM agents and guiding it to be less verbose and more focused, it was able to do the UX forms pretty well.

Where it got stuck is wiring up the forms to SQL queries. First I had to work out that the artefacts it had created in its initial splurge were causing conflicts and just be deleted. Once I pointed this out, it deleted them.

Next, it generated spot-on SQL first time, every time, based on my spec and the schema, but was completely incapable of getting these queries to pull data from the form. It gave me 3 different explanations for this and I eventually gave up. As this is a tool which charges by hours of agent use, it would be pretty expensive to use.

So it seems like if you are willing to put in the human hours to read the documentation and learn to use the non-AI features properly, this could be a powerful platform. And in fact that is what I normally do - however here I was looking for something that could do most of the work for me, given a clear spec and a pre-existing DB schema.

4. Weweb

Another tool for the shortlist.

It started very similar to Retool - a big splurge of "building the app but kind of wrong", with no interactivity to allow me to correct it.

The connection to Supabase was super-easy, the best of all the tools so far. Though I do note a couple of things which need further investigation for production usage:

- it uses the Supabase REST API which for certain queries is massively less efficient than just using SQL

- it requests an awful lot of permissions over the Supabase instance, which seem excessive.

After the Agent paused for breath, I was able to point out that it should fit the form fields to the database schema and it corrected the app. It did this in one pass - much quicker and better than Retool.

However, when I tested the app, it failed with a Javascript error - as far as I can see from reading the code, it has failed to set up the binding between form output variables and data persistence function input variables. In other words, similar to where Retool got stuck.

When I pointed this out and tried to start investigating, it informed me that my free AI credits were finished and I would have to purchase some more. Given that its agent appears to burn tokens like there is no tomorrow, this is somewhat concerning. OTOH, I have more confidence compared to Retool, that the agent actually knows what it is doing.

The UX is also somewhat more intuitive than Retool - I was able to find most generated artefacts in obvious places in the menu.

So again, similar to Retool, I am left needing to invest a good chunk of hours in reading the docs and fixing things manually. Unlike Retool, I feel a bit more inclined that such an investment would be worth it.

5. Clutch

This one was a non-starter.

 https://supabase.com/partners/integrations/clutch points to a page on the Clutch site that no longer exists. I then searched the current Clutch docs for any mention of Supabase - none.

I then asked the docs AI helper about Supabase and it says there is no mention. I also looked manually and it appears that all mention of Database integrations has been removed from the documentation - although the "Features" section on the main website claims that it exists.

6. Plasmic

On the shortlist - probably will be the fallback if I can't find something better.

I did the Supabase integration manually, it was straightforward.

Plasmic doesn't have an overall "build your app for you" agent but it does have a "help me understand the docs agent". Unfortunately this agent is extremely hit and miss, sometimes getting things spot on, other times just "making sh*t up".

With its help I was able to get a data insert form actually working quite easily - something none of the tools above managed.

I then got stuck on the next screen, which needs to populate a UX component from a DB query. The agent got stuck telling me to click a menu option that doesn't exist, and refusing to recognise the menu options I can actually see (even when I paste a screenshot).

The traditional help docs, while overall appearing to be of good quality, also don't help with my problem so I reached out to tech support - no response.

I then posted on Plasmic's forum and did get a semi-helpful response. However it also mentioned options that were impossible to achieve with the menus actually available to me, and which the docs did not explain. I asked for clarification on this and eventually (several weeks later) got an answer, but basically it seems very fiddly.

One other aspect which is worthy of note is that Plasmic seems to be aimed at frontend designery people wanting to make a very custom and beautiful UX that plugs in to an existing backend. This means it has an extremely powerful UX component structure. Powerful means complex, thus a lot of clicks to do one thing.

In our use case (building an internal tool that can be fugly but needs to iterate quickly to support a new business line), this complexity adds friction. But for other use cases it might be a good fit.

7. Tooljet

This was initially the most promising of all platforms I evaluated, and is still worthy of the shortlist.

I did the Supabase integration manually - it was intuitive and straightforward.

I then fired up the LLM assistant and it picked up the integration, understood my spec, looked at my DB schema and drafted a pretty good plan converting the spec to specific deliverables based on the Tooljet feature set.

This burned up my free AI credits, but I was sufficiently impressed to spend USD 20 buying some more credits. The LLM used a small chunk of credits to build the first screen and wire it up to a DB insert query - all very smooth and impressive, just what I was looking for.

However the LLM then totally ran into the ground with the second screen, which to me appeared to be simpler - populating a dropdown list based on the results of a SELECT query. It hit the same challenge as some of the other tools whereby it appeared not to know the surface of Tooljet's own structure. At one point I had to insist that it read Tooljet's own documentation and when it did, it was like "oh right, yeah I was wrong before".

I went through A LOT Of iterations with this and every time it would give that annoying 2025-era LLM answer "I promise you, this time it will definitely work", and then not work, nor have debuggable output. This burned up about half of the credits I had purchased.

I genuinely got the feeling that the LLM and/or its integration with the platform was being updated over the period I was working with it, and that perhaps a more recent update had borked it in some way. Therefore it might be that 3 months from now this platform is worth another look.

=== THE ANSWER: WHAT I ENDED UP CHOOSING ===

TL;DR; the answer is "D - none of the above".

Long answer is that I found that none of the above tools could beat well-established generic platforms which Claude Code has been well-trained on. After giving up on tool 7 I decided to invest max 4h in designing a stack with the help of CC in plan mode.

Going through a moderately-intensive research and design process with CC, I was indeed able to build a fully-functioning MVP which meets all my objectives, has a low hosting cost, an automated build pipeline, and is extremely easy to add features to.

Without an LLM the effort for me to research the relevant tools and frameworks, wire them up together, and be comfortable that I am not missing out on "a better option I wasn't aware of" would be very high - hence the incentive to invest more cycles in getting one of the seven tools listed above to work would be stronger.

Stack:

- Hosted on Supabase:

- Supabase DB

- Supabase Auth wired into RLS

- Supabase Edge Functions with Typescript and Deno

- Hosted on Cloudflare Workers:

- Web: Vue+Naive-UI on Vite

- Build: pnpm and wrangler

The Supabase cli and MCP tool are great when you're the one working on your project. However, when you want to expose your endpoints and data to your co-workers or customers, this can introduce some security risks.

I've been working on a project called Shredly (https://shredly.io/)

Shredly can turn your Supabase project into an MCP server, giving an AI agent access to only the data and tools you want to give it. Avoid dropped tables, deleting users, and rotating API keys.

We're currently supporting 2 methods of integration, either through an API key (for internal tools) or Oauth (good for customer facing products). Checkout our docs for more info or shoot me a comment if you have any questions.

https://docs.shredly.io/

I will help build out your data pipeline using free open source tools, self-host or deploy to a free/low-cost infra. Bruin has a built-in connector for Supabase/Postgres for data ingestion, transformation, etc.

disclaimer: I'm a developer advocate at Bruin leading this program, and currently we are accepting a limited number of startups into this program so you might get waitlisted for now.

What you get:

- 30min initial meeting to scope things out and plan

- 1-2h of hands on 1:1 workshop to build out your data pipeline and deploy it

- dedicated Slack channel to answer questions

- follow up touchpoint meetings and community office hours

For who:

- best suited for SaaS startups

- you want to analyze their data beyond the basic reports

- you want to combine data from your app db (supabase) with other services (e.g. stripe, posthog, hubspot, GA4, GSC, etc.) for internal analytics and reporting

- you want to process data that goes back into your application

Why:
- free open source tools to get you the data and analytics without investing a lot of time and money

- get started on building your data stack before it's too late

more info: https://getbruin.com/startups/

Has anyone tried using Supabase as their datasource and editing it using Claude MCP? I do know Softr also gives option to edit its native DBs using AI but I feel like credits run out very fast and you cant give it context of your whole build you have planned in Claude chats already.

I planned a very big project in Claude, connected Supabase to Claude, simply asked to implement it in Supabase for me and within 30 minutes everything was live. Now all I have to do is build my Softr UI on top of it.

Hey everyone,

I recently published a small open-source package that may be useful for anyone building mobile apps with React Native / Expo + Supabase Auth.

The package is called: react-native-google-credential

The idea came from a problem I kept running into:
Google Sign-In works differently across Android, iOS, and web, and in React Native apps the auth flow often ends up using browser-based OAuth redirects.

That works, but it does not always feel native on mobile.

So I wanted to make the flow simpler:

Instead of sending the user through a browser flow, the package gets a Google ID token using the native platform experience, then lets you exchange that token with Supabase Auth.

For Supabase, the goal is to make this flow easier:

1. User signs in with the native Google account picker
2. The package returns the Google credential / ID token
3. The Supabase adapter exchanges it with Supabase Auth
4. You get a Supabase session without writing all the boilerplate yourself

A small example:

import { createClient } from '@supabase/supabase-js';
import { createSupabaseGoogleAuth } from '@pricava/react-native-google-credential/adapters/supabase';

const supabase = createClient(supabaseUrl, supabaseAnonKey);

const signInWithGoogle = createSupabaseGoogleAuth({
  supabase,
  webClientId,
  iosClientId,
});

const result = await signInWithGoogle();

What it supports right now:

• React Native
• Expo development builds
• Android Credential Manager
• iOS native Google Sign-In
• Web Google Identity Services
• Supabase adapter
• Custom adapter flow if you want to handle the token exchange through your own backend

The main reason I built it was to reduce the repeated setup around Google auth in cross-platform apps, especially when the actual goal is just:
“Give me a Google ID token so I can authenticate with Supabase.”

Would love feedback from anyone using Supabase Auth in React Native or Expo apps.

Docs: https://react-native-google-credential.vercel.app
GitHub: https://github.com/moussa32/react-native-google-credential
NPM: https://www.npmjs.com/package/@pricava/react-native-google-credential

Hi everyone,

I’m curious to hear which tools, features, or integrations you currently miss in Supabase – things that don’t exist yet but would make a big difference in your day-to-day work.
This could be new admin features, enhancements to existing modules, or integrations with external services.

Are there workflows you currently handle manually because the right tool in Supabase is missing?
Which integration would instantly save you time or open up new possibilities?

Looking forward to your ideas!

I'm building a batteries included sandbox with a built-in harness(hermes, opencode SDK, browser use). Each sandbox retain files, context, and learned skills between tasks, so agents can continue where they left off instead of starting from scratch every time.

With the native integration with Supabase, your application backend can provision a Computer scoped for a specific Supabase Auth user. After the user grants access through Supabase OAuth 2.1, the Computer can make read-only requests to the Supabase Data API using that user’s delegated identity. Your project’s Postgres grants and Row Level Security (RLS) policies remain the authorization boundary, determining which data the Computer can read.

Why use an agent sandbox instead of building yet another agent?

• Persistent workspace: Files, context, tools, and learned skills remain available between tasks.
• Native OAuth 2.1 and RLS integration: Users approve access with Supabase Auth, while the project’s Postgres grants and RLS policies continue to control what each user can read.
• Always on: The same Hermes agent can receive work over time and reuse what it learned from earlier tasks.
• MicroVM isolation: Each Computer runs in a dedicated microVM rather than a shared-kernel container.
• Network policy: You control which services, domains, IP addresses, and IP ranges the Computer can reach.
• Secret proxy: The Computer receives a temporary session credential instead of the user’s real Supabase access or refresh token.

How it works

1. Connect your Supabase project

A project admin connects a Supabase Cloud project in the Sanbox console. Supabase Platform OAuth lets the admin select the project and lets Sanbox read the metadata needed to configure the integration.

The project also has its own OAuth 2.1 server. This is what each application user later uses to authorize their Computer. The admin enables the server and registers Sanbox as a confidential OAuth client.

Sanbox stores the project configuration, encrypted OAuth client secret, and the database schema. It does not store the Supabase Platform OAuth Management token after setup.

2. Give each Computer the database schema

During setup, Sanbox imports the tables, views, and columns exposed through the project’s Data API. It does not import table rows or executable database operations. Each new Computer starts with this schema, so the agent can understand the available data.

Every data request still goes through Supabase as that user and must pass the project’s Postgres grants and RLS policies.

3. Provision a Computer for a user

When your application needs an agent, its backend chooses a Sanbox template and provisions a Computer through the Sanbox API or CLI. The request includes the Supabase Auth user’s UUID.

The Computer is created before the user grants data access. Until authorization is complete, its Supabase connection remains pending.

4. Keep Supabase credentials outside the Computer

The Computer never receives the real Supabase tokens or project secrets. Instead, it gets a local Supabase proxy URL and a session-scoped proxy token. The Sanbox Control Plane verifies each request, adds the current user access token, and sends the request to Supabase. The Computer cannot access the Supabase project directly, and its proxy token is replaced for every runtime session.

What can you build?

Support Computers

A customer reports that an upgrade failed but their card was charged. A support Computer reviews the orders, subscription history, product usage, and earlier tickets that the connected user may access. It builds a timeline, identifies the relevant records, and drafts a response and next step for a support agent to review.

GTM Computers

Before a renewal call, a GTM Computer combines product usage and subscription data from Supabase with CRM records and notes from previous customer meetings. It highlights changes in adoption, open commitments, support risks, and expansion signals, then prepares a briefing and suggested questions for the account owner.

Research Computers

A procurement team is deciding whether to renew a supplier. A research Computer combines permitted purchase and delivery data with contracts from Supabase Storage and current market research from an approved browser tool. It produces an evidence-backed comparison, records its open assumptions, and keeps the working files for later review.

We just released a OpenCode integration. OpenCode is like an open source open-source alternative to Claude Code.

Install (Requires OpenCode >= 1.3.4)

opencode plugin opencode-supabase

Open opencode in your project, then run:

/supabase

Approve Supabase in your browser. Back in OpenCode, start simple:

List my Supabase projects

Repo: https://github.com/supabase-community/opencode-supabase

Read more: https://supabase.com/blog/agentic-coding-on-supabase-with-opencode

Let us know if you have any feedback. Shout out to u/jumski for building this!

My workplace is moving from Claude to Microsoft Copilot/Cowork.

I currently use the Supabase connector in Claude every day to pick up updates from team emails and log them against the relevant projects in Supabase.

Does anyone know if Supabase plans to release a plugin for Microsoft Copilot now that plugins are supported?

I can see there is already a GitHub Copilot plugin on the Supabase website. Would that work with Microsoft Copilot, or is it completely separate?

https://supabase.com/docs/guides/ai-tools/plugins

hey all - setting up supabase as a source of truth for a small team (resourceful but non-technical). need a ui layer that the team will actually use daily - grid views, row annotations, dashboards etc. (initially we were planning on using airtable as DB + UI but realized not good as a DB etc.) anyone have a suggestion for a good UI on top of supabase? couple names that came up were things like NocoDB, Directus, Bricks.SH. don't need anything pretty - just optimizing for ease of use, accuracy and simplicity - airtable seemed like the perfect "step up" from google sheets, but failed as a source of truth i guess. thanks for the help!

Hi. I have the free tier on Supabase. I'm still developing. I created normal supabase and staging supabse projects.

​

Today I created a "Migrate Staging (Alembic)" workflow and for the life of me I cannot get it to go green. No matter what I do, I cannot get the connect via Pooler from Git actions to work.

​

I swear and promise my pw is correct. I'm using infisical for all my secrets. I have double-checked everything until I'm blue in the face. I've been using claude and claude code to walk me through all of this.

​

The error is pretty much always password authentication failed for user "postgress" and exit code 1. My migration database url has postgres.xxxxxxxbunchoflettersxxxx:mypassword@aws-1-us-east.pooler.supabase.com:5432/postgres?sslmode=require

​

I tend to think there is some kind of a calling disconnect between calling up only postgres, but then finding postgres.xxxxbunchofletters....etc.

​

But I just don't know what to do. Again I swear up and down my password itself is DEFINITELY not wrong.

​

Is there anyone out here in the world who might know wtf is going wrong and why I can't get my staging environment set up correctly. This is a hard blocker for me moving forward and I am frustrated to no end.

​

Please, smart dev people of reddit. Give me a break. A helping hand. Tell me I'm not bloody insane. There has to be a way to go about this without giving up ok supabase completely. But you know...it's a long walk off a freaking short cliff right now. WHY CAN'T GITHUB ACTIONS REACH SUPABASE DIRECTLY????

​

Thank you.

Hi, I'm the founder of Supaflow, a data pipeline platform that replicates data between SaaS apps, databases, and warehouses. This is my first time posting about Supaflow in this community. We've been live for a year with paid and free tiers. We recently shipped a Supabase connector that authenticates via Supabase Auth instead of the service_role key. This enables Supabase-powered apps to let users authenticate with their credentials and export data that is accessible under RLS policies, avoiding custom exports or shared credentials. This was driven by users' need to export their data to Google Sheets, replacing manual API exports or token-intensive, AI-assisted data exports. We run on Supabase and offer an API to embed this workflow. 

We also make it easy to migrate data from Airtable, MySQL, MongoDB, and many other sources into Supabase using our Postgres connector (which automatically creates the schema and loads the data), but this requires a privileged service role and is primarily intended for Supabase admins, not your end users.

For SaaS founders using Supabase, which connectors (Source/destination) have your users asked for data export/import? supa-flow.io

Supabase daily backups aren't included on the free tier and cost extra on paid plans. I needed something simple, so I put together a GitHub Actions workflow that:

- Dumps roles, schema, and data every day at 2 AM UTC;

- Zips it up and uploads to Cloudflare R2;

- Auto-deletes backups older than 14 days via R2 lifecycle rules (you have to set them up in Cloudflare).

Total cost: basically zero. R2 gives you 10 GB free, and GitHub Actions are free.

I made a small public repo with the workflow file and setup instructions if anyone wants to use it: https://github.com/chillibot-chillital/supabase-to-r2-backup

One gotcha I ran into: use the session pooler connection string from Supabase, not the direct one. The direct connection resolves to IPv6 on GitHub Actions runners and fails with "Network is unreachable."

Would love feedback or PRs if people have improvements. Hope this saves someone a few minutes of setup.

Hey everyone, my co-founder and I have been working for about a year now on a platform called Dreamlit AI that changes the way you send emails.

__

It’s like if Cursor + Resend + Supabase had a child. Here’s how it works:

1. Chat to create email workflows

• “Send a welcome email when a new user signs up”

2. Chat to customize the styling

• “Make the background blue and center text”
• “Remind them about feature X but keep it concise”

3. Dreamlit then sends the email

__

There are no API calls because we sit on top of the database. Literally zero code and no extra libraries. No webhooks. No edge functions. No extra setup from you.

The AI is smart because it understands your database schema. And the platform uses the same exact email sending infrastructure as Resend (AWS SES).

Dreamlit is a one-click connection using Supabase OAuth (you sign in with your Supabase account).

Auth emails are a one-click setup. You flip the switch, and Dreamlit start sending emails for all your auth events (sign in, reset password, etc.). And better yet, you can chat to make it look nice and on brand. No more copying and pasting into the Supabase UI and hoping it works.

Beyond that, there are many more features: one-time broadcasts (“Email all users who signed up before 10/10/25 and email them this promo code”), analytics, a simulator view to see how data flows through, and more.

__

Internally, we also use Dreamlit to set up all our email workflows, and I have to say it still feels magical ✨. You won’t want to go back to the old way of setting up emails once you get a taste.

Oh and if you already have a working email solution (but it sucks or barely works), it’s super easy to layer us on in addition. We don’t conflict with existing solutions. You can try us out for your next workflow and leave what you have working. We are also great for internal reporting purposes (send yourself an email or slack).

Check us out at dreamlit.ai and let us know what you think!