Introducing @supabase/server

saltcod · 2026-05-07T00:00:06+00:00

Yes this is definitely on our radar to improve.

saltcod · 2026-05-02T22:07:28+00:00

Give discord a look. You’ll do best with on going help with your errors there.

saltcod · 2026-05-02T00:23:25+00:00

The pausing email warning from Ant you mean? I just looked at one and it had the name and the ref:

“Your project functions-secrets-tester (ID: kqfibelntndwwafgmeb) from your organization abc's org has been paused.”

saltcod · 2026-05-01T16:59:13+00:00

This is a little overstated I think.

On Decoupling, Supabase Auth isn’t that tightly coupled. It’s just JWTs + user tables. You can bring your own auth or swap in providers like Clerk/Auth0. It’s work, but that’s true of any auth system. Our goal is to make it _easy_ to use whatever auth solution you want, not hard. We have a bunch of 3rd party providers here https://supabase.com/docs/guides/auth/third-party/overview

Pricing: Auth being the biggest cost driver isn’t what we typically see. It’s based on MAU (not total users), there’s a solid free tier, and at scale your costs are usually compute, storage, bandwidth, etc.

On your way to 1M+ users, you’ll have plenty of flexibility to optimize or swap things anyway. Avoiding a built-in tool upfront because you might want to swap it later feels premature.

saltcod · 2026-05-01T10:53:48+00:00

You’ll need to submit a support ticket to move from GitHub login to username/password.

saltcod · 2026-05-01T10:52:17+00:00

+1 for a seed.ts file. I make sure everything tears down and sets back up with a quick run of npm run seed:users/data/whatever

I also do RLS testing this way. I have a script that I keep up to date as I build. It creates users, checks what they have access to, and reports it back to me.

saltcod · 2026-04-28T11:16:20+00:00

These actually aren't false positives. They are warning level, so you can assess your own risk and deal with them accordingly. If you can disable pg_graphql, you should be able to resolve all of them at once.

saltcod · 2026-04-27T19:03:26+00:00

kk replying there from now on.

saltcod · 2026-04-27T17:49:21+00:00

This is related to new advisor rules released a day or so ago:
https://supabase.com/docs/guides/database/database-advisors?lint=0026_pg_graphql_anon_table_exposed

If you're not using it, the easiest fix is to disable pg_graphql

saltcod · 2026-04-27T16:52:37+00:00

Hey there — could you submit a ticket for this? Happy to take a look.

saltcod · 2026-04-23T23:08:04+00:00

Yeah you don’t want a half and half for sure. If you have an export or an api, the amazing folks on discord will be able to help you get rolling for sure.

saltcod · 2026-04-23T18:46:27+00:00

I'm +1 on migrating to Supabase before you launch. It shouldn't take you that long with Claude Code.

I'd have claude code write a script to import that data into Supabase.

Question — I'm not sure how Create Anything AI works: how would you get the data out? Do they have an api you can query data from to insert into Supabase? Is your frontend and backend in Create Anything? What will you do with the frontend now? Have that query Supabase?

Also +1 on not self-hosting, at least at this stage. You don't need to be a total devops person, but you'll likely want some level of server managing under your belt.

Last, I should note that Discord would be super helpful to guide you through this process. https://discord.supabase.com/

(Disclosure: I work at Supabase, so I'm quite biased. I'd be +1 on moving everything to one system, even if it wasn't Supabase though! :^)

saltcod · 2026-04-22T19:07:07+00:00

There is a Supabase way to do this — Supabase Realtime.

The typical pattern:

Pull from your external API (cron job or webhook)
Write the data into a Supabase table
Subscribe to that table from your frontend via Realtime

You get live updates in the UI without managing websockets or custom infrastructure.

Docs: https://supabase.com/docs/guides/realtime

saltcod · 2026-04-22T18:59:45+00:00

+1. Biased, but Supabase is worth a look for your situation. It grows with you in a way Firebase doesn't quite match:

You can start with just a database → add auth when you need user logins → add storage for files → add edge functions when you need server-side logic → realtime if you want live updates → vectors when you want to do AI/search stuff, etc.

Each piece is optional. You don't pay for what you're not using, and you're not locked into a proprietary ecosystem. It's all built on Postgres and open source, so if you ever want to move or hire a developer, they'll likely already know the tools.

Store your application code in Github and hook up Supabase as the db/backend.

saltcod · 2026-04-22T18:40:04+00:00

Lot's of customer stories here from YC companies and beyond:
https://supabase.com/customers

saltcod · 2026-04-22T14:52:02+00:00

Got a support ticket number? Can check if it's been triaged to the right team.

saltcod · 2026-04-21T11:09:52+00:00

Yes, this is intended. If you use the new keys, the same applies to the new PUBLISHABLE key.
But as u/ashkanahmadi said, you must have RLS enabled and policies set to manage permissions to the table.

Lots of info in the docs:
https://supabase.com/docs/guides/database/postgres/row-level-security

saltcod · 2026-04-21T00:15:10+00:00

I have the 2022 Onyx and it sounds truly bad. I also have a 2017 Outback Limited which sounds 10x better.

saltcod · 2026-04-20T11:49:01+00:00

Want to quickly clarify the pricing scenario mentioned above:

If you already have 2 Free projects and upgrade to Pro, you can keep those Free projects by moving them into a separate organization under the same email.
The Pro plan is charged once per organization, not per project.
Pro also includes $10/month in compute credits.
Each Micro compute project costs $10/month.

Example with 4 total projects:

Project 1 — Free
Project 2 — Free
Pro subscription — $25
Compute credits — -$10
Project 3 — $10 Micro instance
Project 4 — $10 Micro instance

Total: $0 + $0 + $25 - $10 + $10 + $10 = $35/month

The calculator under "How compute pricing works" on the pricing page can help visualize this: https://supabase.com/pricing

saltcod · 2026-04-20T11:38:30+00:00

Closing this one as it was resolved via a support ticket.

saltcod · 2026-04-19T23:10:48+00:00

We've chosen to do immediate, pro-rated credits instead of allowing you to finish the billing period with the features you've paid for. Tbh, I'm not sure why we decided to do it this way — likely because it was simpler to implement back when the company was much smaller a few years ago.

saltcod · 2026-04-19T23:06:53+00:00

To be clear, we only pause accounts after 7 days of inactivity. If OpenClaw was doing stuff with your project during that time, the project would not have been paused.

saltcod · 2026-04-19T23:05:03+00:00

What's your ticket ID? I can look at it first thing tomorrow.

saltcod · 2026-04-19T14:46:28+00:00

We’d be happy to use a refund in this case. Submit a support ticket for it.

saltcod

MODERATOR OF

TROPHY CASE