Boundary: repeatable file-access checks for Supabase staging projects

[Lians-ai]

I'm building Boundary and looking for solo founders or small teams (roughly 2–10 people) running a real Supabase product to try the current beta for free. No card, subscription or purchase is required for this beta trial. Your own hosting costs remain yours.

Boundary is an experimental local checker for a specific file and document record in a supported Supabase staging project. It checks access as the owner, another customer and someone signed out, then lets you rerun the same checks after changes. It requires a separate staging project, two ordinary test accounts, synthetic data and Node.js 22+. It is not a full security audit or a guarantee that an application is secure.

Try the two-customer demo, or get the local checker and setup instructions. The demo uses synthetic data; it is not evidence from a customer deployment.

If this fits your app, reply here or email beirnewebsites@gmail.com with a non-sensitive description of your setup. I'd like to learn where you get stuck, whether the result is useful, and whether you would rerun it after a real change. Honest negative feedback is welcome; no testimonial required.

If you already maintain these tests, what does your current setup handle well, and what is still tedious? Existing pgTAP or integration tests may already cover your needs.

Please keep credentials and private records local. No production access or customer data is needed.