Hey r/supabase 👋
I’m one of the developers behind Reloops, an opensource creative collaboration and asset review tool we’ve been building with Supabase as a core part of the stack.
The idea is to combine file storage, organization, client review/approval, and feedback into a single workspace, something along the lines of Google Drive + Frame.io + Bynder + Ruttl.
We’d love some feedback from other Supabase builders, especially around the product and architecture.
GitHub: https://github.com/Reloops-App/Reloops
Some of the main features:
Current stack:
React + Supabase + Postgres + FFmpeg + OpenAI API + Screenshot API
One interesting thing about the website shown in the video:
We created it by putting the relevant prompts, references, and project files into Reloops, then exposing that context through MCP. We asked an agent to use Reloops as its long-form context while building the website.
Instead of repeatedly copying prompts, screenshots, files, and feedback into the agent, it could pull the project context directly from the workspace.
Mushroom_Large introduces Reloops, an open-source tool for creative collaboration and asset review, built using Supabase. They seek feedback on the product and architecture from other Supabase users. The tool integrates features like file storage, client review, and AI-powered search, using a stack that includes React, Supabase, and OpenAI API.
Love the Supabase + MCP setup! How are you handling row-level security for guest review links?
Nice stack. The website-capture + MCP context loop is the hard part. We do URL → hosted screenshot as an agent tool if you want capture separate from the review canvas: https://grabbit.live