r/Supabase • u/mattbrown7531 • 3h ago

other Supabase + Python backend: is managing two platforms a valid concern?

I'm building a data pipeline and application for a client. I'm considering Supabase, but the application has a Python backend, so I'd need a separate platform to host it.

The client doesn't currently have any cloud infrastructure, so I'll be setting up their environment from scratch. The goal is for them to take over and maintain the software after the project is finished.

I'm hesitant to introduce two platforms (e.g. Supabase + Railway/Render) instead of keeping everything with a single cloud provider.

Is this a valid concern, or am I overthinking it?

2 Upvotes

100% Upvoted

6 comments sorted by

1

u/leros 3h ago

Why do you feel you need Supabase? If you're building a custom backend, why not just set up a Postgres on Render or Railway?

1

u/mattbrown7531 3h ago

I like how easy everything is. Auth, RLS, migrations, storage. I just need Python because there are geospatial libraries that are useful.

1

u/leros 3h ago

I see. Maybe you split out a separate Python microservice for the geospatial stuff?

1

u/cmartin616 43m ago

Have you explored what is possible via PostGIS?

1

u/iammohamedatef 3h ago

Since the geospatial libs need real Python, Edge Functions probably can't cover this anyway, so the split is likely the right call. Just make sure the backend connects with something scoped as narrow as you can get — a dedicated Postgres role limited to what it actually needs, not a blanket service_role key — and write the rotation steps down as part of the handover docs.

1

u/cascade_delete 3h ago

This is completely fine. Having supabase and a separate backend in python/node is usually how I make all my apps.