How Floot works
Floot builds and hosts full-stack apps, and the AI assistant you already use drives it over the connector. What you get, and what it costs.
Floot gives you a full-stack app — database, sign-in, file storage, email, and hosting — with no infrastructure to set up. You build it by talking to the AI assistant you already use: Claude, ChatGPT, Cursor, Codex, or any other MCP client.
What you get
A Floot project is a real TypeScript and React app — pages, components, and backend endpoints — and you can read or export all of it. Floot runs the parts you would otherwise have to stand up yourself:
- Database
- A managed Postgres database. Your app's endpoints query it directly, and you can browse the tables and download a backup yourself.
- Accounts and sign-in
- Email-and-password sessions, or Sign in with Google or Microsoft through OAuth that Floot brokers for you — no developer account of your own to register.
- File storage
- Somewhere for the files your app's users upload, and for the images, icons, and fonts your app ships with.
- Email and push
- Transactional email your app can send with a log of what went out, plus web and native push notifications.
- Scheduled tasks
- Jobs that run on a schedule, without a server to keep alive.
- Hosting
- Publish to a free
<yourname>.floot.appsubdomain. A custom domain is a paid-plan feature — see How to add a custom domain.
How your assistant drives it
Floot runs a remote MCP server. You connect it once to the assistant you already pay for, and after that you describe what you want in your ordinary chat. Your assistant creates the project, writes the files, provisions the database, runs the app, reads its own errors, and publishes — each of those is a tool call it makes against your project on your behalf.
You are not left guessing what happened. Creating a project returns a live preview link, and the preview keeps updating as writes land. See Your project view for what is on that screen, and What your AI can do for the full set of actions.
Claude and ChatGPT install Floot in one click from their own directories. Every other client takes a server URL and an OAuth sign-in. Start at Build from Claude & ChatGPT or Connect any MCP client.
What it costs
The thinking runs on your own subscription. Your assistant brings its own model, so Floot charges nothing for tokens — they are not Floot's to charge for.
Floot meters the work instead, in build actions: one per tool call your assistant completes against your project, reads included. A few calls are exempt — polling a running job or a publish, listing your projects, fetching a preview link, cancelling, and unpublishing — and calls that fail are not counted. Free accounts get 100 build actions per UTC day plus 400 in any rolling seven days; paid plans raise the daily number and drop the weekly ceiling entirely. See Build actions.
Where credits still apply
Build actions are not the only meter. Floot credits are a separate balance, and two things spend them:
- Generating images. Asking your assistant to generate image assets runs an image model on Floot's side, so it is billed in credits.
- AI features inside your published app. If your app calls a model through Floot's built-in AI package, every call your app's users make spends credits.
Two meters, two owners
Build actions are counted against your own account, across every project you touch. Credits are always charged to the owner of the project, never to a collaborator working on it. Neither meter is deducted from the other.