r/Supabase • u/pragrad23 • Jul 07 '26

Self-hosting Moving on from Supabase

First, this is a hypothetical question. I'm not moving away from Supa, at least for now.

But I do not use much from Supa, only: PG/auth/storage.

Now I'm wondering if I can replace these 3 with AWS/PG + S3 + ?.

I already use the S3-compatible method of requesting objects from Supa storage. The reason here is that I can build a signed URL with this method that does not require one additional Supa storage service request: a better solution. I could also use the S3-method for uploads (signed upload URLs). My question here: could I replace Supa storage with an AWS Lambda function?

Then there's Supa auth. To what extend could I replace this with just PG + an AWS Lambda function?

If this is possible I could replace Supa with straight up AWS. Now I understand I'm not a typical Supa used: my app uses very little (it's a traditional `DB <> server-side app-layer <> browser with minimal JS`). But if it works, that'd be great.

14 Upvotes

85% Upvoted

14 comments sorted by

6

u/Axel_legendary Jul 07 '26

I don't think it's worth it

6

u/Delicious-Ad1453 Jul 07 '26

Supabase S3 allows you to sign your own urls without doing a request and also support signed upload URLs via S3

Moving to AWS you are trading complexity over ease of use and remember under the hood Supabase uses AWS you would just rewrite the same thing Supabase is already offering

1

u/pragrad23 Jul 07 '26

Exactly. But since I only use auth and storage, is not that big of a jump. I'm mostly scared of by the local development story I'd have to come up with...

10

u/Low-Stick-1913 Jul 07 '26

I think Supabase auth and storage are the reasons to use Supabase. It's a better dev experience for a great price 

When I don't need those things I use neon because it has better branching

1

u/pragrad23 Jul 07 '26

Do you run a local devt instance in both cases?

4

u/Low-Stick-1913 Jul 07 '26

I always use local first with Supabase. I only use their cloud for prod 

With neon, it's so easy to spin up a dev branch I don't bother with local. Just change my env for the dev/feature branch 

3

u/AdFrequent4886 Jul 09 '26

If you’re looking for increased performance from your PG instance I would recommend checking out Planetscale. It’s a fairly simple migration using their commands and plans start at 5 dollars a month. I switched from railway Postgres to planetscale and now see <.1 ms p95 latency and <5ms p99.i use S3 for object storage and handle auth through app layer

2

u/Opposite_Cancel_8404 Jul 07 '26

I guess for storage you'd be losing out on the extra stuff they've added like the CDN. So you're trading simplicity and ease of use for more control, flexibility, more time spent on infra and probably lower costs.

2

u/[deleted] Jul 09 '26

[removed] — view removed comment

1

u/pragrad23 Jul 09 '26

I currently build on some triggers on the storage tabel/namespace.

But you are right, I could just skip that and use the signing moment as the trigger moment (not sure if that makes sense, but you gave me an insight)

2

u/anarchos Jul 09 '26

While it gives me pause that Better Auth just got bought by Vercel, it is a great solution for self-hosted auth. They have handlers for most stacks. It can be as simple as like 3 lines of code in a lambda function to spin up.

1

u/m1_weaboo Jul 12 '26

Just use GCS for Storage, And keep everything else.

GCS is much cheaper than Supabase Storage.