This content originally appeared on DEV Community and was authored by Kyle Ledbetter

Public Report Sharing for Supabase: Stop Being Your Team’s Analytics Middleman

TL;DR: We just shipped one-click public sharing for Supabase analytics reports. Your stakeholders can now self-serve their metrics instead of asking you to run queries.

The Problem Every Developer Knows

It’s 3 PM on a Thursday. You’re deep in a complex feature implementation. Then Slack lights up:

PM: “Hey, can you pull the user retention numbers for last month?”

Founder: “What’s our MRR growth looking like?”

Investor: “Can you send me the latest engagement metrics?”

You have two choices:

Context-switch, write SQL queries, format the results, send them over (there goes your afternoon)
Give them database access (security nightmare)

Both options are terrible. And you’ll be doing it again next week.

What We Built

Dreambase connects directly to your Supabase database and generates analytics reports using AI. We just added public report sharing—one click to make any report publicly accessible.

The workflow:

Your PM/founder generates a report in Dreambase (no SQL required)
They click the share button in the report toolbar
Toggle “Report Visibility” from Private to Public
Copy the URL and share it

You’re not involved. They get their metrics. You keep coding.

How It Actually Works

For Internal Teams

By default, reports are private. Workspace Owners, Admins, and Project Managers already have access based on their roles. They just copy the internal link and share it in Slack.

No configuration. No tickets. No interrupting developers.

For External Stakeholders

When they need to share outside the workspace (investors, advisors, customers), they:

Click share button
Toggle to Public
Copy the new public URL
Save changes

The report is now accessible to anyone with the link. No login required. A globe icon appears next to public reports so everyone knows what’s shared.

Interactive Data, Not Static Images

This is the key part: reports query your Supabase database directly. When the data updates, the report updates. Share the link once, stakeholders interact with the data.

No more “can you regenerate that report with updated numbers?” They can generate a new report in seconds themselves.

Why This Matters for Supabase

When your analytics connect directly to your Supabase database (your actual source of truth) there’s no reason to treat insights like they’re locked in a vault.

Traditional analytics tools were built around the assumption that data lives in a separate system, accessed by a separate team, exported to separate files. That made sense when analytics required complex ETL pipelines and dedicated data warehouses.

But Dreambase connects directly to Supabase. Your product data is already there. Your analytics should flow as easily as your data flows.

If you can share a Google Doc or a Figma file with a link, you should be able to share a product analytics report the same way.

That’s what we built.

Why This Matters for Dev Teams

You stop being the analytics middleman.

Your stakeholders can:

Generate their own reports (AI writes the SQL)
Share reports with each other
Bookmark public links for recurring metrics
See live data without asking for updates

You maintain security.

Public reports are read-only views. No database credentials exposed. No write access. Toggle back to private anytime.

Internal reports respect workspace permissions. You control who has access at the workspace and project level.

Your Supabase data stays in Supabase.

No JavaScript tracking libraries to install. No data piping to external platforms. No event schemas to maintain. Dreambase connects directly via PostgREST.

Your source of truth remains your source of truth.

Real Use Cases

Investor Updates

Your founder generates a monthly metrics report and shares the public link. Investors bookmark it. They check progress whenever they want. Nobody asks you to pull numbers.

Team Dashboards

Your PM creates reports for feature adoption, user engagement, conversion funnels. They share them with the team. Everyone sees the same data. No more “what’s the latest on X?” in Slack.

Customer Transparency

Building in public? Share usage stats or uptime metrics. Your customers see the same data you see. No custom status page to build and maintain.

Cross-Functional Collaboration

Share reports with contractors, advisors, or part-time team members who don’t need full workspace access. They get insights without database credentials.

Technical Details

Performance

Reports are cached at the edge
Sub-second load times globally
Optimized for mobile viewing

Open Graph Previews

Dynamically generated preview images for each report
Shows key metrics when shared in Slack/Discord/Twitter
No more “click this random URL and trust me”

Security Model

Public reports are read-only
No database credentials in URLs
Toggle visibility anytime
Workspace-level permission controls

Integration

Direct PostgREST connection to Supabase
Respects your RLS policies
Works with your existing Supabase setup
No schema changes required

See It Live

Here’s a public report we’re using ourselves:
Pickleball Court Analytics

Notice:

Loads instantly
Shows live data
Clean public page
Preview when you share the link

Getting Started

Public report sharing is available now for all Dreambase users, including the free tier.

Sign up at dreambase.ai
Connect your Supabase project (30 seconds, read-only access)
Generate a report (AI writes the queries)
Click share → toggle public → copy link

Your stakeholders can now self-serve their analytics. You can get back to building features.

Why We Built This

We’re developers too. We’ve been the analytics middleman. We’ve context-switched out of deep work to run SQL queries for stakeholders who just want to see if a number went up or down.

It’s a waste of developer time. And it’s a waste of stakeholder time waiting for you.

When your analytics connect directly to Supabase—your actual source of truth—there’s no reason insights should require developer intervention.

If your PM can share a Google Doc, they should be able to share an analytics report.