giusdp
I was wondering about migrating my liveview project to supabase from ecto/postgres. I know there are already some discussions about using supabase in this forum but they are mostly about praising supabase as a good fit for any solo dev project (which is my case), and none about approaches to use it in elixir.
Unfortunately there are no well maintained elixir libraries out there (only found supabase-elixir from 2 years ago) but then I saw that supabase also offers a graphql api on top of the database, so maybe I can just use any graphql client library. Searching for one I found Neuron, so I could use that to talk with supabase from liveview.
Is anyone here using a similar approach? Or what other approaches/stacks are you using with supabase?
I understand that moving the DB/backend to supabase means that liveview is being used only for the frontend but I don’t really want to use other languages or frameworks 
I’d prefer to keep using elixir.
I’m just curious about your thoughts and solutions about this!
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
landm
Supabase is just postgresql under the hood, you can connect directly to it. If you provide the connection params to your Phoenix app, it will work the same as if it were a local db with no extra work. Ecto, etc, all just work, except operating on a remote db.
In your case, I’m not sure what the benefit of supabase would be as you’re using liveview for frontend. I have one app that is run this way, but it is a primarily backend application which has frontends written in different languages (React/TS, etc) connecting to it. Supabase simplifies the experience for varied frontends.
giusdp
I was attracted by the extra features of supabase so I wanted to try it (db editor, auth with social logins, serverless functions etc). I don’t know why I defaulted to “I can’t use ecto with it” though! So thanks. I will definitely keep using ecto.
I also would love to expand my app in the future with multiple frontends so I think starting out with a baas system would be the best… although I’m looking at liveview native for the future.
landm
Yeah, the management features of supabase are great, db config and editor, etc. Also worth noting that Supabase uses Gotrue for social logins, which you can easily do the same in your phoenix app if that’s a determining factor. Anyway, if you plan to have non-phoenix frontends, I think going the supabase route is a good choice.