Skip to content
← Blog

How to build a web app with Claude, from idea to a live link

Two ways to build a web app with Claude and put it online: ask in Claude chat with the floo connector, with no code or terminal, or build it in Claude Code from your own repository. Both end with a link your team signs in to.

floo team

TL;DR

To build a web app with Claude, describe what it should do and who uses it, and let Claude write it. To put it online, connect floo: in Claude chat, Claude creates the app, deploys it with sign-in and a Postgres database, and sends you the link. In Claude Code, one prompt deploys the app from your repository.

  • No code: Claude chat plus the floo connector. floo keeps the code.
  • Your own repository: Claude Code plus the floo CLI.
  • Either way, the app has a real server, a database that keeps its data, and invite-only sign-in: on by default from chat, one line of config from Claude Code.

A web app is three things: pages people open in a browser, a server that answers them, and somewhere to keep the data. Claude can write all three. What turns that code into something your team uses every day is a place to run it, a database that persists, and a door that only lets the right people in.

Start with what the app should do

The more specific the ask, the better the first version. Name the people, the data, and the one screen that matters:

Build a tool where my team logs customer requests. Each request has a customer, a summary, a status, and who owns it. Show this week's open requests first, grouped by owner.

That is enough for Claude to design the tables, the form, and the main view.

Path 1: build it in Claude chat, no code

Use this if you don't want a terminal or a repository.

  1. Connect floo once. Open floo in Claude's connector directory, click Connect, and approve the sign-in.
  2. Ask for the app. Paste your description. Claude creates the app on floo, which starts with team sign-in and a Postgres database, writes the code, and deploys it.
  3. Get the link. Claude waits for the deploy, fixes it if it fails, and sends you https://<your-app>.getfloo.app.
  4. Invite people. "Invite sam@example.com to the app."
  5. Change it by asking. "Add a priority column." "Show a count of open requests at the top." Every change is a commit, so a bad one rolls back.

The build in chat guide covers Claude, Claude Team and Enterprise, and Cowork.

Path 2: build it in Claude Code, from your repository

Use this if you want the code in your own git repository and editor.

  1. Have Claude Code build the app. Pick a stack you like, or let Claude pick. Next.js, Rails, Django, FastAPI, Laravel, and Go all work.

  2. Deploy it. In the project folder, paste:

    Read https://getfloo.com/docs/introduction.md and deploy this app to floo.
    

    Claude Code installs the floo CLI, writes floo.app.toml, and runs floo deploy. You approve one sign-in in the browser.

  3. Add what the app needs. Sign-in, Postgres, and a daily job are each a few lines in floo.app.toml. The step-by-step version is in how to deploy an app built with Claude Code.

  4. Keep shipping. Every push deploys again.

What makes it a real app, not a demo

  • The data stays. Postgres, not a file in the container or the browser.
  • Only invited people get in. floo's gateway handles sign-in and tells the app who each person is.
  • Secrets stay out of the code. API keys live in the app's environment, set with floo env set.
  • Changes are reversible. Every version is a commit and a deploy you can roll back to.
  • It can run on a schedule. A cron job sends the Monday summary or cleans up old rows.

Which path should I pick?

Pick chat if the person who knows what the app should do is not a developer, or if you want a working tool today. Pick Claude Code if an engineer will own the app, if it needs packages or services the chat path doesn't cover, or if the code should live in your company's GitHub. You can start in chat and move later: floo connect owner/repo moves an app floo hosts to your GitHub repository with its full history.

Frequently asked questions

Can Claude build a web app?

Yes. Claude writes the code for the pages, the server, and the database queries. To make it a web app other people can open, it also needs a host. With the floo connector, Claude creates the app on floo, deploys it, and sends you a link, all from the chat.

Do I need to know how to code to build a web app with Claude?

No. In Claude chat with the floo connector, you describe the app and Claude writes and deploys it. floo keeps the code, so you need no terminal, git, or GitHub account. Developers who want the code in their own repository use Claude Code instead.

Where does the data in a Claude-built web app live?

On floo, each app gets a Postgres database. Claude writes the tables and queries, and the data stays between visits and deploys. Dev and prod have separate databases.

How do I share the app only with my team?

Apps built in Claude chat start invite-only. From Claude Code, set access_mode = "accounts" in floo.app.toml. Then say "Invite sam@example.com to the app" in chat, or run floo apps invite from a terminal. People sign in before they see anything.

Get your app live.

read https://getfloo.com/agents.md and set me up on floo

Get an API key
Usage-based pricing. See plans →