alfrednutile

We run this in Coolify https://coolify.io/docs/services/pgbackweb In our case on a cheap server

I mean you could easily use another mcp provider or write your own (ai can do it or zapier or n8n etc) The MCP would use the jwt passed in. Supabase has an official mcp as well but in case you wanted one that represented the business layer of the data vs just data.

Did not seem like spam especially with the followup replies 🤔

Thanks for sharing great insights!

Thanks for sharing!

I hosted this on Coolify. https://coolify.io/docs/services/pgbackweb I self-hosted the Coolify but it could run on other systems.

Btw what can save time is the built in AI that Supabase has to setup all these triggers etc :)

If they hit a million users they should plan for a yacht :) that would be awesome to get that many users. But good point overall.

Here is what Claude thinks and I had these problems about 2 years ago due to using prisma with it Short answer: Prisma won't "break" Supabase, but it fights against it. Supabase has its own migration and schema tooling that's purpose-built for Postgres, and Prisma's ORM layer can step on several Supabase-specific features. The main friction points: **Prisma ignores Supabase's Postgres superpowers.** RLS policies, Postgres functions, triggers, extensions like `pg_net` or `pgvector` — Prisma's schema file doesn't model any of that. So you end up maintaining Prisma migrations *and* raw SQL migrations side by side, which defeats the purpose. **Supabase CLI already does what Prisma Migrate does.** `supabase db diff` auto-generates migrations by diffing your local and remote schemas. `supabase db push` applies them. `supabase migration new` lets you write custom SQL. It's all native Postgres SQL, not an abstraction layer. **For exposing data to AI** (the Reddit poster's question), Supabase's auto-generated REST API via PostgREST + the MCP integration is a much cleaner path than Prisma. You define tables, RLS handles access control, and the API is instant — no ORM code generation step needed. The person on Reddit would be better off using `supabase db diff` to detect schema changes and the Supabase JS client or REST API for data access, rather than adding Prisma as a middleware layer that obscures what Postgres is actually doing. Would make a good quick reply or even content topic — this is a common footgun in the Next.js + Supabase crowd.

Careful though prima might break how Supabase manages its schema. It is worth using Supabase cli instead. But it is a great tool

Migrations and Data are two different things so I will cover both Migrations you can use the command line tool to do those as you or AI code. Any decent model will know but feed it the docs https://supabase.com/docs/guides/deployment/database-migrations It is really good and will go well Data is different Backing that up can AI can help you run the commands but if you also host a tool like https://coolify.io/docs/ PG Backup is a good way to back up your database

It is a great choice for a number of reasons AI built in to help you if needed RLS that has a good UI, docs and AI Storage which is awesome Event system so you can simplify how you build the system User and Auth sessions Awesome API Edge functions if needed And of course Postgres cause it is awesome

Thanks for sharing!

Great share. It also for me would bring storage to the table and events system so I can integrate into other tools. I wonder if websockets (Realtime) still work if you are not using its sessions?

I have built many systems before that have websockets, authentication, storage, database (of course), events etc. The fact I can get all of that out of Supabase doesn't make me less of a backend developer. I think the evolution of any technology solution is to get easier and easier to use to solve the business problems they exist for. I think for many Supabase is a great foundation for any business application that gets even slightly complicated. In many cases it becomes the the hub to the businesses I use it for. And then we can build different UI systems to interact with it or automation systems. Some systems I support have n8n talking to it using events, softr reading data to it for the UI and then react based front end for external users. I think teams not using it really should reconsider it over more traditional combinations of services they use to create the same foundation.

Oh wow they no longer give you access 😱 Just ignore my reply then sorry

Supabase the service has some top notch built in backup options I would go with that since it is built in, easy to recover.

Thanks!

I really benefit from the event system features which allows me to build automations with external tools like n8n using the webhook integration and crud events on tables. This has really help make some complex automations way easier for me to dol

Yes I remember before Supabase doing all this in at the time Laravel took AWS and S3 for storage Laravel auth for auth which lacked features for social logins Websockets had to use Pusher or their new thing which was not fun Events had another library RLS was in code

Why do you use the rest version vs just SQL?

What do you like about xano? Just curious it looks interesting

I have done both AWS and Supabase And like someone above said choose the right tools for the job For me Supabase has the building blocks I need for most automations and applications. Auth Storage Events Websockets Postgres RLS Unlike AWS, Supabase imo packages all up so I can just get going with my idea or customer project. Pick something and get comfortable with it and ideally focus less on ops more on the business goals

