> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/tutorials/guides/supabase.md).

# Supabase

Supabase is an open-source Postgres development platform that gives you a full backend — database, authentication, instant APIs, file storage, realtime subscriptions, and vector search — built on top of standard, unmodified Postgres. Rather than stitching together separate services for auth, storage, and data, Supabase exposes them all through one project, with every table automatically available as a REST and realtime API the moment you create it. Because it's just Postgres underneath, nothing about your data is proprietary or locked into a vendor-specific format: it's the same database and SQL you already know, with a managed layer of tooling on top.

As a client on the GLBNXT platform, you get Supabase delivered as one of the open-source components in your fully managed AI stack — with the infrastructure, security, compliance, and scaling handled for you, and your data kept on European infrastructure. That means your development team can go straight to building: standing up relational tables, enabling `pgvector` for RAG pipelines and semantic search, wiring up authentication, or connecting Supabase into an n8n workflow — without provisioning servers, managing upgrades, or configuring the surrounding orchestration yourself. GLBNXT handles the operational layer so Supabase functions as a ready-to-use building block within your broader AI solution, alongside the platform's other integrated tools.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.glbnxt.com/tutorials/guides/supabase.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
