Start here
Browse the docs
Start here
What Floot builds for you, how to connect it to the AI assistant you already use, and where to watch your project come together.
- How Floot worksFloot 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.
- Build from Claude & ChatGPTConnect Floot to Claude, ChatGPT, Codex, Cursor, or any other MCP client and build full-stack apps without leaving the chat.
- Connect any MCP clientAdd Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers — server URL, transport, and OAuth.
- Your project viewThe live preview page your assistant hands you — what is on screen, how the shareable link works, and what you can do without leaving it.
Building with your AI
The connector in depth — everything your assistant can do on your projects, how that work is metered, and what to try when it misbehaves.
- What your AI can doThe full capability list for the Floot connector — what your assistant does on its own, and the few things you finish in the browser.
- Build actionsHow Floot meters connector usage: one build action per tool call, what is never counted, and the daily limit per plan.
- Testing your appHow your project's tests run, what they can reach, and how to give code under test dummy secrets, fake responses and results from Floot services.
- Examples: every state of your appSee the loading, empty, error and edge-case states of a page side by side while you build, without breaking anything to get there.
- Connector troubleshootingFixes for the things that go wrong connecting Floot to Claude, ChatGPT, or another MCP client — and the behaviour that only looks broken.
Best practices
How to describe what you want to your assistant so the first attempt is close.
Services & integrations
The database, auth, storage, and email Floot provisions for every project — and how to wire in outside services.
- What's built inThe services every Floot project comes with — database, auth, AI, storage, email, realtime, and jobs.
- Sign-in for your app's usersHow login works in the app you build: email and password, password reset, your own first admin account, Google and Microsoft sign-in, and bringing your own.
- PaymentsTake payments in every app you build through one Stripe account, with zero code setup: test in the preview for free, then connect your Stripe account to take real money.
- ShippingCheck addresses, quote rates, buy labels and track parcels through Shippo: test in the preview for free, then connect your own Shippo account to buy real labels.
- Floot AI in your appThe AI service your app calls for its own users: what it does, the models, how it spends credits, how to switch it off, and using your own provider key.
- Scheduled jobs and background tasksRunning work outside a request: background tasks, timers, and scheduled jobs — their limits, where to see them, and when they run.
- RealtimeKeep pages up to date the moment data changes, and show who's here, who's typing and where their cursor is, without refreshing.
- EmailSending and receiving email from your app: verifying a domain, daily limits, bulk sends, bounces, and what it costs.
- Visitor analyticsWhat Floot's built-in tracker records, where to see it, and how it handles cookie consent.
- Connecting external servicesHow Floot apps talk to third-party APIs, webhooks, and email providers.
Platform
The infrastructure under your app, and how your data is handled.
- Reliability and limitsThe infrastructure behind your published app, the limits that apply to it, and what happens when you reach one.
- Daily hosting limitA cap on what your published apps can spend on hosting in one day, so a bug or a traffic spike pauses your apps instead of running up your bill.
- Your databaseThe Postgres database built into your Floot project: how you reach it, when it sleeps, how connections work, and how export, import, backups and restores work.
- Backend runtime contractWhat your app's backend can rely on at runtime: the database role, transactions, timeouts and size limits, each marked supported, current behavior or not provided.
- Security and dataHow Floot handles your code, your data, and your users' data — including what your own AI assistant can see.
- Security headers and embeddingChoose who can show your app in an iframe, set your own Content Security Policy, and change the Referrer-Policy of your published app.
- Fixed outbound IPSend your backend's calls from fixed IP addresses, for banks, payment processors and partner APIs that only accept allowlisted IPs.
Projects & domains
Share your work, publish it privately, hand it off, or take it somewhere else entirely.
- Publishing your appWhat a publish ships, why the live site can be behind the preview, changing the floot.app address, unpublishing, the Made with Floot badge, a loading screen while a page opens, and what to do when a publish is stuck.
- Sharing your projectsPreview links, collaborators, development previews, private apps, handing a project to another account, and making a project public.
- Publish privatelyPublish your app so only the people you invite can open it — for internal tools, client previews, and betas.
- Duplicate a projectCopy a project, choose between sharing and copying its database, and see what a copy gets.
- Connected appsLet one of your Floot apps use another's features and data — no API keys, no glue code.
- How to add a custom domainPoint your own domain at your Floot app, step by step, including the DNS gotchas.
- Custom domain troubleshootingFix a custom domain by symptom: verification that never finishes, records at the wrong DNS provider, CAA records, a root domain that does not load, and what happens to domains when a plan lapses.
- Search engines and SEO settingsThe SEO tab: site name and description, robots.txt and the sitemap, pre-rendering, per-page meta tags, noindex, and the primary domain and redirects.
- Self-hostingExport your code and database and run your Floot app on your own infrastructure.
Mobile apps
Turn your project into apps people install on their phones.
- Creating mobile apps from your websiteTurn a Floot web app into real iOS and Android apps — installable on a phone, and submittable to the App Store and Google Play.
- Publish to TestFlight and Google PlayConnect your Apple or Google Play account once, and Floot uploads every app build to the store's testing track.
- Connecting Apple and Google: troubleshootingWhat each message means when connecting your Apple or Google Play account or uploading a build, and how to get past it.
- Native app featuresPush, permissions, the share sheet, background work, the status bar, and iPhone-only builds — what to ask your assistant for.
- Native plugins and native settingsWhich Capacitor plugins work in a Floot app, what a plugin of your own needs, the native config files your project carries, and what the build does not support.
- Add your app to a home screen or desktopInstall a Floot app on an iPhone or Android home screen, or on a Windows or Mac computer, straight from the browser — no app store, no installer, no download.
- Installing your iOS appRun your Floot app on the iOS Simulator or a real iPhone, and publish it to the App Store.
- Installing your Android appInstall your Floot app on an Android device, and publish it to the Google Play Store.
FAQs
Short answers to the questions we get most.
- Billing, credits, and plansThe two meters — build actions and credits — what rolls over, and what each plan includes.
- Managing your subscriptionHow to upgrade, downgrade, switch between monthly and yearly billing, cancel and undo a cancellation, and where your card, invoices and tax details are.
- HostingHow hosting is paid for, how to top up, what happens when the balance runs out and how to come back, and how to take a site down.
- Code, data, and exportsGetting your code and database out of Floot, and how to bring an existing project in.
- APIs, scraping, and mobileConnecting third-party APIs, scraping without getting blocked, and what it takes to ship a native app.
- Troubleshooting and supportWhat to try when the AI loops on the same error, when a publish or the preview gets stuck, where the logs are, and what to send support.
- Your accountSigning in, changing your email, two-factor authentication, paying on the right account, signing out other devices, limiting or disconnecting an assistant, and deleting a project or your account.
- Missing projects and accounts"Project not found" almost always means a different Floot account. How to find which account owns a project, and how to connect your assistant to it.
- Community and linksWhere to find the Floot community, updates, and support.
Can't find what you need?
Click the chat button in the bottom-right of floot.com to talk to us, ask the community on Discord, or email hello@floot.com. We're here to help.