Just a heads up many times people miss this but the AI assistant in Supabase (hosted and self hosted) is pretty amazing.

How is the data being accessed? API Web UI And by users, apis etc That might help to know.

Right, I think this is a good answer because overall. If you find a good service to handle things like subscriptions, email, etc it is typically worth it

Oops just asked someone at Supabase and it gets admin rights. Not sure why since the oauth is being approved by that user. I will try to find out more.

Great question, thanks for asking. The user completes an OAuth interaction with Supabase before they can chat with it. This sets up their authenticated session, which your MCP server uses to obtain a Supabase JWT tied to that user's identity. When the MCP server then queries Supabase on their behalf, it passes that JWT, and Supabase's RLS policies evaluate from it, ensuring each user only sees and modifies the rows they're permitted to access. Thanks for asking!

:)

100% yes you can full automate it. I do not totally agree with u/ihavemanythoughts2 not that they are wrong I just feel like Claude knows how to deploy, knows how to set things up (github actions etc) I think learning what questions to ask is more important.. u/ihavemanythoughts2 sorry I mean I get your point and 100% agree with #2 just use one and point it to your code and go for it. Keep asking questions here too btw

Hey this can be tricky. Supabase migrations will become files in the code's supabase folder. What you can do is use Claude desktop and the Connection for Supabase to compare the current schema to what is in the files. (No need for mcp Connectors are built into Claude Desktop) Since you can even point Claude desktop to a folder now you have it able to connect to your super Bass and see your current code base right there in that folder and fix any migrations or run any commands you need as needed. Keep in mind too wherever you are with this project. I usually tell people keep it simple at first. If no one's using your site then just have production and you know your workflow can be simply that production Supabase database. Get it going. Use its built AI and UI to create your migrations and database changes and then later come back to building proper migrations. Just depends on what you are comfortable with.

I suggest one above he did a great job helping me use self hosted For self hosting Coolify makes it super easy

btw wanted to share the video that goes with this [https://youtu.be/tSmJHQG-jEE](https://youtu.be/tSmJHQG-jEE)

He covers migrations and more. It is older maybe some of the gotchas are fixed.

Yes there is a great video on it too let me share it[self hosted](https://youtu.be/nyX_EygplXQ?si=1R1AtTCJ-pc5s7vs)

Totally agree, what use to be numerous libraries and code for auth, webhooks, storage, events, rls etc is packaged so well and with proper ci/cd you can really make it hands off for going from staging to production

btw I talk about it a bit here https://youtu.be/rDN3m2qs58I and other videos since I use this a lot even with Softr.io and other no-code frontends

I mean it is "fine" but part of Supabase is learning how to use it, lean on it. There was some aha moments for me especialy in a few areas. 1) https://supabase.com/ui the UI components are more than UI they are ways to easily solve common challenges (Auth, WebSockets, Storage, and RLS) once I leaned on these more I did not have to worry about the complexity that comes with those areas of a project or application 2) I started to build apps that follow a pattern I call "Read, Write, Listen" the main point is to reduce the risk that comes with lots of business logic in code I would let the Frontend code read, write and listen to events based on RLS and the users auth sessions (so all the logic was in the RLS and the database). For example user logs in and Reads "their" tasks (each row is related to the user_id0 and when they click 4 tasks to set them as done they mark them completed (Write) and then as the backend system (Supabase Functions, n8n, Make, Zapier etc) mark them done the ui "pops" thanks to Websockets and Events that are triggered with row updates (Listen) 3) Storage and Events - this is one of my favorite features with Supabase a user can use the UI and the Supabase ui file upload to upload files and then events can trigger the backend system to "do something" with the file which is a super power and more of an Event Driven Design system. But any table in your Supabase that does not have RLS enabled can be connected to if your anonymous key shows (which is fine and ideal let this show) TLDR from ai So with RLS disabled, the exposure model is: Anyone with the project URL + the anon key can read/write all rows in that table (depending on what grants exist on the anon role). Since the anon key is typically embedded in client-side code and is considered public, this effectively means anyone who inspects your frontend can access everything in that table. Without the anon key, they get nothing — the API gateway blocks the request.

For example enable RLS so only authenticated users can read this table

It is confusing for sure. Supabase has Ai built in on the right you can ask it to do it for you.

<@1018917924989304872> what are your struggles with RLS and does the built in AI help you in anyway?

Great questions! Nice work on the form was fun to fill in.

<@648106514325700608> I tried something as an alternative to upwork but the hard part was getting businesses to use it. How is that part going for you?