In this guide, you’ll learn how to:
  • Connect multiple Rocket projects to the same Supabase database.
  • Build a new Rocket project using an existing Supabase project.
  • Understand when and why sharing a database is useful.

​
Before you begin

You’ll need:
  • A Supabase account with at least one active project.
  • Your Supabase account connected to Rocket.
  • Access permissions for the database you plan to use.

​
Why share a Supabase database

Connecting multiple Rocket projects to the same Supabase database is helpful when you want to:
  • Build different frontends (e.g., web and admin dashboard) that share the same data.
  • Maintain consistent authentication, storage, and API settings across projects.
  • Test new UI designs in a separate Rocket project without duplicating the backend.
You can also use an existing Supabase project to build in Rocket if you already have a working database and want to revamp its UI.

​
Best practices

Rocket connects to your whole Supabase project, but it only uses the parts you point it to. Being specific upfront keeps everything tidy and on track.
  • Tell Rocket your tables and fields right away
    In your first prompt, mention the tables and the pieces of data you care about.
    Examples:
    • Table: Users → Fields: Name, Email, Date joined
    • Table: Orders → Fields: Order ID, Status, Amount
  • Bring in your existing setup
    If your database is already running, describe it clearly in your first prompt.
    Rocket does not automatically know your schema unless you tell it.
  • Be clear about the pages you need
    For example:
    “I need a Users page that shows Name and Email, and an Orders page that shows Status and Amount.”
  • Keep projects focused
    Use one Rocket project for each goal, such as:
    • One for your customer-facing app
    • One for your internal admin dashboard
  • When Rocket generates a new script
    Only push it when you really want to update the database structure.     Push when: You add a new feature that needs a new table or field.
    Do not push when: Your existing schema already covers your needs.
  • Managing changes needed in both apps
    When two Rocket apps share the same Supabase project, any database change applies to both apps once the script is pushed.
    Each app may still need its own updates to display or use the new data. In many cases, you will need to prompt Rocket again.
    Example scenario:
    1. In App A, you prompt Rocket: “Add a field to save phone numbers in the user profile.”
    2. Supabase now has a new field called Phone number.
    3. App B also has access to this field through the shared project.
    4. To use it, prompt Rocket again in App B: “Update my Users page to also show Phone number.”
  • Try things safely first
    If you are experimenting with new ideas, connect them to a test project before applying them to your live database.
Quick reminder: The clearer you are about your tables and fields at the start, the smoother Rocket can build the right UI for you.

​
Use an existing Supabase project in Rocket

1

Start a new project in Rocket

From the Rocket dashboard, create a new project and choose your preferred starting point (blank or with templates).
Success check: You’re taken to the Rocket workspace for your new project.
2

Connect your existing Supabase project

  1. When prompted to connect a database, select Supabase.
  2. Log in to your Supabase account.
  3. From the list of projects, choose the Supabase project you want to link.
You can connect to a Supabase project used by another Rocket app or even one created entirely outside of Rocket.
Success check: Rocket confirms your Supabase project is connected.
3

Start building your UI in Rocket

Once connected, Rocket automatically uses the schema, tables, and auth settings from your linked Supabase project.
You can design pages, components, and workflows without changing the database.
Success check: Your Rocket app displays live data from your shared Supabase database.

​
Troubleshooting

​
1. I don’t see my Supabase project in Rocket

What you’ll see:
After signing in to Supabase, your project list is empty.
How to fix it:
  • Make sure you are signed into the correct Supabase account.

​
2. Changes in one Rocket project affect another

What you’ll see:
Updating data in one Rocket project instantly updates it in another.
How to fix it:
  • This is expected when projects share the same database.
  • If you want separate data, connect each Rocket project to its own Supabase project instead.

One database, multiple projects

Share data, streamline development, and revamp existing apps by connecting Rocket projects to the same Supabase database.
Need help?
Email us at support@rocket.new or join our Discord community.