Start now

Guide · Database

Give your AI-built app a real database

Many AI-built apps save data in a local file or in the browser, which breaks as soon as real people use them. On Project3000 every app gets its own database and cache, already running.

By the Project3000 team · · 4 min read

In short: every app gets its own PostgreSQL-compatible database and Redis-compatible cache. Your AI connects the app to them with the deploy prompt, and converts apps written for SQLite, MySQL or MongoDB.

Why a local file isn’t enough

A SQLite file or browser storage works on one computer. Online, your app runs as two copies on separate servers, and both must see the same data. A shared database keeps every copy in step and keeps the data safe when a server is replaced.

What you get

  • A PostgreSQL-compatible database, available to your app as DATABASE_URL.
  • A Redis-compatible cache for sessions, live updates and rate limits, as REDIS_URL.
  • Every record stored on three servers, so a server failure loses no data.
  • Your data in your download: the dashboard’s Download button includes a database dump that restores into any PostgreSQL.

How your AI connects it

The deploy prompt tells your AI exactly how: use the provided settings, retry briefly if the connection drops, and change SQLite, MySQL or MongoDB code to PostgreSQL. You don’t write any of it yourself.

Storage for files and database together is 1 GB on Basic, 5 GB on Pro and 10 GB on Business.

Questions and answers

Can I connect with my own database tool?
The database is private to your app and isn’t reachable from the internet. Use the Download button for a full copy, or ask your AI to add an admin page to your app.
Can I use Supabase or Firebase instead?
Yes. Apps can connect to outside services; the included database is there if you want it.

Put your app online today

One prompt in the AI you already use, one click to deploy. A database, HTTPS and a link you can share are included. From $9.90 per app per month.

Start now