Supabase
Replies: 31 comments 44 replies
-
|
Great topic! Why do people give up on Supabase for certain projects? In France, we have a lot of companies that prefer to have their data at home. Sometimes for the wrong reason, but somtimes for the right reason. For example, because of GDPR issues or because they host health data and need HDS hosting (equivalent to HIPPAA). Today, I don't do these projects with Supabase. Because maintaining and updating the selft hosted version is way too complicated. An idea that would help would be to make it easier to use a postgresql exeterne, so that you can use existing skills in your organization, or take a managed version of postgresql somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate the feedback! This has been a fairly common notion with regard to matching regulatory requirements. By an external Postgresql - do you mean your own existing instance, managed by your team? A managed Postgres elsewhere (e.g., Aurora)? |
Beta Was this translation helpful? Give feedback.
-
|
I'm actually thinking of a managed instance elsewhere: it means you don't have to worry about database security, backups and snapshots. These things are pretty well mastered by others.... |
Beta Was this translation helpful? Give feedback.
-
|
Please open source or provide access to exactly same Supabase MCP experience, I was just pointed out to your post after bringing this up on discord. While Supabase currently onboards a ton of people via AI/vibe coding, you left us completely drowned when we moved to hosting our own instance. There is no a single MCP server on the market that supports the same set of commands or even as basic as your token usage. "The MCP execute_sql tool appears to only support SELECT queries and basic DML (INSERT/UPDATE/DELETE), not DDL statements." is basically what Cloude constantly points out when I'm trying to do anything via Google's toolbox and after spending multiple days searching even this gives a complete headache when doing anything now. Please do something for us here. 
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for asking! Some recent notes here -#39849 |
Beta Was this translation helpful? Give feedback.
-
|
Small note, my self hosted supabase is not running on local host, it's running on remote server. So the dev workflow works on on localhost while I use toolbox mcp to have AI work with the remote DB. Issue is that the toolcalls of postgres mcp does not match what your closed source mcp server offers that gives a better usability for AI to work with supabase. |
Beta Was this translation helpful? Give feedback.
-
|
Hello and thanks for all your hard work! Tell us about your setup: I deploy on Railway, with a Railway template I built myself. The template config automates almost all the self-hosting headache; networking, new DB passwords for each role, encryption keys, etc. At first, around January 2025, I was building a small digital product with a friend. This was on the Supabase hosted platform. We ended up scrapping our startup. However, I couldn't forget about the pain points I experienced with local dev during that time. Now, the main project is the Railway template itself for now. There is an example NextJS app included, which is a rough imitation of Trello. The goal was to test almost every Supabase feature; auth, studio, meta, storage, realtime, etc. How long have you been self-hosting? About one year. How would you describe yourself? I'm a solo dev, with a full-stack background. I consulted for years for a large financial company in Canada. My focus is growing towards "full-stack++", working towards some approximation of the competencies of a principal engineer. I strive to work across all layers of software delivery. This has gradually taken me to the infra space. I'm happy gaining competence in TCP/IP, Docker, shell scripting, systems-level programming, resilient multi-container architectures. This is all relatively new for me and self-hosting Supabase has been a great way to grow as a developer. What's actually working well for you? What's working well is the feeling that the Supabase stack is the endgame for product development. The last tech stack we'll need for quite some time. Almost everything you could ever need functionality-wise is here. That's a huge testament to how much thought went into designing the stack. So, if we can continue to improve the developer experience with Supabase, our productivity and ability to deliver value to the world will only improve from here. What made you choose self-hosted?
What parts of the experience have been smooth or even straightforward? Updating environment config per-service has been incredibly smooth. I've updated the Any unexpected wins? Figuring out how to version my email templates in code and integrate that into building the Auth image, was surprisingly easy once I took ownership for self-hosting. A few lines were added to a Dockerfile that bases from Supabase's official Auth image: FROM supabase/gotrue:v2.180.0
# Copy email templates into the container
COPY ./templates /home/mailer/templates
# Install lightweight file server for email templates
USER root
RUN apk add darkhttpd
USER supabase
# Run file server and auth server in parallel
ENTRYPOINT darkhttpd /home/mailer/templates --port 8080 --addr 127.0.0.1 & authWhat's the top thing that would make your life with self-hosted Supabase easier? The biggest pain point that still remains, based on my current experience, is that new migrations added to the Postgres image don't run in a continuously deployed setting. The running Postgres container has a volume mounted, with a data directory and an entire database, pages of data etc. When I update the Postgres image version in my GitHub repo, a new deployment starts. A container is spun up, the previous one is shut down, the new one is placed onto the infra node with the volume mounted, and it starts. I see the following message logged: The official Postgres Docker image is designed to only run the scripts in the entrypoint folder one time if there's no data directory. Because that's how the Supabase Postgres image manages those migrations, this presents a great challenge to keeping self-hosted Postgres services up-to-date. It doesn't have to be that way though, and Supabase could choose to manage those migrations in another way. They do all need to be idempotent though obviously. I still have no solution at this time, it would take a thoughtful and considerable effort to change how this is implemented in the Supabase Postgres image. If you could wave a magic wand and improve one thing, what would it be? Convince Supabase to use a monorepo strategy in their self-hosting example. I've written a few comments about why this is great for modern cloud CI/CD (watch paths, each service builds from a sub-directory). An example that might serve as inspiration: https://github.com/BenIsenstein/pgonrails |
Beta Was this translation helpful? Give feedback.
-
This is truly essential in a business environment. This is one of the reasons why I haven't used Supabase in several apps I've developed. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
In my framework for self hosting, PG On Rails, the email templates update instantly in local dev. No need to restart containers 😉> > - Add minimal tweaks at the container level, where useful, without disrupting the fundamental stack. (hosting email templates within the Auth container itself via httpd, tweaking Kong routing, etc)
|
Beta Was this translation helpful? Give feedback.
-
|
@aantti I want to recommend that you can think of everything that supabase releases as "building blocks" toward self-hosted successful outcome. Then, you can create an image release and docs etc around a profile that works for self-hosting while finding a way to resolve with the release cycles of the supabase product components. Then you can manage a stability and release cycle that focuses on what the self-hosting community is asking for. |
Beta Was this translation helpful? Give feedback.
-
|
...for instance, if the existing dockerfiles (which are geared toward use in https://github.com/supabase/cli) are not a good fit for self-hosting, then a set could be created somewhere that inherits what works from releases, and makes the changes needed based on consensus from self hosting. It can become a branch in the tree of supported release, and we already are set up to support that. |
Beta Was this translation helpful? Give feedback.
-
|
As promised on X here is my feedback how I use the supabase. Tell us about your setup: What does your deployment look like (infrastructure, deployment method)? We use Hetzner VPS with Coolify and the supabase template. What kind of project or team are you running it for? I work for different projects and companies. We use it as backend for financial asset overview, here we host a supabase for testing ourself. Prod is managed by supabase. Engineering Company , here we use supabase as backend for realtime car tracking. And here we host it self also in prod. How long have you been self-hosting? How would you describe yourself? Are you a solo indie dev, a small agency, a bigger company? Is application infrastructure your main focus, or are you a full-stack developer in need of an "open source Firebase"? What made you choose self-hosted? What parts of the experience have been smooth or even straightforward? Any unexpected wins? What's the top thing that would make your life with self-hosted Supabase easier? If you could wave a magic wand and improve one thing, what would it be? Something different than the basic auth for the dashboard (user with roles like in the hosted version) Happy to hear that things starts rolling :) |
Beta Was this translation helpful? Give feedback.
-
|
@aantti we have high hopes :-) !
Kubernetes, started with the now-abandoned Bitnami chart, added the missing bits and evolved it.
Open source and (recently) proprietary education products
3 years
Currently "solo indie dev", moving to a startup, postgres fanatic
Both! I do from server provisioning up to (very poor) CSS.
My previous main project was intended to be an open/research platform for low-budget/free/government education providers, so freedom/independence and cost were paramount... Also, need to host (amongst others) in China and other "air gapped" environments.
None that really stand out unfortunately.
Up-to-date, relatively comprehensive ops and release documentation. "We changed X so you need to Y, Breaking change ABC, etc."
Coherent engineering leadership across all the component apps. There are obviously some very talented coders amongst the bunch but it very much feels like a bunch of stuff hacked together with no cohesion. If you look at the git history of the There are marketing/design people that seem to put a nice polish on the outside of everything but the same care is not afforded for the individual projects at the technical/docs level. Supabase has always tried to portray the company as a "good open source citizen" but I haven't seen any of that really. The code is available but there is basically no community around the components, nor any desire to foster one... And again the docs/community around the "black-box" SAAS product is a COMPLETELY different thing. Firebase (Photoshop, MSOffice, ...) has a great community for it too - it's just not an open source community. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed feedback, @AntonOfTheWoods. Building a platform like Supabase and the organization around it involves a lot of complexity and tradeoffs. Self-hosted deserves better tooling and documentation - no argument there, and that's what I'm focused on improving. That said, there aren't many similar open-source platform stacks for the data layer that come with a truly permissive license. We're working to do better on all fronts, while maintaining that openness. I'm keeping your notes - there's a lot of work ahead regarding our community efforts (which includes all-things-self-hosted). |
Beta Was this translation helpful? Give feedback.
-
|
Hey, and welcome to the team! It's fantastic to see a dedicated focus on improving the self-hosting experience. Thanks for opening up this discussion. Here's a rundown of our experience in the wild. Our Setup
About UsWe're a small company of two. My role is a full-stack developer. We absolutely fit the profile of a team needing an "open-source Firebase" that gives us more control and flexibility. What's Actually Working Well
The Top Thing That Would Make Life EasierIf I could wave a magic wand, my top request would be to radically improve the update/upgrade process and its related communication. This is where we've hit our biggest hurdles:
Other SuggestionsA feature we'd love to see more guidance or tooling for is high-availability and replication. I know Postgres replication is a well-trodden path, but a holistic guide or solution that also covers Storage replication would be incredibly valuable for scaling and resilience. Thanks again for reaching out to the community. Despite the maintenance challenges, self-hosting Supabase has been a huge win for us. Looking forward to seeing how the experience evolves |
Beta Was this translation helpful? Give feedback.
-
|
Whoa, thanks so much for a very thorough feedback here! Let me digest :) Re changelogs - very true, and also I've just started some experimental lightweight process for CHANGELOG and image version updates. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @aantti, Thanks for starting this thread. As a new user trying to self-host on a UGREEN NAS, I just went through a very painful, full-day debugging session. I wanted to share my findings and a complete guide for what I had to do to get it working. P.S. I am very new to this, so my solution might not be ideal, but it does work and directly addresses several problems (Secrets, Permissions, DB roles) all at once. Here is my guide, which I hope can help you and the team improve the official docs. Title: [GUIDE] The Fix for 'permission denied for schema public' on Self-Hosted (UGREEN NAS)I finally found the solution. It's a three-part problem:
Here are the complete steps I used to deploy, and the final fix for anyone else who gets stuck. Part 1: Get Code and Create Project DirectoryThis is the standard first step. # Get the code (if you don't already have it)
git clone --depth 1 https://github.com/supabase/supabase
# Make your new supabase project directory
mkdir supabase-project
# Copy the compose files over to a project
cp -rf supabase/docker/* supabase-project
# Copy the fake env vars
cp supabase/docker/.env.example supabase-project/.env
# Switch to your project directory
cd supabase-projectPart 2: Prepare Your
|
Beta Was this translation helpful? Give feedback.
-
|
Ouch, a lot of work here! Will keep this as a bookmark for a guide related to UGREEN NAS for sure. Will also review as part of my ongoing effort to make the self-hosted docs more detailed. Curious, why do people use a "NAS" to self-host Supabase? :) Is that because there's some nice compute power? Because of storage capacity directly available? What's your actual "use case" if I may? |
Beta Was this translation helpful? Give feedback.
-
I jump right in because i do also host on my (Synology) NAS, or at least that was my dream until i managed it today.
In the end, with todays version of supabase, hosting on my NAS system required only a few changes in the .env (thanks to the auto generate script to skip the tedious secrets) and the docker-compose. |
Beta Was this translation helpful? Give feedback.
-
|
I really like Supabase, but my experiences with self-hosted have been nothing short of painful. Our infrastructure is on GCP. Our two attempted deployments crashed and burned. Both deployments utilized Google’s Cloud SQL and their global load balancer. One attempt was with Cloud Run, the other with a managed instance group. I felt like I got close with both, but ultimately bailed because the time investment was too much If I could pick an ideal setup, it would be Supabase managed (functions, auth, advisors, storage, etc) with my own Cloud SQL. This would allow us to do processing on GCP with our data for increased privacy, lower latency, and reduced egress fees. Having the ability to right-size my Superbase functions and backend database separately would be immensely beneficial. My app’s database is memory intensive — separate right-sizing gives me the ability to tune my system where it’s needed and prevents shared resourcing. Google Cloud SQL lets to take advantage of CUDs that makes the pricing more palatable. I’ll probably wrestle with self-hosting again at some point to make it work. I really don’t want to move everything. Help! In all seriousness, it’s great to see that you care so much about self-hosted as an option. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, this is fair. Running Supabase on a managed Postgres is somewhat non-trivial at the moment (although achievable). It's got some immediate limitations, though. This is definitely a valuable signal you're sending here. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, as other mentioned, big thank you to see a dedicated focus on improving the self-hosting experience and for all your great work so far! About UsWe work in life sciences/research and health care. Our products range from management dashboards for health professionals and patient portals to workflow and tooling for researchers. Our SetupWe host everything self hosted on AWS through cloud formation IaC, mostly for compliance reasons but also for reduced legal complexity and talent competence. Our Criteriaself hosted, full code control with ability and competence to contribute, no outbound telemetry to external, white label-able and IP transferrable licenses of our products, all Infrastructure as Code with no console UI clicking, Modern tech stack without lock in, least amount of code to maintain ourselves, low complexity, MVP fast -> scale ready later What's Actually Working WellAll together we use supabase auth, client and server side sdks, storage (through s3), vector, studio, rest, very happily and successfully. Most happy i am about the amount of custom endpoints and backend/types code i do NOT have to write and maintain anymore by heavily making use of one Postgres DB as the single source of truth for data structure (-> types), permissions, auth and many RPC functions (love them). As much as possible is maintained through the declarative db schemas and that makes it feel a lot like the "single file backend" which is working pretty well for me for AI coding and context management. Very important is also to use this setup from across languages, we have different applications and backends using typescript or python and the supabase sdks make it very easy here to port code and patterns The Top Thing That Would Make Life EasierThe one thing i wished to have was an easier path to self host supabase with AWS RDS as the postgres DB, that was a real pain to setup and took me 2 weeks of custom cloud formation and shell scripting to alter the supabase/postgres migration files and align extensions, role grants and migration order to fit the RDS constraints (which suck, but for a reason i guess) The community AWS self hosting is to complex/costly/resource intensive for smaller scale products or MVPs, we wanted to "just" self host on an EC2 and "just" use RDS instead of a postgres DB inside of the EC2 and to be able to connect to our other AWS hosted projects/IAM setup etc. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, thanks a lot for the kind words - and for being so specific about your environment and the role. Super nice that self-hosted Supabase option (although, modified :) has been that much useful. Regarding "AWS RDS as the postgres DB, that was a real pain to setup" - that's really true, unfortunately. I've done a similar experiment a few months ago, and it's a very tedious process indeed, which then comes with certain limitations (here, if you'd like to ever compare notes). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the amazing product! Setup:
About us:
Working well for us:
Nice to haves:
|
Beta Was this translation helpful? Give feedback.
-
|
Appreciate the feedback! This is noice - "self-hosting for about 2 years now"!! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @aantti for asking!
Supabase running on several geographically-dispersed bare metal servers running NixOS, deployed using docker-compose
B2C product supporting both web and mobile apps
2 years
Solo indie
Full stack
Avoiding vendor lock-in at the data center level. Desire to understand what's going on beneath the hood
My app was postgres-based already, and migrating it into Supabase was easy peasy
Stripe integration, while not totally seamless, was easier than I expected. I ended up writing some MVs and cron jobs to sync them to fix some issues and then it was great. I think Supabase recently released something that makes this work better but I'm good with my solution :-)
Align versions here https://raw.githubusercontent.com/supabase/supabase/master/docker/docker-compose.yml with whatever you have running in hosted Supabase to keep things consistent
I'd love to be able to do active-active replication among my supabase servers, particularly the Some kind of built-in scheduled backup facility in Studio (maybe it's there and I missed it!) with ability to restore to point in time etc Let me set the OpenAI base URL using environment variable when running supabase using Docker so I can use other OpenAI-compatible LLMs including locally hosted LLMs. (ref. https://github.com/orgs/supabase/discussions/33205) (Sorry that was three LOL) |
Beta Was this translation helpful? Give feedback.
-
|
This is great, exactly what I've been trying to understand & collect as various opinions and feedback. Specific feature suggestions are much appreciated. The last two in particular have been definitely adding more barriers than necessary. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, congrats to the team, Supabase is a great product and amazing evolution. For the same reasons shared by others, compliance and full data control and sovereignty is the key reason for self hosting. We are in the middle of the deployment on AWS, and we noticed that the github Cloudformation is outdated, with older versions of postgres and too broad permissions/security issues, so we are now trying to rewrite/build our own version, which goes against my will, and is a hassle I would have preferred not to take on. So I was happy to read you guys are open to soften that pain. The ideal version for me would be a fully aligned Cloudformation template with one click deploy resulting in the same stack as your online version and that is easy to update aligned with a transparent change log. Simply provide a domain name, and the rest is magic coded and secured by your team. We would be happy to pay a license for this like we do in the cloud on top of the infra cost we carry. Please let me know asap if we can expect some important improvements soon, so we can hopefully avoid our own rewrite attempts. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting :) This looks more like a paid "onprem" option, though? |
Beta Was this translation helpful? Give feedback.
-
|
What kind of project or team are you running it for? How long have you been self-hosting? How would you describe yourself? What made you choose self-hosted? What's the top thing that would make your life with self-hosted Supabase easier? At the moment, it doesn’t feel like Supabase is actively promoting or supporting self-hosting: some templates are outdated, community examples are sparse, and GitHub issues often show people struggling to get production-grade setups running. If you could wave a magic wand and improve one thing, what would it be? Ideally, self-hosting would support all core features we rely on — including Edge Functions, automated database backups, replication, and other reliability features that are currently much easier to use in the managed service. |
Beta Was this translation helpful? Give feedback.
-
|
Echoes the previous comment somewhat :) I can't say much about possible paid options for advanced self-hosted configurations like the above, but your comments regarding K8s are definitely very useful to me. |
Beta Was this translation helpful? Give feedback.
-
my own product
appr. 2 years
full stack developer
use supabase as solo developer
full stack developer in need of an "open source Firebase" but based on a SQL DB
everything like realtime usage, auth service, rest api, storage. Just the setup of self-hosted supabase took alot of effort with adjusted DB images
cost efficiency, gaining practice in running a self managed kubernetes cluster, and the ability to create and delete full instances for automated test runs
Supabase as backend with devspace and nuxtJS make app development very smooth and I experience less bugs as with other tech stacks. the automatically generated typescript types and the generated rest API create a very solid base. In-cloud E2E testing works also great with a supabase instance as testing environment with seeding that gets freshly created for every test run
With cloudnativePG as Kubernetes Postgres manager I can even reach high availability and DB backups quite easily
A kubernetes helm chart that uses cloudnativePG as Postgres DB
To have this helm chart ready to run |
Beta Was this translation helpful? Give feedback.
-
|
Looks like a very nice example of starting smaller then making it more advanced :) Glad to hear the product stack works overall quite well for you as a solo fullstack developer! The nice-to-haves above make sense. |
Beta Was this translation helpful? Give feedback.
-
|
As an interim note - I'm reading all the comments here and I'm grateful that everyone has taken the time to provide detailed, specific feedback. This means a lot. I can’t promise immediate improvements on everything, but this input is extremely insightful and very valuable as open feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for considering us! I work in a small tech product startup as a software eng, and I also manage the whole infrastracture. Everything is on AWS, we use EKS + S3 + RDS postgres. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone and thanks for asking for our feedback!
I am a software engineer / project manager working both as an employee in a
small SAP consultancy company and as freelance.
I have been using Supabase for about a year now (with both PRO and free
plans) and decided to introduce it into my company for a big software
product we developed for a customer of the aerospace industry (MRO). We had
strict requirements that led us to choose a self-hosted (Docker) setup of
the platform.
First setup was very easy following the documentation but I didn't realize
that self-hosted was missing useful dashboard configuration like
authentication, etc; so it was a bit tricky.
For me/us Supabase is really a great choice since there's no API
development to do and the system provides such useful and interesting
features like realtime, RLS and many others.
If the self-hosting whole setup experience was as similar as possible to
cloud hosting it would be perfect, that's the only thing I would improve.
Thanks and keep doing this excellent work!
Alessandro.
Il giorno gio 13 nov 2025 alle ore 17:00 Eduardo Silvi <
***@***.***> ha scritto:
… Thanks for considering us! I work in a small tech product startup as a
software eng, and I also manage the whole infrastracture. Everything is on
AWS, we use EKS + S3 + RDS postgres.
I've tried to self host ~8 month ago, it was only a test (we're now in
production with cloud hosted supabase). I was very happy to found a
community driven helm chart, but my problem was that the chart was forcing
me to have a postgres cluster deployed in my kubernetes cluster, while my
need was to use the RDS instance.
—
Reply to this email directly, view it on GitHub
<#39820 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKR4SIRQNGE56ACUM64RLS334STI7AVCNFSM6AAAAACKBIQ4GCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJWGA2DQMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
--
__________________________
Alessandro Recano
|
Beta Was this translation helpful? Give feedback.
-
|
That's encouraging :) Thanks for the story and hopefully we'll be able to gradually make it more convenient. |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone, I've been reading through the whole discussion and decided to get into it as well, since I'm having some trouble with my self-hosting supabase instance as well. So, let's go! Tell us about your setup: How would you describe yourself? What's actually working well for you? What's the top thing that would make your life with self-hosted Supabase easier? Try refreshing your browser, but if the issue persists for more than a few minutes, please reach out to us via support. So far, I've found no solution for those errors, other than running my instance without any kind of integrations available, so I will keep on searching how to do it. |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate your story here! Not great re: analytics not starting and the other issue, however, it would probably be counter-productive to substitute this discussion for proper issue resolution. Regarding analytics - how much memory on your server instance? My recent tests show at least 4GB memory is required to start all containers, especially analytics 🙈 The other problem you've mentioned - could you possibly provide a full description in a separate issue, where do you see that, how to try recreate, have you configured custom db name/user, etc. 🖖 |
Beta Was this translation helpful? Give feedback.
-
Of course! I currently have a 4GB RAM instance running. I've just opened the logs for the analytics container and I've got this error in repeat: "Runtime terminating during boot ({function_clause,[{'Elixir.Logflare.Utils',ip_version,[nil],[{file,"lib/logflare/utils.ex"},{line,243}]},{elixir_eval,'FILE',1,[{file,"/opt/app/rel/logflare/releases/1.26.4/runtime.exs"},{line,276}]},{elixir,eval_external_handler,3,[{file,"src/elixir.erl"},{line,386}]},{erl_eval,do_apply,7,[{file,"erl_eval.erl"},{line,919}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,479}]},{erl_eval,expr_list,7,[{file,"erl_eval.erl"},{line,1207}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,446}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,436}]}]}) Crash dump is being written to: erl_crash.dump...done |
Beta Was this translation helpful? Give feedback.
-
|
Not quite sure what's going on. Can you open an issue? Please include all related details about your OS, virtualization, etc. (e.g., |
Beta Was this translation helpful? Give feedback.
-
|
Upd: Resolved via #40719 |
Beta Was this translation helpful? Give feedback.
-
|
I’m currently using Supabase in a smaller personal project and considering self-hosting in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Glad it's helpful :) We'll be improving wrt self-hosted. |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
We're hosting Supabase on a mid-size VPS server. We took over a half-finished flutter app using Google Firebase as the backend. When looking into that and the features to be implemented there and bugs to be fixed, we were shocked by the very bad dev experience using Firebase. Therefore, we looked into Supabase and rewrote the app to use it instead. In the end, it was quite some work, but it provides a much better dev as well as user experience.
We are a small company with a few fullstack developers, also doing our own infrastructure.
We chose to self-host supabase because of the strict data privacy requirements of our customers (handling health data). We really love having a proper postgres database running, which ensures the schema and allows for thorough and granular authentication and permission management.
In our experience only the logs for the API Gateway, Postgres and Auth are working while PostgREST, Edge Functions and Cron do always show "No results found". Also for the Edge Function DX we would love to see feature parity with the hosted version. Allowing for CRUD operations via the UI and the CLI. In general it would be great to be able to use the CLI with self-hosted instances.
That said, Supabase is still such a great piece of software, thanks for all the work you and the team put into it! |
Beta Was this translation helpful? Give feedback.
-
|
Also, with the latest self-hosted Docker Compose configuration logs work :) |
Beta Was this translation helpful? Give feedback.
-
|
That sounds great, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Profile is something else, I think. To point CLI to self-hosted Supabase database you could use |
Beta Was this translation helpful? Give feedback.
-
|
But that only works for the db part, right? Ideally we'd want to use the CLI with selfhosted just like with the hosted version, e.g. logging in, for edge functions, etc... |
Beta Was this translation helpful? Give feedback.
-
|
That's for db only, correct. |
Beta Was this translation helpful? Give feedback.
-
|
Another interim update:
|
Beta Was this translation helpful? Give feedback.
-
I would say a little bit of everything (Cloud, Self Hosted, Kubernetes) but most have already been migrated to other technologies.
Well, a full-stack developer with many freelance projects
Most of the features work excellently. I'd say the most useful thing for me is having such a complete system available to quickly fix problems at any time.
Update:
This also needs to be fixed |
Beta Was this translation helpful? Give feedback.
-
Thanks! It's been a ton of work that the team has put in it over the years. Glad it's mostly working for you :) Much appreciated.
Stern, but fair ;) It needs a revamp and more content. The extra items you've mentioned are very useful - adding to my Linear 🙈
There's an ongoing work that the team has been doing on both, hoping to add more soon. Thanks, much, for the detailed feedback above! |
Beta Was this translation helpful? Give feedback.
-
|
Adding my perspective as someone who's helped teams evaluate and deploy Supabase:
|
Beta Was this translation helpful? Give feedback.
-
|
This is something I forgot to mention:
It is undoubtedly vital for any environment that calls itself "professional" or "business." For a long time, I was looking for ways to update databases, and it was quite frustrating and tedious. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, @Rubenburdin ! |
Beta Was this translation helpful? Give feedback.
-
|
I am currently checking whether Supabase is a solution or not for my company. Reading your statements I see two problems. First, is there no way to connect a non-dockerized Postgres database? I didn't test that out myself right now but i thought there were just a few config entries that have to be changed. Second, the updates of Supabase itself. Can you share some experience with it? I would like to know if there is a way to be certain that an update was successful and what you do if you notice that it wasn't. Is the only fix for that, to roll back to a previous backup and try again? |
Beta Was this translation helpful? Give feedback.
-
|
@YukiAttano You can definitely use Supabase as long as it's not an overly complex project or one that will grow over time. You'll encounter the same issues mentioned in this discussion, but if there aren't any significant changes after version 1, then you can rest assured it will work very well. On the other hand, yes, you can use another database; you just need to modify the necessary connection files. I tested this about a year ago, and it worked fine. You should try it now. Updating Supabase is easy; you just need to stop the container, update the images, and restart it. But if you're talking about updating the database schemas and structure, then you'll run into a lot of problems. |
Beta Was this translation helpful? Give feedback.
-
We are only using the edge-runtime, which we self-host on Kubernetes. We run it on memory-optimized nodes with 4 CPUs and 32 GB of RAM. We deploy a container to ECR, and the container includes a functions/ directory containing about 40 different functions. We’ve been self-hosting this setup in production for about a year. We have an in-house fork and we included rust code for things like a prometheus service that also has some functionality exposed in the ts/js runtime.
We’re a medium-sized startup with 50+ employees.
The main reason we started using this was that many of our functions require complete isolation from one another (Deno works really well for this). And within the edge-runtime these are supported which has been nice. From there, we just kept adding more functions, and everything has continued to work well.
|
Beta Was this translation helpful? Give feedback.
-
|
@kallebysantos fyi :) |
Beta Was this translation helpful? Give feedback.
-
|
Tell us about your setup: How would you describe yourself? What's actually working well for you? What's the top thing that would make your life with self-hosted Supabase easier? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed feedback! This is really helpful.
Can you elaborate on this one? Did you mean lack of certain configuration UI components (e.g. for Auth), or something else? |
Beta Was this translation helpful? Give feedback.
-
|
A couple of things really:
To put this in perspective, Appwrite self-hosted offers the auth capability with third parties, and traefik is easily configured via the dashboard despite it being traefik driven. In reality, I carve out traefik as it acts as my reverse proxy across multiple services anyway, but as a first timer to Supabase self-hosted having configurable data rate limits would be good for a hobbyist - though I realise I'm perhaps not the target audience! Appwrite self-hosted also supports multi-org and project, though this is less of a concern to me as I believe in distinct project isolation myself, but it's always worth knowing what is happening elsewhere. When/if Appwrite add support for Postgres they would become a more attractive proposition as I'm not a big fan of their current TablesDB API on MariaDB - I find Supabase/Postgres far easier to understand and interact with given my own background. Again, this is all just my own opinion as a hobbyist. |
Beta Was this translation helpful? Give feedback.
-
|
Really appreciate these details :) |
Beta Was this translation helpful? Give feedback.
-
|
From an Automation & CRM standpoint, self-hosting offers strong advantages when you need full control over integrations, data flow, and automation logic. For teams that manage sensitive customer data or complex workflows, having the infrastructure in-house allows direct access to logs, APIs, and database schemas, which is critical for maintaining accountability and auditability. A few observations from practical deployments: Infrastructure flexibility matters: Running on containerized environments (Docker/Kubernetes) with orchestrated backups and scaling policies works reliably for medium-to-large CRM systems. It simplifies updates, restores, and disaster recovery, which is often a pain point with cloud-hosted automation platforms. Automation pipelines benefit from local performance: When triggers and workflows rely on near-real-time processing (e.g., lead assignment, task creation, or event-driven notifications), self-hosting reduces latency and avoids API throttling from third-party services. Unexpected wins: Teams often discover opportunities to integrate custom modules or legacy systems that would be impossible or slow to implement in cloud-only platforms. This is especially valuable in CRM where bespoke processes often exist. Challenges: Maintenance overhead and monitoring are the main bottlenecks. Scheduled updates, database migrations, and high-availability setups require dedicated attention; without automation and monitoring, tasks like workflow failures or delayed triggers can easily go unnoticed. If there’s one thing that could make self-hosted setups smoother for CRM and automation-heavy teams, it’s a unified dashboard for monitoring workflow execution, automation health, and integration logs. Having that visibility reduces the operational burden and ensures automation pipelines remain reliable. At Leadsflex, we’ve found that self-hosting pays off when automation reliability and data control are critical, but it’s important to build strong operational practices alongside the deployment. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, But the real fun began, when I decided to try this on self hosted vps, and that doesn't seem to be convenient at all, Supabase UI doesn't work, you have to do everything from a terminal. I may not be your targeted audience, but as the Supabase Cloud is made accessible to non-coders like us through AI, this brings in a little expectations for the self-hosted part too. I believe a tool should be so easy, especially the UI, that you dont need to learn it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, useful!
Would love to know more :) Do you mean you had issues using Studio overall? Some specific parts of Studio? Expectations from self-hosted Studio functionality not matching your Supabase platform experience? Something else? :) |
Beta Was this translation helpful? Give feedback.
-
|
A quick interim update on the state of self-hosted Supabase :) First of all, the main goal so far has been to bring self-hosted configuration up to speed, make it more predictable as the "upstream" repo, collect feedback and ideas, identify & validate the gaps, and plan for enhancements. What's happened lately:
Next steps would be along the lines of working on major component updates (Postgres 17, Envoy as API gateway, further enhancements for Studio, support for new API keys, more work on the Helm chart, etc.) Appreciate everyone's feedback here, and thanks, much, for being a Supabase user :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I'll leave this recap here; we're doing pretty well! Thanks, @aantti The most important points so far: ✅ MCP Server ✅ Token Generator (Web Docs) ✅ SQL Snippets 🔼 Documentation (Improving... Improving... 👌I definitely believe it is necessary to document processes like the ones I mentioned above.) 🧐 Analytics and Logs (I think it's much more stable lately; however, many have reported instability. This will need to be verified, as those who reported it should check with the latest versions. For me it would be a 🔼) 🫤 DB Migration (Schema Updates) 🫤 Backups 🫤 DENO Update 🫤 Postgres Update 🫤 Replications (I'm really not sure about this... From my perspective, I think [I'm sure] that it's better to use the Cloud service) 🤔 ❓ Other Fixes (Please mention them in the comments) Thanks again to @aantti, the supabase team, and all the contributors! Lets Goooo! |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thank you for taking feedback. This is all probably going to sound quite spirited, so I want to preface it all by stating how much I enjoy of what I can get working out of Supabase. I truly think you have something special here, which is why it hurts so much when things don't quite work out. I'm a hobbyist with ambitions to learn and use these things for fun, not profit. I've been doing self-hosting in general for probably a decade now in some form or other. Unfortunately, I've found the self-hosting experience for Supabase to be unusually frustrating. The rest of my system uses a Traefik reverse-proxy as a unified entry-point / router to direct direct incoming requests to different applications most often based on the Host in the request. I rarely if ever run into issues slotting in most anything behind this system, but Supabase unfortunately happens to've been a particularly prickly outlier for me.
To sum it up things up:
|
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone!
We've been investing more in self-hosting lately - including bringing on a new team member (me!) dedicated to improving the experience.
We know there are challenges (we see the issues you've filed!), and we've been working through them. But I'd also love to hear about what's working 🙂
Tell us about your setup:
How would you describe yourself?
What's actually working well for you?
What's the top thing that would make your life with self-hosted Supabase easier?
I’m trying to get a clearer picture of who's running Supabase self-hosted and how it’s going in the wild. Since we prefer not to have telemetry in our open-source projects, your input here directly helps shape our focus.
Quick note: I can't promise immediate fixes for everything - think of this more as helping us understand the audience. That said, I'm definitely interested in hearing about feature gaps, bugs, and requests too.
Thanks for sharing! 🙏
Beta Was this translation helpful? Give feedback.
All reactions