Threads
Loading user profile...
The user introduces AppGrape Studio, a UI builder for Supabase that connects via OAuth without requiring service keys or API secrets. It respects RLS and RBAC policies and is designed for secure, no-code UI building. The user plans to open source the project. Another user questions the market need for such a tool compared to AI-driven UI builders.
The user introduces AppGrape Studio, a UI builder designed to integrate seamlessly with Supabase data. This tool aims to simplify the creation of custom admin panels and business dashboards, providing more control for developers compared to AI-based builders.
Well, this is probably not going to replace AI UI builders - which is sufficient for quick shipping of PoC, MVP, small tools. But when it comes to internal ERP systems, for instance, that reliably run businesses, we find that the UI needs to be easily reliably modified by the knowledge workers. Integrations and workflows need to be intentionally built with fool proof security. That's where tools like these are necessary.
Thank you. Appreciate this.
Oh this is probably it. We are using a custom domain - obviously because we want the email to go from a "related" address when someone signs up. So you are right in that, the sender domain is different from supabase.co - and this could be flagged by Microsoft defender or other services. Is there a way around this?
No, the domain isn't that new.
Great point. Yeah, most UI builders ask for the service role key / access to secrets. We have tried to intentionally create a method that doesn't do that. It is the users own token that is used for all sessions - including the first one where we establish connection. We do this to fully utilise the power of native security and RLS provided by supabase.
Thank you for the feedback. With your feedback, I will make a documentation about how we connect with supabase and respect all the RLS, RBAC without storing/cacheing any data. And yes, that was our reasoning behind making it open source - to mainly build trust that we don't read anything unnecessary, and don't store anything. Thanks for your suggestions :)
We have built several Softr + Supabase projects, but never used Claude MCP for architecting the database. With Softr, the problem seems to be more and more to do with building deliberate UI that runs businesses. Softr is pushing for AI based building a lot more than I like.
We self host most of ours - so cannot comment on 1, 2 and 4. We use real time feature quite frequently and it has worked well for us so far.
In the recent years, we see ourselves prefer Supabase over others (we self host for a lot of projects, btw) - we find the auth a dream, integrates so well with other backend layers like python fastAPI, updates/support are regular, and is amenable to build reusable front end blocks. We also have a host of SQL functions built over time - so I guess we are leaning towards Supabase these days.
We have a few projects that use python fastAPI backend + auth and postgres from supabase + react-ts for front end. These were slightly complex projects that required some serious automations that we wanted to set up ourselves.
Well, that's because Supabase is supposed to be an all-in-one postgres backend, something similar to firebase (less reason to open-source). prisma and auth.js are more (comparitively) DIY and composable (more reason to open source). I mean, I wouldn't judge AWS by the number of open source SaaS apps built on it. But I do understand that you would like to "see" something built with it before trying it out. Happy to demo a few projects we have built on Supabase (I have an agency that builds custom business softwares along with mobile app counterparts if that's your jam) - they are not open source though.
I mean, you can imagine why most of the serious ones may not be open source \*and\* not-for-developers - many good ones are internal and propreitory, while the open source community, in a majority of cases, builds for builders. You are looking for a slice that is a rarity and measuring Supabase against this metric - maybe you should look for other "evidences" to know if this is a good enough platform. Say, the company's valuation, or how many commercial tools offer seamless integration to Supabase, how many UI builders accept Supabase as a backend - these are business decisions made because there is demand from serious paying users. Wouldn't you say Supabase is solid by these measures?
From my long experience in the field, I have seen many well-built robust internal and client-facing enterprise-grade softwares and mobile apps that use Supabase. Not everyone is just free-tiering for MVPs and PoCs on Supabase. Even a search on this subreddit gives results including: [https://www.reddit.com/r/Supabase/comments/1iesvz0/what\_are\_some\_examples\_of\_large\_production\_apps/](https://www.reddit.com/r/Supabase/comments/1iesvz0/what_are_some_examples_of_large_production_apps/) Even though outdated, this repo used to collect Supabase projects: [https://github.com/zernonia/madewithsupabase](https://github.com/zernonia/madewithsupabase)