Threads
Loading user profile...
Terry Sutton announced a new feature allowing developers to provision a Supabase project using the Stripe CLI as part of the Stripe Projects developer preview. This integration simplifies the setup process by providing a full Supabase project with one command. A user inquired about the integration's automatic capabilities with Stripe.
Terry Sutton is seeking volunteers for the SupaSquad to support the Supabase subreddit. The goal is to enhance community engagement by answering questions, guiding new users, and maintaining high-quality discussions. Existing contributors are encouraged to apply, while new participants are invited to get involved before applying.
Claude / Codex / etc will make very quick work of this. These days, I would use a static site with markdown if everything was truly static, otherwise I'd make a custom admin for managing content with Supabase as the backend. If you need all of WordPress, sure go ahead, but if you just need some of the features of a CMS, I would not hesitate to build it myself today.
Closing this thread due to an abundance of ambulance chasing. Please reach out to support if you need more help and the'll point you in the right direction.
You can definitely upgrade, get the report, and then downgrade. But usually teams who need SOC 2 don't just need the paper. They also need project scoped dev permissions, sso, more backups, vendor-backed support SLA's, etc.
Please file a support request so we can take a look
Shooting you a dm to get your support ticket id.
Please submit a support ticket and we'll be able to assist you.
Will handle via support.
What error are you seeing? Anything in your console?
Hey there — very likely running out of memory. A good place to start would be to find and fix the heavy queries and restart your project to clear enough resources to restart the db
\> about 0.035 GB on disk, a handful of accounts Happy to take a look at what's causing this. We have many surprisingly large projects running on the free tier. Sending you a dm to get some more details. (I'm from supabase)
If using a framework: https://supabase.com/ui
Yes as others have said, you can upgrade and downgrade as you like as long as you're within the limits of the free plan. Note that limits reset at the end of the billing period — might be helpful if you're close to the end.
Looks like others have chimed in here with similar: you don’t need enterprise for hipaa. You can to the teams plan with the hipaa addon which would be a bit cheaper With self-hosting on AWS you have to manage and maintain **just the DB** \- Supabase provides HIPAA coverage for everything else, edge, realtime, storage
Cool project! Nicely done. You should post this on Discord (in #showcase) as well!
Replied in the support ticket.
Hey again u/No-Estimate-362! Wanted to follow up here — our legal team reached out to you directly via email with responses to your DPA questions. Hopefully that helped with some of the questions you had. We're actively building out our public privacy documentation, so a lot of this will be more easily accessible soon, but we wanted to make sure you got real answers in the meantime. Thanks again. We really appreciate these thoughtful questions!
Hey — thanks for the detailed writeup, and very sorry for the disruption to your project. We became aware of an issue affecting Edge Function deployments at approximately 17:00 UTC on July 30. Since then, our teams have been focused on mitigating the issue and restoring affected deployments. As part of our response, we have: * rolled back a recent code change associated with the issue * released CLI v2.111.0 so new deployments are not affected * continued working with the remaining affected customers to fix their existing deployments New deployments using the updated CLI should no longer run into this issue. We will continue assisting affected customers until all remaining cases have been resolved. If the manual fix support applied to your project didn't resolve the 409, that means you're still in the "remaining cases" bucket. Please reply on your existing ticket noting it recurred (or DM me your project ref / ticket #) and I'll get it escalated so someone actively works your specific functions rather than leaving you to retry.
Hey there! Thanks for the thoughtful questions. We've been working through these with our legal team. A few of the questions have led to improvements we're making to our documentation: * We're updating the DPA to better clarify the signing process and how it becomes effective. * We're adding countries to our public subprocessor list so that information is easier to find. * We're still confirming the questions around AI subprocessors and data residency/support access We'll update this thread as those changes land. In the meantime, if you're in the middle of a compliance review, feel free to reach out to [legal@supabase.com]() with any organization-specific questions.
Sorry you're having issues here. We're facing extremely tight capacity constraints right now with our infra provider. We've working around the clock on getting more and we're starting to see capacity improvements today. Appreciate your patience.
These are almost always an account issue. Happy to look into this with a support ticket id.
very cool. thanks for sharing!
Hey there — you can keep your free projects while on a Pro plan. You just need to create a new org and move the projects there. We keep free and paid projects separate for billing and usage purposes. [https://supabase.com/docs/guides/troubleshooting/keeping-free-projects-after-pro-upgrade-Kf9Xm2](https://supabase.com/docs/guides/troubleshooting/keeping-free-projects-after-pro-upgrade-Kf9Xm2)
Sorry you’ve run into this. Our team needs to manually address this. Will escalate it internally.
Yep [https://railway.com/deploy/supabase](https://railway.com/deploy/supabase) But the getting started guide has gotten much simpler lately for any vps [https://supabase.com/docs/guides/self-hosting/docker](https://supabase.com/docs/guides/self-hosting/docker)
Would make a good thread on Discord — the folks there are extremely good.
If you go with Supabase + a js framework, I'd definitely start here [https://supabase.com/ui/docs/getting-started/quickstart](https://supabase.com/ui/docs/getting-started/quickstart)
Hi there — feel free to dm me your ticket number and I can look into this for you.
Please submit a support ticket for this — we'll likely need to manually restart your instance. In the meantime, Discord would be a great place to get debugging help on why it's happening regularly.
We're experiencing some latency with our management api. Status updates here as soon as we have them: [https://status.supabase.com/incidents/9p4j7rw8rcdb](https://status.supabase.com/incidents/9p4j7rw8rcdb)
Following up here from our legal team: \> To really discuss this issue we should separate two things people often blend: where your data is *stored*, and which jurisdictions have *authority over the provider*. Choosing an EU region keeps your core project data and backups resident in that region, but you're right that geography alone doesn't resolve the second question of compelled disclosure, and this isn't specific to Supabase. Any U.S. company or any provider with a sufficient US nexus that has possession, custody, or control of data can be subject to US legal process regardless of whether the data is stored in the EU -- including AWS, Microsoft Azure, and Google Cloud. Regulators and courts have grappled with the tension here with GDPR, which is why SCCs, TIAs, and supplemental safeguards exist. The supplemental measure that actually addresses compelled disclosure is encryption where Supabase holds no key (region selection and SCCs don't). \> What actually changes the analysis isn't location, it's whether the provider can decrypt your data. Standard, provider-managed encryption doesn't help here, because the provider holding the keys can be compelled to use them. What does help is encrypting sensitive data with keys we never hold (client-side or application-layer encryption), then Supabase may only be capable of producing encrypted data because we would not have the ability to decrypt it ourselves. That's the viable middle path between "just pick a region" and "self-host everything." Region selection plus our DPA (EU SCCs, defined security safeguards) covers your residency and transfer obligations; customer-controlled encryption is what addresses the access concern. And it's also worth nothing that we would challenge government orders that conflict with applicable law rather than disclosing on demand. Of course users can also do client side encryption on top of that and have control over their own keys. Hope this helps!
nice! these should be enough to get you going I think: [https://github.com/supabase/supabase/blob/master/DEVELOPERS.md](https://github.com/supabase/supabase/blob/master/DEVELOPERS.md) [https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
hey u/Cold_Interaction_598 sorry about the delay here. Missed this comment. Re: backups — the storage team is looking at ideas here. Could you say more about the use case you're trying to solve for here?
Copying from a recent self-hosting thread: \> We have no plans for multi-project at this point. There's a ton of complexity in building and maintaining a multi operator, and then we'd end up handing a lot of that complexity over to you. Separating instances into their own servers is a good thing. [https://www.reddit.com/r/Supabase/comments/1u147jz/comment/oqoos0t/](https://www.reddit.com/r/Supabase/comments/1u147jz/comment/oqoos0t/)
Self-hosting updates here! [https://www.reddit.com/r/Supabase/comments/1u147jz/recent\_updates\_to\_selfhosting/](https://www.reddit.com/r/Supabase/comments/1u147jz/recent_updates_to_selfhosting/)
Nice one! This would be great in the docs — maybe under troubleshooting guides — if interested! [https://supabase.com/docs/guides/troubleshooting](https://supabase.com/docs/guides/troubleshooting)
could be this from us-east-2 [https://status.supabase.com/](https://status.supabase.com/)
Unfortunately there isn't currently a tool for this. Here's the guide for migrating regions: [https://supabase.com/docs/guides/platform/migrating-within-supabase](https://supabase.com/docs/guides/platform/migrating-within-supabase)
Would love to have your help with a better doc for that! Very cool to see it running on a pi!
Appreciate this frustration. See my previous comment about why we do this: [https://www.reddit.com/r/Supabase/comments/1u147jz/comment/oqoos0t/](https://www.reddit.com/r/Supabase/comments/1u147jz/comment/oqoos0t/)
Good question! There's actually so many good reasons. Here's a few: 1. Reduced adoption risk: * Even customers who never self-host care that they can * Makes the managed platform easier to adopt because it reduces perceived lock-in 2. Compliance requirements * Some organizations can't use our hosted offering 3. Open source stewardship * Since supabase itself is built on a bunch of open source projects, its important to us to give back * Investing reinforces the core promise that attracted many users to us in the first place 4. Forcing function for product quality and portability * Running the platform outside of our hosted infra forces better docs, reproducible deployments, etc * Improvements flow back into hosted * The entire platform becomes more standardized no matter where it's deployed 5. More Supabase begets more Supabase * A self-hosted deployment is still a Supabase deployment * Devs learn the APIs, build integrations, create content, train coworkers, etc * Growing the ecosystem is valuable regardless of where it runs These are just a few off the top of my head!
Appreciate the feedback. Would love to hear more about docs confusion if you've got any specific examples I could go from. The 3rd party auth one is interesting — first google result is a landing page, which links to the providers, all of which list the config option near the top. Maybe these were added since you last tried? In any case, love to get any more feedback you have like this.
We have no plans for multi-project at this point. There's a ton of complexity in building and maintaining a multi operator, and then we'd end up handing a lot of that complexity over to you. Separating instances into their own servers is a good thing.
we got u!
It sounds like you're already aware of this, but for others who read this: Functions automatically run in the region closest to the user making the request. But if the function is performing db or storage operations, you can choose to run in the same region as your db. Docs: [https://supabase.com/docs/guides/functions/regional-invocation](https://supabase.com/docs/guides/functions/regional-invocation)
Love to hear more about how it's changed your life! :\^)
What way do you mean? We already have a Python sdk, but I'm sure you've already seen that. [https://supabase.com/docs/reference/python/start](https://supabase.com/docs/reference/python/start)
\^yes, this is basically our position.
Hey there. Sorry you're running into this. This is likely related to this dns issue [https://status.supabase.com/incidents/308hm84ntd47](https://status.supabase.com/incidents/308hm84ntd47) We'll provide updates there as soon as we have them.
Indeed, still working on the community round part. Unfortunately we don't allow transferring shares :\^)
Have you seen the new RLS Testing tool in the Dashboard? [https://github.com/orgs/supabase/discussions/45233](https://github.com/orgs/supabase/discussions/45233)