Grant guide

Supabase grant database with RLS and audit records

FundingLens stores organisation profiles, funding opportunities, source facts, AI audit records and billing state in a Supabase-backed data model with RLS controls.

Best for

Teams deciding where to spend application time

Technical buyers and operators reviewing the data architecture behind FundingLens grant intelligence.

Use this page to

Make the first review more concrete

Understand a Supabase-backed grant database with RLS and audit records.

Review workflow

What FundingLens helps you do

Keep source facts, caveats and next actions together so your team can decide what deserves attention before application work starts.

01

Use public source tables for reviewed opportunities while keeping organisation profiles, saved opportunities and billing state protected by membership policies.

02

Store source URL, fetched timestamp, raw fields, AI summary, fit reasoning, eligibility caveats, confidence and review status.

03

Keep service-only operations such as ingestion, billing sync and suppression writes behind server-side routes and privileged keys.

Readiness checks

  • RLS enabled on exposed tables.
  • Public opportunities separated from private workspace data.
  • Source facts and AI audit records linked.
  • Server-only writes used for sensitive operations.
  • Retention and deletion runbooks documented.

Eligibility caveats

  • Database architecture does not remove the need for policy review and regression tests.
  • Service-role secrets must never be exposed to browsers.
  • FundingLens still needs human review for ambiguous funding data.

Source references

Related FundingLens pages