> For the complete documentation index, see [llms.txt](https://help.imagine.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.imagine.art/imagine-computer/build/build-connectors/supabase.md).

# Supabase

#### **What is Supabase in Build**

Supabase turns a front end you generate in Build into a fully working app. Without it, your project looks and behaves like the real thing, but nothing is actually saved. Connecting Supabase adds a real database, real logins, and real storage behind the scenes, called Cloud inside Build.

#### **How to Connect Supabase**

In the composer, click the plus icon, then Connectors, then Supabase, and click Connect. You can also find Cloud represented by the purple cloud icon in the preview toolbar once your project is open.

<figure><img src="/files/elBTm6f8kyiqZr1fQyHu" alt=""><figcaption></figcaption></figure>

#### **What It Unlocks**

Once connected, your app can save real data, remember signed in users, and store files, rather than just simulating the experience. This is what turns something like a storefront or a signup form from a convincing demo into a real, working product.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.imagine.art/imagine-computer/build/build-connectors/supabase.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
