# Supabase — Set up Supabase for every Expo environment in one command

- Company: Supabase (supabase.com)
- Announced: 2026-11-10
- Category: developer-tool-release
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://supabase.com/blog/set-up-supabase-for-every-expo-environment-in-one-command
- Record: https://forck.live/items/34105-set-up-supabase-for-every-expo-environment-in-one-command
- Subject: Supabase

Expo built a Supabase integration into the EAS CLI so developers can create a Supabase project, install the SDK and write keys to every Expo environment with one command. The command, eas integrations:supabase:connect, replaces the old routine of creating a project in one dashboard, copying keys into another and checking that preview and production held the right values. Adding --environment preview gives Preview its own Supabase project with separate keys, leaving production data untouched, while Development can point at a local Supabase stack. Supabase Security and Performance Advisors run from the CLI and report findings such as a table with Row Level Security disabled or a foreign key without an index in the Expo build dashboard, next to the build logs for the change that introduced it. Every command runs without prompts and returns JSON, so an agent scaffolding an app can set up its backend in the same pass. Quilia, which builds a client app for personal injury law firms, uses a read-only Supabase MCP server and a development project to ship several fixes a day through Expo Update. The integration requires eas-cli 21.8.0 or newer and a project linked to Expo.

## Evidence

Verbatim from https://supabase.com/blog/set-up-supabase-for-every-expo-environment-in-one-command:

> Supabase is available as an integration in the EAS CLI. Run eas integrations:supabase:connect in an Expo project, and it creates a Supabase project, installs the SDK, and writes your keys to every Expo environment. The next build and the next update have a working backend, with no trip through the Supabase Dashboard.
> 
> Expo is the open source framework and cloud platform that 80% of React Native developers use to build, ship, and update their apps from one codebase. Supabase has been the database behind a large share of those apps for years. Expo's team built this integration so connecting the two is a step the CLI runs rather than a guide a developer follows.
> 
> Setup is one step #
> 
> Every new Expo app on Supabase used to start the same way. You created a project in one dashboard, found the keys, pasted them into the other, installed the SDK, and checked that preview and production ended up with the right values. The command does all of that in one pass, from authorizing your Supabase account to writing the keys into Production, Preview, and Development on Expo. The setup work between starting a project and writing the first screen is gone.

---

Record: https://forck.live/items/34105-set-up-supabase-for-every-expo-environment-in-one-command
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
