Diagram: an AI-built internal tool goes to a Croft private full-stack host with a database, not a public PaaS plus a separately wired database.

Blog · October 14, 2026 · Rich Chetwynd

How to deploy an AI-built app with a built-in database

Deploy an AI-built app with an integrated database: put it on a private host that includes a real SQLite database, then ask your assistant to save the data.

Short answer: deploy to a host that includes a real SQLite database

To deploy an AI app with an integrated database, put it on a host that already includes the database, then ask your assistant to save the data there. On Croft, each app gets its own SQLite database on your private server, with shared workspace data, team sign-in, and backups, so there is no separate database product to provision or wire up. You keep building in Claude, Cursor, ChatGPT, or another assistant. (Already have a host? See how to give an AI-generated app a real database.)

Can AI set up an app database? Yes, for the app side. Your assistant adds the tables and the code that reads and writes them. What it can’t do on its own is provide a place for that data to live. That is what the host is for. This post is the hosting decision: a private full-stack host with a database and team access, versus a public PaaS plus a database you attach yourself.

What “integrated database” means

For an AI-built internal tool, an integrated database is not “any live URL plus a DB add-on.” It means:

  1. A real database that comes with the app: no connection strings to manage and no separate service to stand up
  2. A lasting private URL colleagues can bookmark and reopen
  3. A shared app database, so everyone works against the same saved data
  4. Team sign-in, so only your people open it (company login as the access benefit)
  5. Backups and rollback when the next AI edit goes sideways
  6. Room to keep iterating in Cursor or Claude and redeploy without babysitting a multi-service public stack

Croft uses SQLite per app with shared workspace data. Related: artifacts to apps, backups and versioning, for developers, host a Cursor app.

You built the app. Now you need a real place with data.

Cursor, Claude, and similar tools make it easy to ship a useful internal tool: an approvals queue, an ops panel, a tracker, a small admin UI. It runs for you. Then you hit the full-stack cliff.

What usually goes wrong:

  • You deploy to a public PaaS (Railway, Render, Vercel). The default posture is internet-facing. Privacy, auth, and team access are your job.
  • The app needs saved data, so you add Postgres or another database as a second product: connection strings, backups, and who can reach it.
  • Login is DIY. You wire auth, invites, and roles before anyone can safely use the tool.
  • You keep iterating with AI, but every redeploy still feels like standing up a small public product stack for a team-only app.

Developers and non-developers both hit this. Almost everyone builds with AI now. Developers pick a private team host when they do not want full PaaS ops for a small internal tool. Non-developers pick it when the assistant built something useful and the company needs a lasting place with shared data.

Broader context: Where to host a vibe-coded app privately, Where to host a Cursor vibe-coded app for your team, Where to host an app I built with AI, and Croft vs Railway.

How to deploy from Claude, Cursor, or ChatGPT

  1. Start a free trial and get a croft (private server for your workspace).
  2. Connect your assistant: Claude, Cursor, ChatGPT, or another supported path.
  3. Ask it to deploy the app to your croft (not a public host). Optional browser path: Ask Croft.
  4. Ask for the data that should persist, for example “save each request so we can find it later.” Your assistant adds a table and wires it up. The app gets its own database on your private server, and teammates work against the same saved data.
  5. Invite colleagues. They open a normal URL, sign in with company login, and use the tool.

More on turning builds into hosted apps: artifacts to apps. Cursor-focused landings: host a Cursor app and Deploy a Cursor app for your company. For the data step in more detail, see how to give an AI-generated app a real database.

Backups, access, and governance

The database is only useful if the team can trust it. On Croft:

  • Backups and rollback. The database is backed up, so a bad AI edit is recoverable. See backups and versioning and security.
  • Access. Apps are private by default and sit behind team sign-in, so only the people you invite can open them.
  • Governance. Admins control who can do what in the workspace. See roles and permissions.
  • Your data stays yours. You can export it any time. See your data.

Public PaaS + wired DB vs Croft

Need Public PaaS + separate DB Croft
Default URL Public / preview by default Private by default
Database Extra product you wire and back up Included with the host (SQLite per app, shared workspace data)
Team sign-in You assemble auth Company login in front of apps
Best when Internet-facing products and services AI-built / vibe-coded apps the team opens
Ops load for a small internal tool App host + DB + auth + hardening Low

This is posture, not a peer feature checklist. Railway, Render, and Vercel shine when the app faces the internet and you want classic public PaaS delivery. Croft is a private team host: you bring the AI-built app; the team gets one place to open it, with the database already there. See Croft vs Railway and the rest of compare.

When public PaaS plus a database is right

Pick a public PaaS and a separately wired database when:

  • The app is meant for customers or the public internet
  • You want preview deploys, multi-region or edge-style delivery, and classic product hosting
  • You are happy operating the app host, the database, auth, and privacy as the service grows

That is a strong job. It is simply the wrong default for a private full-stack deploy with a database when only your company should use the tool.

When Croft is right

Pick Croft when:

  • You built an internal tool with AI and the team needs to open it
  • You want private hosting by default, not a public URL you lock down later
  • You want the database included with the host, not a second product to wire
  • You want shared data, team sign-in, backups, and rollback without assembling a stack
  • You would rather connect Cursor or connect Claude and deploy than stand up a full public PaaS for a small tool

Expect a private place for team apps, optional connectors, templates, and a path to keep shipping from your assistant. Optional in-product AI chat: Ask Croft.

FAQ

How do I deploy an AI app with an integrated database?

Deploy the AI-built app to a private team host that includes the database, not to a public PaaS with a separate DB add-on. On Croft, connect your assistant, ask it to deploy to your croft, then ask for the data that should save. Each app gets its own SQLite database, with shared workspace data, team sign-in, and backups.

Can AI set up an app database?

Your AI assistant can add the tables and write the code that saves and loads data. It still needs a host that provides the database. On Croft the database comes with the app, so you ask for what should persist and the assistant wires it up. You do not provision a database or manage connection strings.

How do I do a private full-stack deploy with a database?

The same way: choose a private host that includes the database and team access, rather than assembling a public host, a database, and auth separately.

How do I host an AI internal tool with a database?

Put it on Croft. Connect Cursor or Claude, deploy to your croft, and ask for the data that should save. The database comes with the host. See for developers and artifacts.

What is a private team app with a database?

A lasting app your colleagues open behind team sign-in, with shared saved data, not a public preview URL and not a local demo that forgets everything on refresh. Croft hosts that kind of app.

Is this the same as “give my AI app a database”?

Not quite. Giving an AI-generated app a real database is about making data stick once you have a host. This post is the earlier choice: private full-stack place with DB and team access, versus public PaaS plus a wired database.

Is Croft the same as Railway, Render, or Vercel?

No. Those are public PaaS options for internet-facing services. Croft is a private team host for AI-built internal apps. See Croft vs Railway.

Does Croft use Postgres?

No. Croft uses SQLite per app with shared workspace data. You get a real database with the host; you do not provision a separate Postgres service for a typical team internal tool.

Do only non-developers use Croft?

No. Developers use Croft for small private team projects when they do not want Railway/Render/Vercel-style infra. Non-developers use it when the assistant built the app and they need a private place the team can open. See Croft for developers.

How much does Croft cost?

Starter from $24/month on annual billing, Growth $59 and Scale $99/month on annual. 14-day free trial, cancel anytime. See pricing.

Start a workspace →  ·  For developers →  ·  Host a Cursor app →  ·  Ask Croft →  ·  Pricing →

More from the blog

CRM Quotes z z

Your team’s first app could be live tonight.

Free for a day, and a week once your first app is live. No card needed.