bgevconsultancy consolidates document storage under Supabase

Helm-v2 is moving uploaded documents from Cloudflare's file storage into the same vendor already handling its database.

infrastructuresecurity

This is mostly an operational change, not a new legal workflow. But it simplifies an important part of the product: documents now have one home alongside the underlying application data, rather than being split across Supabase and Cloudflare.

The team has also added checks around storing files and controlling download access. That matters because document storage is the layer beneath uploads, conversions and retrieval. The change also lays groundwork for later restrictions that keep stored material private by default.

So what Legal teams and product leaders weighing hosting choices should care because simpler document storage can make permissions and operational ownership easier to manage.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

SHA	Subject	Author	Date
`59e850d5`	T4.1 supabase storage replace r2	Clava Stripdown	2026-07-23	↗ GitHub

SHA

Subject

Author

Date

59e850d5

T4.1 supabase storage replace r2

Clava Stripdown

2026-07-23

↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-956.md from inside the repo you want the changes in.

bgevconsultancy consolidates document storage under Supabase

Commits in this thread

Capture this thread into my fork