Reliability and limits
The infrastructure behind your published app, the limits that apply to it, and what happens when you reach one.
Floot is built for production apps. Your site runs on managed AWS infrastructure, with no DevOps work from you. This page covers what every app gets, the limits that apply to it, and what happens when you reach one.
What's included with every app
| Feature | Description |
|---|---|
| Database | Managed Postgres for your app's data |
| Backend | Highly scalable serverless backend on AWS Lambda |
| Authentication | User sign-up, login, and session management |
| Hosting | Globally distributed content delivery built on AWS CloudFront |
| File storage | CDN-backed storage for user uploads and assets |
| Send and receive email from your app — verify your own sending domain to reach real recipients | |
| Realtime | WebSocket-based live updates and presence |
| Jobs | Scheduled cron jobs and background work, up to 10 per project |
| Custom domains | Connect your own domain on a paid plan, once the app is live on its .floot.app subdomain |
| Security | HTTPS everywhere, and secrets kept server-side and never shown to the AI — see Security and data |
Hosting infrastructure
- Automatic scaling based on traffic — no capacity planning
- Global CDN for fast load times worldwide
- SSL certificates (HTTPS) issued and renewed automatically
Uptime and reliability
Floot aims for high availability on all published apps. The longest disruption so far was the October 2025 AWS event, which took out a large part of the internet rather than Floot alone. There have been a small number of brief platform incidents since, each resolved within about half an hour.
A single app can still go offline for reasons that have nothing to do with the platform: an unpaid hosting balance takes it down (see below), and a traffic spike can get it throttled.
Runaway traffic is throttled automatically
If an app's traffic spikes far past its own baseline — usually an infinite loop or a runaway client-side poller rather than real users — Floot caps that app's backend concurrency automatically. The cap lifts on its own: no sooner than half an hour after it went on, and only once traffic has settled back below it. While a cap is in place your app sheds some requests. We are alerted whenever this happens, but no message goes out to you automatically, so if you think your app is being capped, open the support chat.
If you experience downtime or performance issues, reach out via the support chat and we will respond quickly.
What gets metered while you build
Your assistant brings its own model tokens, so building does not spend Floot credits. It spends build actions instead. One action is one tool call your assistant makes on a project, and the count is charged to the account whose Floot login authorized the connector — not to the project owner.
| Plan | Build actions per day | Rolling 7-day cap |
|---|---|---|
| Free | 100 | 400 |
| Pro — $25/mo | 1,000 | None |
| Power — $100/mo | 5,000 | None |
| Older Floot credit plans | 100 | 400 |
Failed and cancelled calls never count. Six housekeeping tools are free and never count either: get_job_status, get_publish_status, list_projects, get_preview_url, cancel_request, and unpublish_app — unpublishing is deliberately free so a capped free account can always free its publish slot.
The 7-day cap is a rolling window: today plus the previous six days, sliding at each UTC midnight. There is no weekly reset moment. The daily cap resets at UTC midnight.
If you subscribe to one of Floot's older credit plans, your usage is metered at the free caps. Those plans buy credits, not build actions — switching to Pro or Power is what raises the ceiling.
What credits are for
Credits are a second, separate meter. They do not convert into build actions, and build actions do not convert into them. Paid plans include a monthly credit quota — 5,000 on Pro, 15,000 on Power — and two things spend them:
- Image generation. Images made with
generate_imageare produced by Floot's own model, so they spend credits in addition to counting as a build action. - AI features inside your own published app. Floot's built-in
@floot/aipackage — chat, embeddings, image generation running in your app for your users — draws on the same credit balance. Connecting your own OpenAI or Anthropic key instead moves that spend to your provider bill.
Both are billed to the project owner's balance, whoever triggered them. See Billing, credits, and plans.
Account limits
| Limit | Free | Paid |
|---|---|---|
| Projects | 5 | Unlimited |
| Published apps | Unlimited | Unlimited |
| File storage | 100 MB | Unlimited, billed past the daily free allowance |
| Single file upload | 100 MB | 100 MB |
| Scheduled jobs per project | 10 | 10 |
| Shortest scheduled-job interval | 5 minutes | 5 minutes |
| Custom domains | Not available | Included |
The project and published-app caps are checked at the moment you would exceed them and are never applied retroactively. If you are already over a cap, you keep everything you have — you just cannot add more until you upgrade or free a slot.
Private files your app serves are handed out as time-limited links: a private download URL can be signed for at most 24 hours.
Verify a sending domain before you launch
Until your workspace has a verified email domain, your app's outbound mail is sent from Floot's shared domain, and any message addressed to someone other than you is redirected to you instead with a notice explaining why. That is useful while testing and wrong for a live app — verify your own domain in your project's Email settings on floot.com before real users sign up.
Custom domains need the app to be published to its .floot.app subdomain first. Ask your AI assistant to add one and it hands you a link: the DNS setup finishes in a wizard in your browser, not in chat, and the link is good for one hour. See How to add a custom domain.
Hosting allowance
| Plan | Monthly hosting allowance |
|---|---|
| Free | None recurring — a one-time $3 credit at signup is all a free account has |
| Pro — $25/mo | $10 of hosting per month |
| Power — $100/mo | $25 of hosting per month |
| Older Floot credit plans | $10 of hosting per month, whatever the credit tier |
Usage past your allowance is billed pay-as-you-go. The baseline is about twice the underlying infrastructure cost; a few units carry more margin than that — realtime connections most of all — so read the hosting dashboard rather than multiplying an AWS price list. Every workspace also gets the first 100 MB per day of file storage and the first 50 MB per day of database storage at no charge before metering starts — see Hosting.
When your hosting allowance runs out
If your hosting balance goes negative and stays there, Floot takes the app offline. How much warning you get depends on your plan:
- Active paid subscription, not cancelling — a 3-day grace window, with warning emails during it
- Free accounts — no grace period
- Cancelled or pending-cancellation subscriptions — no grace period
- Cards that have been failing for more than 14 days — no grace period; inside those 14 days you get the same 3-day window, so there is time to fix the card
A takedown removes infrastructure rather than flipping a switch: custom domains are detached, the .floot.app subdomain is released, and the database is disabled. Your code and your data are kept, so bringing the app back is a re-publish once the balance is positive again, not a toggle.
Monitoring your usage
Track build actions and credits on the plan and usage dashboard, and traffic on the hosting dashboard. Plan changes are browser pages on floot.com — no tool can move you between plans.
You can also just ask while you build. Your assistant can read your hosting and Lambda numbers through the connector and suggest ways to bring them down.