Floot Review 2026: Building a Client Portal With Claude and Floot

Floot is a platform for building and hosting apps from inside an AI chat. You add the Floot connector to Claude, ChatGPT, Cursor or another AI app, describe what you want, and the app is built and published at its own link. Floot is backed by Y Combinator, and its site says no technical background is needed.

The part that matters for a business owner is the split of work. You keep using the Claude or Codex subscription you already pay for to do the building. Floot handles the pieces that usually need a developer: the database, user accounts, files, email and hosting. A client portal is a good test of that, because it needs logins, saved records, file sharing and email notices.

This review walks through a client portal build, then covers cost, setup, limits and fit. For the wider field of app builders, see our Lovable alternatives page.

What Floot Is

Floot lets you build real apps from within Claude and ChatGPT rather than in a separate builder window. It also works with Cursor and other AI apps. Its site says no git or terminal is needed.

Apps go live at their own link. Floot says they can be published to the web and to the app stores with one click. Connecting Google Play needs a paid plan; Apple is available on every plan. SEO essentials are added automatically.

Floot's site lists Stripe payments, Google login and Zapier among its integrations, plus thousands of other services with step-by-step setup guidance.

• Where you build: inside Claude, ChatGPT, Cursor or another AI app
• What Floot runs: the backend, data, logins, email and hosting
• Who it is for: people who do not write code
• Publishing: a live link, with web and app store publishing

Building a Client Portal With Claude and Floot

A client portal is a private place where your clients sign in to see their own information: documents, project status, invoices or messages. It is a useful example because Floot says it takes the backend off your hands, and a client portal needs one for every feature.

The steps are short. Add the Floot connector to Claude. Describe the portal in plain language: who signs in, what each client can see, and what you upload for them. Floot says Claude does the building on your own subscription. Floot stores the data, creates the user accounts, keeps the files, sends the emails and puts the portal online.

Be specific in your first message. Name the client record fields you need, say that each client may only see their own records, and say which events should send an email, such as a new document or a status change. Then sign in as a test client and as yourself, and check that one client cannot see another's records before you invite anyone.

• Sign-in: Floot says users can create accounts
• Saved data: client records, statuses and notes live in Floot's database
• Files: Floot handles the file side of the app
• Email: Floot says apps can send emails, receipts, updates and notifications
• Hosting: the portal is published at its own link

What Floot Handles and What Stays With You

Floot handles the database, authentication, files, email and deployment. You do not set up a separate database service, an auth provider, a mail service or a hosting account.

You design the portal: what clients see, what you upload, how long records are kept and who gets notified. Check that what Claude builds matches what you described.

If your portal holds sensitive client data, read Floot's own terms and privacy information on floot.com before you load real records. This review did not test Floot's security or compliance.

Using Your Own Claude or Codex Subscription

Floot says people build with the Claude or Codex subscription they already have. The building happens in your AI app, and Floot supplies the backend and hosting. Floot says normal building actions do not add a second AI-credit bill.

Floot also has credits. The homepage says credits apply only to the optional Floot agent and AI image generation. The pricing page says AI credits are for powering in-app AI features or using the optional Floot agent.

Your Claude or Codex plan has whatever usage limits that provider sets.

Who Owns the Code and Data

You own your app's code and data, according to Floot's self-hosting docs. Paid plans can export the code, and the database can be exported on any plan.

Moving off Floot takes setup. Before the exported code will build, you replace Floot's managed services with your own: logins, file storage, email, scheduled jobs and AI keys. You also supply your own database connection and secrets, re-upload stored files and maintain the code yourself. Floot support does not cover self-hosted apps.

Ownership and infrastructure control are separate questions. You own what you build and can take it with you. While the app runs on Floot, Floot runs the servers, database and hosting, so you do not set up or control that infrastructure yourself.

Floot Pricing

Floot uses flat plans rather than per-token billing. These are the plans listed on Floot's pricing page. Monthly and yearly billing are offered. Yearly rates show when you switch the Yearly toggle on the pricing page, and Floot describes yearly as 2 months free.

Each paid plan includes a monthly hosting allowance in its price: $10 a month on Pro and $25 a month on Power. It is not an extra fee. Connecting Google Play requires a paid plan; Apple is available on every plan.

Setup and Getting Started

The Free plan lists 100 building actions a day and no included hosting allowance. Check Floot's plan page for what you can publish on Free before you plan on it.

If you want a custom domain or no Floot badge on a client-facing link, those are on Pro and Power.

Building actions are capped per day on every plan.

Who Floot Fits

Floot fits owners and small teams who want a working portal, intake tool or internal app and do not want to hire a developer or manage servers. It fits best when you already use Claude, ChatGPT or Cursor and want Floot to handle the backend and hosting.

It also suits a quick prototype. You can put a working version online at its own link and decide later whether to invest more.

• Good fit: a simple client portal with logins, records, files and email notices
• Good fit: non-technical owners who already pay for Claude or ChatGPT
• Good fit: prototypes you want online at their own link
• Check first: anything with strict compliance duties, where you need to review Floot's terms

Where Floot Is the Wrong Choice

Floot is the wrong starting point when you have specific compliance or infrastructure requirements. Examples are data that must sit in a set region or on your own servers, a security review of the hosting stack, or controls a regulator expects you to run yourself. While the app runs on Floot, Floot runs that infrastructure, not you.

An important app is a different question. A portal can be central to your business and still fit Floot, since you own the code and data and paid plans can export it to self-host. Complex workflows and deep integrations with legacy systems are the other case where a custom build can serve you better. Our page on Lovable alternatives compares Floot with other AI builders.

Verdict

Floot is a good fit for a first client portal built by a non-developer, mainly because the database, logins, files, email and hosting come with it and you build with the AI subscription you already have. The Free plan lets you test the idea at no cost, and Pro at $25 a month, which includes $10 a month of hosting, covers a custom domain and badge removal.

Test permissions carefully before real clients sign in, and read the terms before loading sensitive data. You own the code and data, so you are not locked in. Look at a custom build or self-hosting when you hit a specific compliance or infrastructure requirement, not just because the portal became important.