blinking-light-cirlce
fogbender-logo

Observability for Supabase

Hosted Grafana & Prometheus observability stack for Supabase

Why Supafana?

Easy-to-setup, persistent, and secure observability for Supabase! Supafana removes the need to suddenly learn how to deploy container infrastructure.

Hosted

If you use hosted Supabase, chances are, you have an appreciation for having someone else handle infrastructure. Say, you want advanced observability for your Supa DB, but got better things to do than sort out Grafana deployment? Supafana is for you!

One-click setup

When things are going wrong with your production DB, the last thing you want is drop everything and march down the road of solving observability infrastricture. Supafana offers a one-click alternative.

Persistent historical data

One of the issues with running supabase-grafana as a vanilla container is having all historical data wiped on container restart. Supafana ensures historical data remains intact if your observability instance reboots.

Secure

supabase-grafana requires a highly-sensitive service_role key. Unless you’re running your Grafana container on the intranet, it’s imperative to take security extremely seriously—for example, to keep the dashboard behind https://.

Intranet

To be clear, if you are running supabase-grafana on the intranet, it’s still imperative to take security extremely seriously.

Alerts coming soon

Supafana observability instances come pre-configured with a working SMTP setup, ready for Grafana Alerting. Alerting!

Supported

The Supafana team offers round-the-clock fanatical support to all customer teams via in-app team-to-team messaging.

Database monitoring
without a Ph.D. in Database Monitoring

The rather unfortunate NoSQL chapter in the storied almanach of database technology wasn’t born so much as a revolt against relational algebra or SQL per se, but as a totally understandable pushback against the mind-shattering complexity of getting going and maintaining a relational database in a non-enterprise—i.e. startup—setting. While the rise of cloud computing platforms unambiguously ushered in a renaissance for Postgres and friends, the getting started bar remained unacceptably high until Supabase made its debut.


Supabase managed to bring two fairly different camps of folks—the "I’ll never use Firebase because not relational" and the "I’ll suffer through the indignities of handwavy data integrity because I’m not terraforming" ones—under one, gigantic, expanding roof. This is an enormous accomplishment that will reverberate across the internetverse for decades.


However, at least at the time of this writing, the skillset delta between running a Supabase Postgres project and monitoring a Supabase Postgres project remains a tad bit galactic. This is not an accident—to properly fix this, Supabase has to spin up what would essentially amount to another—observability-focused—company.


And while we’d never bet against Supabase, we figure that a) they’re too focused on core business to build an observability company and b) they’re very likely to continue dragging other database companies for filth with increasing velocity, becoming an attractive host for us, Remoras.


With this, we invite you to observe in peace, monitor with confidence, and stay hydrated with Supafana.

TRUSTED BY SUPATEAMS FROM ACROSS SUPASPACETIME

  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9
  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9
  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9
  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9
  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9
  • Customer 0
  • Customer 1
  • Customer 2
  • Customer 3
  • Customer 4
  • Customer 5
  • Customer 6
  • Customer 7
  • Customer 8
  • Customer 9

Have you heard?

Bromley McAlister Bromley McAlister
Riot Forever

Checked out Supafana, and it’s rad, but the cloud just isn’t for me—I’m all about that rack and stack life. So I whipped up a similar setup in our colo in like half a Saturday. It’ll be safe here till spring when we’re leveling up to a killer new DC.

Avery Baldwin Avery Baldwin
Spartan

Supafana is an incredible service with a lot of potential. Their team’s innovation and dedication are truly impressive. However, our infrastructure requirements are quite specific, and since Supafana uses Nix, it just doesn’t align with our current tech stack. We wish them the best and look forward to seeing their continued success!

Tanner Lexington Tanner Lexington
Anchorite Shrugged

My understanding is Supafana uses Elixir as its application server, and while the service looks really useful, I simply refuse to pay for SaaS not written in Rust. Best of luck, though!

Rajesh Viraj Singh Rajesh Viraj Singh
Boldwave

While I have a lot of respect for what Supafana has achieved, I can’t justify using a service that isn’t open source, especially when it leverages the fully open-source Supabase. It’s important to support and use tools that contribute back to the community and maintain the transparency and collaboration that open-source projects thrive on. Good luck to Supafana, but it’s just not the right fit for our principles and needs.

Lars Müller Lars Müller
Datengarten

Supafana’s got some bold claims, but their love for SQL and Supabase just doesn’t cut it for me. Anyone who’s still stuck on relational databases clearly doesn’t get the power and flexibility of NoSQL. Why would I waste my time with a service that doesn’t embrace the future of database technology? No thanks, Supafana. I’ll stick with solutions that understand the NoSQL revolution.

Lenin Arakawa Lenin Arakawa
Wakeborough Capital

Even though they allegedly went through YC, it doesn’t look like they’ve raised much capital. There’s no way you should trust a startup that hasn’t raised at least 20 million dollars with your core infrastracture, which metrics and observability obviously is—I’d rather trust a free Fly.io container than take a gamble on Supafana.

Annika Bertström Annika Bertström
Snåljåp Lösningar

As a founder, you’ve got to be frugal to survive and grow. Paying for Supabase? That’s just crazy when you can snag free credits from AWS and use RDS, then hop over to Azure for Azure SQL Database, and finally switch to GCP for Cloud SQL for PostgreSQL. But paying for Supafana? That’s downright ridiculous! If you know how to write proper SQL, you don’t need all those fancy metrics or monitoring. Smart founders manage their resources wisely and don’t fall for such obvious gimmicks.

Anton Melnikov Anton Melnikov
Shizgara Foreva

Postgres normal database, but I believe MySQL more superior across layers, plus reliability. Also, Postgres appears to been founded by Stonebraker, notorious hippie from the Berkeley with zero credibility.

Jean-Louis Deschamps Jean-Louis Deschamps
Mistralytics

Attempted to use Supafana, it sounds intriguing, but it appears to require something called a "supabase", which je ne sais quoi or why we would use it. Interesting project though, bonne chance!

Bob Sobchak Bob Sobchak
AC Expeditions LLC

Looks like Supafana is built by Fogbender Software, Inc., and Fogbender Software appears to be based in Oakland, California. I can't believe anyone would voluntarily choose to live in California, not to mention Oakland. How are these people still alive and where do they even get groceries and clean water?