About Floot
Floot is an AI app builder that works with Claude, ChatGPT and other supported AI assistants. Describe an app to build and publish it with hosting, a managed PostgreSQL database and user logins. Floot supports Stripe payment integrations, custom domains on paid plans, and iOS and Android builds from web projects. A free plan is available; paid plans start at $25 per month. Build actions, Floot AI credits and hosting have separate allowances. App-store release requires developer accounts and store review.
Best for: Founders and small teams building web-app MVPs, client portals, internal tools or AI-enabled products through an existing AI assistant, with managed backend services and hosting.
What is Floot?
Floot is an app-building and hosting platform that connects to the AI assistant you already use. You describe a product in Claude, ChatGPT or another supported MCP client, and the assistant uses Floot to create the project, write code, work with data and publish the app. Floot provides the environment where that software runs, including its backend, database and hosting. Source: Floot overview
Floot's original Product Hunt launch was on 7 August 2025. Product Hunt records a separate Floot MCP launch on 24 September 2026. Source: Product Hunt launch history
From a conversation to a working app
A project contains TypeScript and React code, frontend pages and backend endpoints. The connector lets an assistant inspect files, modify code, run type checks and tests, read logs and inspect a live preview. It can also use a selected element or annotation as context for a change. This gives founders and small teams a way to iterate on a real application through conversation while checking the result on screen. Source: connector capabilities
The screenshot gallery shows an example IdeaGrit storefront, its product catalog and Floot's database interface.
The services behind the interface
Floot combines a managed PostgreSQL database with sign-in, file storage, email, realtime updates and background work. Apps can use email/password authentication or Google and Microsoft sign-in. Other OAuth providers require their own credentials. External services can be connected through APIs; Floot's directory includes Stripe, Shopify, Zapier and Twilio. These integrations can require separate accounts, configuration and charges. Sources: built-in services, integration directory
The database browser lets you inspect and edit records without leaving the project. One important development detail is that the preview and published app share a database: changes to records or schemas can affect live data immediately. Publishing controls code changes, not a separate staging database. Source: database documentation
Web publishing and mobile distribution
A web app can be published to a Floot subdomain, with custom domains available on paid plans. Publishing sends the current frontend and backend together; a failed publish leaves the previous live version in place. Public and invitation-only publishing are separate options. Source: publishing
Floot can also package a web project for iOS and Android. Connected developer accounts receive builds in TestFlight or Google Play internal testing. Developers still prepare their store listing and submit the release for review themselves. Changes to mobile screens need a new app build and release; updating the web version alone does not replace an installed app's interface. Sources: mobile builds, store publishing
How the costs fit together
There are three separate allowances to understand: daily build actions for connector work, AI credits for Floot-powered AI features and image generation, and usage-based hosting. The AI assistant's own subscription is separate. A plan's included hosting is an allowance, rather than unlimited hosting. See the Pricing section for current plan amounts and annual options. Sources: pricing, billing guide, hosting guide
Ownership and portability
Floot states that users own their code and data. Paid users can download the project code; database exports are available across plans while the hosting balance permits access. Moving an app elsewhere requires additional work: Floot-managed packages must be replaced, secrets configured and hosted files migrated. Code ownership should therefore be distinguished from a fully portable copy of every managed service. Sources: exports, self-hosting
This profile summarizes published product documentation checked on 20 October 2026.
Pros
- Combines the database, authentication, storage and hosting in one project.
- Works with an existing AI assistant through MCP.
- Live preview, visual feedback and debugging tools support iterative development.
- Supports web publishing and iOS/Android builds from a shared project.
- Offers source-code export on paid plans and PostgreSQL database export.
- Provides configurable search metadata and server-side pre-rendering.
Cons
- Free daily build actions and one-time hosting credits limit ongoing usage.
- Separate hosting and AI meters require budgeting beyond the subscription.
- Preview data changes can affect the live database immediately.
- No direct Git repository synchronization; local folder sync is a paid option.
- Exported apps need Floot-managed services replaced before self-hosting.
- Mobile app release still requires developer accounts, testing and store review.
How to Use Floot
- 1Connect an AI assistant
Create a Floot account and follow its connector setup for your chosen assistant. Use a client mode that supports the actions you need.
- 2Describe the first working version
Explain the app’s users, pages and main workflow. Ask the assistant to create a small initial version in Floot.
- 3Add data and integrations
Define the records, user permissions and external services the app needs. Supply API keys through Floot’s secure setup form when requested.
- 4Inspect the preview
Check the screens and main flows, then use selections or annotations to request changes. Ask the assistant to run checks and investigate errors.
- 5Prepare the release
Review access rules, sending-domain setup, metadata and hosting usage. Remember that preview database edits also affect live data.
- 6Publish and maintain
Publish to a Floot subdomain or attach a custom domain on a paid plan. For mobile distribution, create a build, test it and submit it through your own store accounts.
Key Features of Floot
Building
3Connect a supported MCP client to create and update Floot apps from conversation, using the assistant’s own model subscription.
Inspect the running app while it changes. The connector can use selected elements and drawn annotations as context for edits.
The assistant can inspect source files, run type checks and tests, and read runtime logs to investigate problems.
Backend
5Create tables and query app data through the assistant, or browse and edit records in the Data interface. Preview and live apps share the database.
Add email/password sign-in, sessions and password resets, with Google and Microsoft OAuth available through Floot.
Store application assets and user uploads, with public files or private access links. Free accounts have a 100 MB storage cap.
Add transactional email and web or native push notifications. Sending email to customers requires a verified sending domain and a paid plan.
Run recurring backend tasks on paid plans. Immediate background work is available on every plan; delayed tasks require a paid plan.
AI services
1Add text generation, tool use, image generation, embeddings or speech transcription through Floot AI, or connect your own provider key.
Publishing
3Publish the frontend and backend together to a Floot subdomain. Paid plans support custom domains and removal of the Floot badge.
Package a web project for mobile, download an Android APK and project files, and upload builds to connected store testing tracks.
Configure site metadata, robots.txt, sitemaps and a primary domain. Enable pre-rendering to serve page-specific HTML to crawlers.
Measurement
1Track page views and traffic sources using Floot’s built-in analytics. Opening the analytics dashboard requires a paid plan.
Collaboration
1Publish for invited users, or add collaborators to the project on a paid plan. Project edit access and app-user access are separate.
Ownership
1Download source code on a paid plan and export a PostgreSQL dump across plans. Self-hosting requires replacing Floot-managed services.
Integrations
1Connect services for payments, commerce, analytics and automation. Supported examples include Stripe, Shopify, Google Analytics and Zapier.
Use Cases
- Create an MVP with user accounts, data entry and a hosted interface.
- Build a client portal for forms, files and account access.
- Create an internal dashboard for team workflows and records.
- Build a product catalog or storefront connected to payment services.
- Add a chatbot, summarizer or AI-assisted workflow to a web app.
- Prototype a mobile companion app from an existing Floot web project.
Integrations
- MCP client
- ClaudeChatGPTCursorCodex
- Managed authentication
- Google sign-inMicrosoft sign-in
- Payments API
- Stripe
- Commerce API
- Shopify
- Automation
- Zapier
- Analytics
- Google Analytics
- Messaging API
- Twilio
- Database
- External PostgreSQL
Limitations
Build-action limits apply even when you already pay for an AI assistant. Hosting and AI have separate usage charges. Preview and live apps share database data. Code export requires a paid plan, and self-hosting needs service migration. Mobile store release and approval remain the developer’s responsibility.