some suggestions and making lots of assumptions …

  • If it’s for SEO it is probably publicly readable - Events like Gigs etc - are all public and you are keen to have this public on the Web [Implication - an external database is a sensible idea for WU reasons]

  • Using a Bubble App as the Editor for these events is convenient and practical. [Implying - Bubble is a low-cost way to implement your Event editing]

  • Logged-in Bubble users could edit the Supabase data via the API Connector - likely with a low volume of editing (comparing writes to reads). [Sure you don’t have autobinding, and privacy rules - but you have other benefits that are possibly more valuable to you]

That’s probably how I would do it - side step all the Users logged in where complexity. But still have an efficient Hybrid solution.

@asked111 top of your mind also :slight_smile:

1 Like