Native integration between Replit and Supabase, similar to what already exists with Neon Postgres. This would allow developers to connect, manage, and provision Supabase projects directly from the Replit interface.
Why is this important?
Supabase has become one of the most popular Backend-as-a-Service platforms, offering not just PostgreSQL databases but also:
Many Replit developers already use Supabase manually by copying connection strings into Secrets, but a native integration would dramatically improve the developer experience.
Proposed features:
One-click Supabase project creation from Replit
Automatic environment variables injection
Database browser/viewer within Replit
Quick access to Supabase dashboard
Impact:
This would enable faster prototyping for full-stack applications and make Replit an even more powerful platform for building production-ready SaaS products.
Would love to hear from others who’d benefit from this!
+1, but if you give to Replit links to supabase documentation it will integrate it flawless. The only thing is that you should create tables directly from the Supabase console or ask replit to create scripts that you can run from the shell…
I think they are pushing their native db feature, that I found a limit if you want to use vector dbs as Supabase does.
I wonder if some of the backend service providers are making exclusive deals with app building platforms. Replit/Neon vs. Bolt/Supabase for example. Bolt almost hides the fact they are just white labeling Supabase and bills it as their own integration.
I thought the same thing, I think @Gipity-Steve runs Supabase on most of his apps though, so I’m sure even if there isn’t something native you could still accomplish using Supabase like @andreabarile10 is saying. I use a few services that Replit doesn’t natively support and as long as I’ve fed Replit documentation, it’s worked fine.
As @shawn93 said, I used Supabase heavily for 6 months last year. It is a solid platform. But I have now come in from the cold, and have gone full Replit-database.
Simply put, Replit cannot “see” the Supabase DB, and so you have to constantly act as a middleman. Replit can’t simply change the schema - it has to give you a script and ask you to run it. Or if there is an error in the Supabase console, you have to copy/paste it over to the Replit agent to get feedback. After a while, it gets to you, and becomes hugely tedious.
I am now a fan of everything under one roof - which really lends itself to what vibe engineering is all about - making life easy!
If Replit were to team up with Supabase and create a simple connector (and drop their deal with Neon), then that would be interesting. But otherwise, I do not recommend it if you want a simple life.
