Build an App · Lesson 3Pro+~16 min readHosting + database + accountsAdvanced

Ship it for your team — hosting, accounts, and your data.

Your tool has run in your browser, for you. This lesson makes it real for everyone else: hosted online, backed by a database so data survives and is shared, gated behind logins where it matters, and connected to the data you already have. The coding AI does the heavy lifting — you describe what you want.

The mental model

A tool people rely on needs to live somewhere, keep its data safely, and let the right people in.

Everything so far ran in your browser for you alone. To make a tool your team uses, three things change: it gets hosted online, its data goes into a real database that survives and is shared, and — when needed — it sits behind a login. A coding AI handles all of it; you describe what you want.

Step 01 Put it online

Pick a platform that builds and hosts in one place (the same conversational/agentic build tools from the website track work here). Deploy gives you a real URL you can send to your team.

Step 02 A real database

In-memory data resets on refresh. A database makes it permanent and shared across everyone using the tool. You don’t design tables by hand — describe what to store.

Database promptStore entries in a real database so the data persists and is shared by everyone who uses the tool. I need to save [the fields]. Let me view, search, edit, and delete records. Tell me anything I need to set up on my end.

Step 03 Accounts and access

Decide who should get in. Not every tool needs logins — but an internal tool with real data usually does.

Open — anyone with the link (fine for a public calculator).
Login required — only signed-in users (most internal tools).
Roles — admins can edit, others can only view.

Access promptRequire a login to use this tool. Only people on my team should have access. Give me a way to add and remove users, and make sure one person’s data isn’t visible to another unless I allow it.

Step 04 Connect to data you already have

The real payoff is plugging the tool into your existing world — a spreadsheet, your CRM, a calendar, an API. Describe the connection and what should flow.

Connect promptConnect this tool to [your spreadsheet / CRM / calendar]. When [event], it should [read or write what]. Start read-only so nothing gets changed by accident, and tell me how to authorize the connection.

Step 05 Going live, safely

Test the whole flow with one real teammate before rolling out.
Make sure data is backed up — ask the AI how backups work on your platform.
Keep a way to roll back if an update breaks something.

The moment a tool holds real data behind a login, security matters. Don’t put sensitive customer or financial data into a tool without proper access controls — and see the “Secure Your AI Use” build for how to do this responsibly.

Your challenge: put it in someone else’s hands

Take your Lesson 2 tool the rest of the way:

Deploy it to a real URL on a hosting platform.
Move its data into a real database so it persists.
Add a login and share access with one teammate.
Connect it to one existing source (a sheet or app), read-only.

That’s an internal app your team can actually use — built with AI, owned by you. You’ve finished the Build an App track.

Next build: Build an AI Agent →Back to Build an App

What you can do now

Deploy an AI-built tool to a real, shareable URL
Give a tool a real database so data persists and is shared
Add logins and roles to control who gets in
Connect a tool to your existing data, starting read-only
Roll out safely with testing, backups, and rollback

You’ve finished this build

Build an App — complete

You can turn a manual task into a working tool, then into a real internal app your team relies on. Ready for the next one? Build an AI Agent → or see all builds.