Floot Review (2026): Pricing, Limits and What It Actually Does
Floot is a connector you add to your AI assistant, and it publishes the app your conversation describes. Here is what that buys you and where it stops fitting.
Try Begin.sh free → Official site
How the connector actually works
Floot does not ship its own chat window. You add it to an assistant you already use, and the vendor lists Claude, ChatGPT and Cursor as supported hosts, with a page for other MCP clients. From there the loop is conversational: describe the project, let the connector build it, then keep asking for changes until the thing matches what you had in mind. The example the site walks through is an order book for a bakery, refined live with instructions like making the headline bigger. Two claims in that flow matter more than the demo itself. There is no git step and no terminal, and there are no build credits burned per edit. That is a real design choice, and it explains most of what follows.
What the platform covers on your behalf
The pitch is that a Floot project is not a front end pretending to be an app. According to the vendor, publishing is one click and the result gets its own shareable link on a floot.app subdomain. Data persistence, user accounts and recurring scheduled tasks are listed as built in rather than bolted on. So is transactional email, which the site frames as receipts, updates and notifications leaving your app without a separate mail provider. Search engine basics are described as automatic. Integrations get their own section, naming Stripe payments, Google login and Zapier, with a guided setup for the rest. Taken together that is the full boring middle of a product, which is exactly the part most prompt-to-app tools quietly leave to you.
Pricing, and what the site will not tell you
The comparison block on the home page makes one pricing claim and one only: flat plans rather than pay per token, with a footnote saying credits apply to the optional agent and to AI image generation. There are no dollar figures anywhere on the landing page, no free tier described, and no usage ceilings named. That is not a criticism so much as a warning about how to read this page. Do not plan a budget from the home page, and do not assume the flat plan covers the credit-metered parts. Open the pricing page before you commit anything, and check it again later, because plans on tools this young move around. Anyone quoting you a specific Floot price from memory is guessing.
The trade you are actually making
Everything convenient about Floot comes from the same decision: the platform owns the runtime. The database is theirs, the hosting is theirs, the deploy button is theirs, and the app lives at their subdomain until you point a domain at it. For a non-technical founder shipping an internal tool or a first paid product, that is a fair swap and it removes a week of setup. For anyone who expects to hand the codebase to a contractor, run it on their own infrastructure or audit what is running in production, it is a harder sell. The honest question is not whether the output is good. It is whether you are comfortable with the output living somewhere you do not control.
Signals that point somewhere else
Three situations come up often enough to name. First, you want a marketing site or landing page, not an application with users and records, so the whole backend story is dead weight. Second, you need the source files, because a client is paying for them or because the project has to go into an existing repository. Third, you are rebuilding a page you can already point at, and what you want is a close copy rather than an original design conversation. Begin.sh handles all three: give it a prompt or a URL to clone, get back a static site or an Expo project, and download the zip. It deliberately does not do hosting, backends or auth, which is the point.
What you actually get
An app, not a mockup
The vendor describes finished projects with a database behind them, not clickable prototypes. One click publishes to a live link on a floot.app subdomain that you can send to someone immediately.
Accounts and scheduled jobs
User sign-up, stored records and tasks that run on a schedule are listed as part of the platform, so you are not wiring an auth provider or a cron runner yourself.
Setup guided, not documented
Stripe, Google login and Zapier connect through a step-by-step flow rather than a docs page you follow alone. Useful if integration work is the part that usually stalls you.
No terminal in the loop
No git, no local build step and no per-edit build credits, per the vendor. Refinement happens in the same chat where the project started, which keeps the whole thing in one window.
Floot and Begin.sh side by side
| Feature | Floot | Begin.sh |
|---|---|---|
| Where you drive it | Inside Claude, ChatGPT or Cursor via a connector | In the browser, from a prompt or a URL to clone |
| What you end up with | A published app on a floot.app link | A downloadable zip of a static site or Expo app |
| Database and user accounts | Listed as built in | Not included, by design |
| Hosting | Handled by the platform | You host it wherever you like |
| Email and scheduled tasks | Listed as built in | Not included |
| Cloning an existing page | Not described on the site | Paste a URL and work from that |
| Pricing detail on the home page | Flat plans claimed, no figures shown | Check the site for current terms |
Trying it without wasting an evening
- Read the pricing page first
The home page claims flat plans but names no numbers, and credits apply to the optional agent and image generation. Five minutes there saves an argument with yourself later. - Add the connector
Floot publishes install links for Claude and ChatGPT, plus a page covering Cursor and other MCP clients. Pick the assistant you already keep open all day. - Describe one narrow thing
Ask for a single workflow with real records, like the order tracker in the vendor demo. Broad prompts produce broad apps that are hard to judge. - Push on the parts that bind
Try a sign-up, a payment and one scheduled task. Those three decide whether the platform is doing the boring work or only appearing to.
Questions people actually ask
Is Floot a separate app I have to learn?
No. It is added to an assistant you already use, and the site lists Claude, ChatGPT and Cursor with a page for other MCP clients. Building and refining happen in that chat, so there is no second editor to open and no terminal in the loop.
What does Floot cost?
The landing page states flat plans rather than per-token billing, and a footnote says credits apply to the optional agent and to AI image generation. No prices appear anywhere on that page, so check the official pricing page for current rates rather than trusting any number you read elsewhere.
Can I get the source code out?
The site does not describe exporting a codebase, and its whole pitch is that hosting, database and deploys are handled for you. Treat code portability as an open question to raise with the vendor before you build anything you would need to move later.
Does it handle logins and payments?
The vendor lists user accounts, stored data and recurring tasks as built in, and names Stripe payments, Google login and Zapier among supported integrations with a guided setup. Verify each one on a throwaway project before you depend on it in front of paying users.
Who is behind it?
The site says Floot is backed by Y Combinator and lists a San Francisco company, with a Discord community, public docs and a changelog. That is more transparency than many tools in this category offer, and the changelog is a reasonable way to judge momentum.
I only need a website, not an app.
Then most of this platform is overhead. Begin.sh takes a prompt or a URL to clone and hands back a static site or an Expo project as a zip, with no hosting, backend or auth in the way. You own the files and put them wherever you want.
Sometimes you just want the files
Begin.sh turns a prompt, or a page you point it at, into a static site or an Expo app you download as a zip. No hosting, no backend, no account system to inherit.
Try Begin.sh free →