# How to turn a Claude artifact into a real web app

A Claude artifact is a great prototype. To give it a URL your team signs in to, a database everyone shares, and a server that runs on a schedule, ask Claude to move it onto floo. Here is what changes and how.

Canonical URL: https://getfloo.com/blog/how-to-turn-a-claude-artifact-into-a-web-app

## TL;DR

**To turn a Claude artifact into a real web app, connect floo to Claude and ask: "Turn this artifact into a floo app with sign-in and a database." Claude keeps the interface you built, adds a server and a shared Postgres database, deploys it, and sends you a link your team signs in to.**

- Artifacts are the fastest way to try an idea. Move it when other people need to use it every day.
- The move adds a server, a shared database, invite-only sign-in, and scheduled jobs.
- You keep building in the same chat. Every change is a commit you can roll back.

An artifact is where a lot of good tools start: a calculator, a tracker, a dashboard you sketched with Claude in ten minutes. It runs inside Claude, which is perfect for trying the idea. When the team wants to use it every day, it needs the things a hosted app has.

## When to move an artifact to an app

Move it when any of these is true:

- **Several people need the same data.** One person's edits should show up for everyone.
- **It should only open for your team.** A link that anyone can open is a link anyone can open.
- **Something should happen when nobody is looking.** A Monday summary, a nightly sync, a reminder.
- **It needs a secret.** An API key for your CRM or your email provider belongs on a server, never in the page.
- **It needs a real URL.** Something people bookmark, or a custom domain.

## How to move it

1. **Connect floo.** Open [floo in Claude's connector directory](https://claude.ai/directory/connectors/floo), click **Connect**, and approve the sign-in.
2. **Ask in the chat that has the artifact:**

   > Turn this artifact into a floo app with sign-in and a database. Keep the interface. Store the entries in Postgres so everyone on the team sees the same data.

3. **Claude does the move.** It creates the app on floo, which starts with team sign-in and a Postgres database. It moves the interface into the app, writes the server and the tables, and deploys.
4. **Open the link.** Claude sends `https://<your-app>.getfloo.app`. Sign in, check it works, then invite people: "Invite the ops team."

## What changes under the hood

| In the artifact | In the floo app |
| --- | --- |
| Runs in Claude's page | Runs on a server at its own URL |
| Data belongs to the artifact | Data lives in a Postgres database the whole team shares |
| Anyone with the link | Invite-only sign-in, and the app knows who each person is |
| Runs while someone has it open | Runs all the time, plus scheduled jobs |
| Keys would sit in the page | Keys live in the app's environment |

The interface usually moves over almost unchanged. The new work is the server: the routes that read and write the data, and the rules about who can do what.

## Keep building

Ask for changes in the same chat: "Add an export button." "Email me when a new entry is marked urgent." Each change is one commit, and every commit deploys to the app's link. If an engineer later wants the code in your company's GitHub, `floo connect owner/repo` moves the app there with its full history.

For the longer version of building from chat, see [how to build a web app with Claude](https://getfloo.com/blog/how-to-build-a-web-app-with-claude) and the [build in chat guide](https://getfloo.com/docs/guides/build-in-chat).

## FAQ

### How do I turn a Claude artifact into a web app?

Connect floo to Claude and say "Turn this artifact into a floo app with sign-in and a database." Claude creates the app on floo, moves the artifact's interface into it, adds a server and Postgres tables for the data, deploys it, and sends you a link your team signs in to.

### What does an artifact need to become a real app?

Usually three things: a server that runs when nobody has the chat open, a database everyone shares, and sign-in so only the right people get in. Scheduled work, like a weekly email, needs a server too.

### Can I keep building it in Claude after it moves?

Yes. Keep asking for changes in the same chat. Each change is a commit on floo and deploys to the app's link, and a bad change rolls back.
