Rescue work
公開状態のSupabaseデータベースをロックダウン
行レベルセキュリティを適切に記述し、公開匿名キーを通じてある顧客が別の顧客のデータを読み取れないようにします。
What you get
- 現在のポリシーと公開されているビューのテーブルごとのレビュー
- データを含むすべてのテーブルをカバーする行レベルセキュリティポリシー
- テナント間の読み取りと書き込みが拒否されることを証明するポリシーテスト
- クライアントコードからのサービスロールキーの使用を移動
- 新しいテーブルを追加する前に確認すべき点に関する短いメモ
Usually built with
Supabase
PostgreSQL
pgTAP
TypeScript
A guide, not a requirement — sellers propose what suits your situation.
Nobody offers this yet
No seller has published this service yet. Ask anyway — the request goes to the marketplace and sellers who do this kind of work can answer it.
Or publish it yourself if this is your work.
Close to this
It works locally but dies in productionThe gap between your laptop and your server, closed: environment, build, secrets and runtime differences found and fixed.from €900CI pipeline that stops your agent shipping bugsTypes, lint, tests and build checks running on every pull request, so broken generated code never reaches your main branch.from €900Untangle dependency hell and get the build greenConflicting versions, abandoned packages and a lockfile nobody trusts, resolved into a build that installs cleanly.from €900Backups and restore drills for a database with noneAutomated backups are half the job. I also prove a restore works, with the recovery time written down.from €700Rotate leaked keys and purge secrets from your repoAPI keys committed to git, hard-coded in the client or pasted into a chat: found, rotated and prevented from returning.from €600Second pair of eyes before you launchAn experienced review of what your agent built, focused on what breaks first when real users arrive.from €600
What will it cost?
Four questions, an instant range. No account, no waiting.
Estimated range
€900 – €1,800
3-5
Based on the catalogue guide — nobody has published this service yet, so there is no market price to work from. An estimate, not a quote: a seller prices the real job once they have read it.
Request a quote
Nobody has published this service yet.