Give Your AI Studio App a Database and User Logins

AI Studio Cloud gives an app you build in AI Studio its own database, customer sign-ins and file storage, with no separate service to connect or pay for on the side. You switch it on from inside the project and it creates a private backend used only by that project. Setup takes about a minute and you can keep building while it runs.

What does AI Studio Cloud actually add to my app?

It adds the three things an app needs to remember anything: a database for your records, user accounts so people can sign in, and storage for files they upload. Before this, an app built in AI Studio could show information but had nowhere of its own to keep it. Now bookings, orders, member profiles and uploads can live inside the project itself.

How do I turn it on?

Open your project, go to More and then Cloud, and switch it on from the Overview tab. Setup finishes in about a minute and builds a private backend for that one project. If setup stops partway, your app is left exactly as it was and the Try again button picks up where it left off.

1. Open the AI Studio project you want to add a backend to.
2. Go to More, then Cloud.
3. Switch Cloud on from the Overview tab.
4. Wait about a minute while the backend is created. You can carry on building in the meantime.

AI Studio always asks you to confirm before it builds anything that depends on Cloud, so nothing is added to your app behind your back.

How do I work with my data?

The Database section lists every table in your project with its approximate row count and whether row-level security is switched on. You can add rows, edit any cell by double-clicking it, and select rows to delete. To add a new table or change a security rule, ask for it in the AI Studio chat.

• Optimize sends a health check to the chat when a database is slow or expensive to run. It uses credits like any other chat message.
• Daily Backups capture your tables and rows. They do not include stored files or your app code.
• Restore replaces the live database with a backup you choose. Database access pauses for a few minutes while it runs, and if the restored structure no longer matches your app, ask the chat to patch it.

How do my customers get accounts?

The Users section charts sign-ups over time and lets you search for any user by email address. Create new user adds someone straight away without sending them an email, while Send invitation emails them a link to set their own password. Open any user to see how they signed in, or delete them, which cannot be undone.

Sign-up, invitation and password reset emails are sent from your own account's email address, and the links in them open your app rather than anything branded elsewhere.

Which sign-in settings should I check first?

Check your Site URL and Redirect URLs before you let anyone sign in. A mismatch between these and your real addresses is the most common reason logins fail. Preview addresses are handled for you, and you can add your own, including mobile app links.

• Email confirmation is required by default. Auto-confirm is only for your own testing.
• Switching off Allow new sign-ups closes registration. Anyone already signed in stays signed in.
• You can block passwords that appear in public breach lists and set your own password rules.

Sign-in is by email and password in this first version. More sign-in methods are planned.

Where do uploaded files go?

Files go into buckets that you create in the Storage section. A public bucket is readable by anyone with the link, while a private bucket requires the person to be signed in. Choose the type to match the file: product photos can be public, customer documents should not be.

• Bucket names use lowercase letters, numbers and hyphens, must be 3 to 63 characters long, and cannot be renamed afterwards.
• You can upload files, create folders, download, delete, rename and copy a file's URL. Renaming a file changes its URL.
• You can set a maximum upload size and review who can read and write through row-level security policies.

What does it cost to run?

Cloud runs on database size tiers, starting with Tiny, which is free, then Mini, Small, Medium, Large and X-Large. Each tier shows its hourly price, and you can change tier once per hour. A change takes a few minutes and briefly restarts the app.

• Database storage can only be increased, up to four times a day, and reserved space is billed hourly even while the database is paused.
• File storage grows with your files and you pay only for what is actually stored.
• Pause blocks access while keeping all your data. Resume brings it back.
• If your account balance cannot cover Cloud charges, Cloud pauses on its own. Nothing is deleted, and Wake up restores it once billing is sorted. You can also drop back to the free Tiny tier.
• Remove Cloud permanently deletes that project's database, users and files. Export your tables as CSV and download your files first. Your other projects are not affected.

How do I know my app is safe to publish?

A security advisor card appears on the Overview tab whenever it detects a problem. View issues lists what it found, and Try to fix asks AI Studio to repair them for you. Clear every critical issue before you publish, and treat warnings as advice rather than blockers.

Does this work with every AI Studio project?

Cloud works only with apps built on TanStack Start. If your project is an existing React app, run Migrate to SSR under Project Settings first, which creates an upgraded copy and leaves your original live and untouched. Migrating does not switch Cloud on by itself, so turn it on afterwards.

• Your published site does not change until you publish it again.
• Sharing or remixing a project does not copy its Cloud data. A copy can still send requests to the original project's Cloud, subject to that project's access rules.

You will find all of this inside your AI Studio project under More, then Cloud, with the Overview, Database, Users, Auth settings, Storage and Advanced settings sections. The migration option sits under Project Settings.