Floot AI App Builder: Build and Publish from Chat

Floot is an AI app builder that connects to the assistant you already use, such as Claude, ChatGPT or Cursor. Describe the app you need in that chat, and the assistant uses Floot to create its pages, backend and database, then returns a live preview. This guide explains what Floot actually builds, how to get a first app online and where its free plan, mobile output and data controls have limits.

What is Floot? A plain-English explanation

Think of Floot as the place where your AI assistant builds and runs an app. The assistant writes and changes the project; Floot provides the working environment, database, sign-in, file storage and hosting. The result is a TypeScript and React web app with backend endpoints, rather than a static picture of an interface. A founder can try a booking or customer portal idea; a developer can ask the same assistant to inspect files, fix a failing request or add a database table. You still need to specify the real user flow and check the result before customers use it. Floot's platform overview describes the underlying pieces.

From a prompt to a working web app

Start by connecting Floot through the Claude and ChatGPT setup guide, or use its remote MCP connection in a compatible client. Sign in to Floot during setup. In your chat, describe who will use the app, the screens they need, the data each action saves and whether people must sign in. For example, ask for a feedback form that stores submissions and an admin page to review them. Let the assistant create the project, then open the live preview it returns. Submit a test record, check that it appears in the right view, and ask for a focused correction if anything fails. Repeat until the key flow works; ask the assistant to publish and check the final URL. Floot's connector can read runtime logs and run typechecks or tests, so those checks can be part of the iteration. The capability list shows which actions are available.

Backend, accounts and services included

A Floot project can use managed Postgres, email-and-password or Google/Microsoft sign-in, file storage, transactional email, scheduled jobs and hosting. This helps when the idea needs actual records, accounts or notifications instead of a landing-page mockup. Ask for only the services the first user journey needs, then test permissions and error cases in the preview. Third-party services can be connected, but API keys are entered through a Floot browser form rather than pasted into the AI chat. If an existing repository is your starting point, note that Floot does not import its codebase as-is: the assistant can rebuild it page by page, while keys and data migration need separate work.

Web publishing and iOS or Android apps

Publishing creates a web app on a Floot subdomain; a custom domain is a paid-plan feature. Floot can also turn that web project into installable iOS and Android apps, but mobile builds must be enabled by a person in the browser under Publish → Mobile. The assistant cannot switch that setting on through the connector. App-store distribution requires your Apple or Google developer accounts, and current plan entitlements and Google Play connection conditions should be checked in the mobile build guide. Test the mobile build on a device rather than assuming a good browser preview guarantees store readiness.

Free plan, build actions and the real cost boundary

As checked on 25 September 2026, the public USD monthly view lists Free at $0, Pro at $25 and Power at $100 per month. The free plan has 100 build actions per UTC day and, according to the billing guide, a rolling seven-day cap of 400. A build action is a connector tool call, including a read or edit; failed calls do not count. AI model usage comes from your own assistant subscription. Floot credits are a separate pool for generated images and AI features that run inside your published app, while hosting has its own allowance. Paid tiers raise daily action limits and provide custom domains and downloadable code. Check current plan details before committing: taxes, regional billing and older-plan entitlements may differ. Floot's billing FAQ and current pricing/mobile pages disagree about some one-time free balances and mobile entitlements, so those disputed counts are deliberately omitted here. The current pricing page also says the optional Floot agent can use credits.

Code ownership, exports and data privacy

Floot's security and data guide states that you own the app code, data and IP. Database export is a browser action available on any plan; a runnable code ZIP requires a paid plan and is downloaded from the project menu. The connected AI assistant is a separate provider: your prompts and Floot tool results sit in that provider's context. If you ask it to query a database containing real customer records, those returned rows can enter that context too. Keep a private project private, treat preview links as shareable access tokens, and review permissions and sensitive-data handling before publishing. Publishing a web app makes its URL reachable; add app-level login if a page must be restricted.

Frequently asked questions

How do I start building with Floot?

Connect Floot to an AI assistant, describe a small app with its users, screens and data, inspect the live preview, then request fixes and publish once the core flow passes your test.

Can I use Floot for free?

Yes, there is a free plan with daily and weekly build-action limits. Your AI assistant subscription is separate, and hosting or in-app AI usage can add costs. Check the current pricing page for your account.

Can Floot make a mobile app?

Yes. A Floot web project can be built as iOS and Android apps after you enable mobile builds in the browser Publish panel. Store distribution needs developer accounts and is subject to current plan conditions.

Official resources and builder community

Use these first-party channels for setup, current terms and account-specific help.

• Floot documentation — official setup and reference.
• Floot support — account or project support; sign-in required.
• Floot Discord community — builder community.