> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/ai-builder/integrated-backend.md).

# Integrated Backend

The AI Builder integrated backend — database, user sign-in, file storage, a server API for secret keys, app email, the Data view, and test versus live data.

Every AI Builder project comes with a backend you don't have to set up: a **database**, **user accounts**, **file storage**, and a **server API** for server-side logic. Ask for a feature that needs any of these — "let visitors book a table", "add a members area" — and the AI creates the collections, rules, and endpoints for you. No third-party database account is needed.

## What's included

| Capability        | What it covers                                                                                                                            |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Database**      | Collections with typed fields, relations, and access rules; realtime updates                                                              |
| **User accounts** | Email and password sign-up and login, one-time codes, multi-factor authentication, password reset and email verification                  |
| **Social login**  | Google, Apple, Microsoft, GitHub, Facebook, Discord and about 30 other OAuth providers, using your own app credentials from each provider |
| **File storage**  | Uploads such as avatars, documents, and images, stored with the record they belong to                                                     |
| **Server API**    | A Node.js API for third-party API calls, webhooks, scheduled jobs, and anything that needs a secret key                                   |
| **Email**         | Contact-form notifications, order and booking confirmations, password reset and verification emails                                       |

## Data view

Open **Data** from the editor menu to see what's in your database — records, users, and form submissions — in an admin dashboard. Switch between:

* **Test data** — what you created while trying the [preview](/ai-builder/preview-and-versions.md).
* **Live data** — real submissions and sign-ups from your published site.

You can browse and edit records here without using AI credits.

## Test and live data

Your preview and your published site have separate databases, so testing never touches real customer data.

* The **first** publish copies test data to the live site as starting content — handy for product lists, menus, or blog posts you set up while building.
* **Later** publishes add only records that don't yet exist on the live site; live records are never overwritten.

Test data is for experimenting and isn't backed up. Live data is included in daily [backups](/ai-builder/publishing-and-domains.md#backups).

## API keys and secrets

When a feature needs a third-party service — a payment provider, SMS, a CRM — paste the API key into chat. The AI stores it on the server side of your project and calls the service from the server API, so the key isn't exposed in the browser.

> **Note:** Keys you share are stored with your project's server code. Use keys scoped to what the project needs, and rotate them if you share the project.

## Email from your app

Your app can send email without any setup:

* **Form notifications** to you when someone submits a contact or booking form.
* **Confirmations** to the person who submitted.
* **Account emails** — verification, password reset, and one-time codes.

Emails are sent from a Hostinger sending address on your behalf. You can set the sender display name, CC and BCC recipients, and HTML content. Replies go to the sending address, so include the visitor's email in the message body if you want to reply to them.

For newsletters and marketing email, connect [Hostinger Reach](/ai-builder/integrations.md#hostinger-reach).

## Older projects

Some projects created before the integrated backend use **Supabase** connected to the user's own Supabase account. They keep working, and the Supabase option still appears for them; new projects use the integrated backend.

## Related pages

* [Integrated AI](/ai-builder/integrated-ai.md) — AI features that run on your backend
* [Ecommerce](/ai-builder/ecommerce.md) — stores, products, and payments
* [Integrations](/ai-builder/integrations.md) — Reach, analytics, and third-party APIs

***

*Last updated: October 20, 2026*