# deploy supabase

**URL:** <https://community.fly.io/t/deploy-supabase/9423>\
**Category:** Build debugging\
**Created:** [December 16, 2022, 11:53am UTC](https://community.fly.io/t/deploy-supabase/9423 "2022-12-16T11:53:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![brunowilliang](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/brunowilliang/32/10882_2.png) [@brunowilliang](https://community.fly.io/u/brunowilliang)\
**Post date:** [December 16, 2022, 11:53am UTC](https://community.fly.io/t/deploy-supabase/9423/1 "2022-12-16T11:53:50Z")

</div>

Is it possible to deploy here on [fly.io](http://fly.io)?

---

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [December 16, 2022, 2:42pm UTC](https://community.fly.io/t/deploy-supabase/9423/2 "2022-12-16T14:42:54Z")

</div>

Yes, but I don’t believe anyone’s written a guide yet. @ptn was dabbling a few weeks ago: [Self Hosting Supabase?](https://community.fly.io/t/self-hosting-supabase/9098)

---

<div class="post-metadata">

**Author:** ![Ty1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/ty1/32/14212_2.png) [@Ty1](https://community.fly.io/u/Ty1)\
**Post date:** [March 11, 2023, 6:58pm UTC](https://community.fly.io/t/deploy-supabase/9423/3 "2023-03-11T18:58:13Z")

</div>

Hi @kurt, Supabase on Fly leveraging fly’s high availability postgres cluster would be amazing, but I am really curious how you would accomplish this?

The Supabase architecture leverages [docker-compose](https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml) which [fly.io doesn’t support](https://community.fly.io/t/deploy-with-docker-compose-yaml/4566/2).

So one would need to rewrite this docker compose as a single docker file using a Procfile to run the various services on a single instance, or load the various services as separate processes, correct?

---

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [March 12, 2023, 3:38pm UTC](https://community.fly.io/t/deploy-supabase/9423/4 "2023-03-12T15:38:34Z")

</div>

I think you’d be better off just splitting the Docker Compose up into individual Fly apps. Each of those entries can be expressed as a Fly app. I believe their Postgres image runs just fine!

The problem with our Postgres clusters is that they don’t include all the extensions supabase relies on.

---

<div class="post-metadata">

**Author:** ![gedw99](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/gedw99/32/1287_2.png) [@gedw99](https://community.fly.io/u/gedw99)\
**Post date:** [March 28, 2023, 10:30am UTC](https://community.fly.io/t/deploy-supabase/9423/5 "2023-03-28T10:30:16Z")

</div>

agree that splitting up is the way to go.

regarding extensions, it just means running your own postresql.

Does fly use stolen: [GitHub - fly-apps/postgres-ha: Postgres + Stolon for HA clusters as Fly apps.](https://github.com/fly-apps/postgres-ha)

someone already has it here: [GitHub - rphlmr/supa-fly-stack: The Remix Stack for deploying to Fly with Supabase, authentication, testing, linting, formatting, etc.](https://github.com/rphlmr/supa-fly-stack)

---

<div class="post-metadata">

**Author:** ![noxford1](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/noxford1/32/17028_2.png) [@noxford1](https://community.fly.io/u/noxford1)\
**Post date:** [May 9, 2023, 1:10pm UTC](https://community.fly.io/t/deploy-supabase/9423/6 "2023-05-09T13:10:54Z")

</div>

FYI: I have a working tool to deploy Supabase to [Fly.io](http://Fly.io), it is work in progress, but it will get you really far.

[SupaFly](https://github.com/nicholasoxford/SupaFly)