What's built in
The services every Floot project comes with — database, auth, AI, storage, email, realtime, and jobs.
A lot of what you would normally wire up yourself is already part of every Floot project. Ask your AI assistant for the feature and the built-in service gets wired in for you. No accounts, no API keys, no setup.
| Service | What it gives you |
|---|---|
| Floot Database | A managed Postgres database. Your assistant reads the schema and runs SQL against it directly. You can also browse tables yourself in the Data tab of your project on floot.com, and export the whole database as a SQL dump from there on any plan. Importing a SQL dump needs a paid plan. |
| Authentication | Sign-up, login, and sessions out of the box, plus one-click Sign in with Google and Sign in with Microsoft — Floot brokers both, so there is no OAuth app to register. Other providers, including Apple, GitHub, LinkedIn, and Slack, work too, using your own OAuth credentials. See Sign-in for your app's users. |
| Floot AI | Text generation with tool calling and web search, image generation and editing, embeddings, and speech-to-text transcription, with no provider account. AI features running inside your published app spend Floot credits, billed to the project owner — or bring your own provider key instead and pay that provider directly. See Floot AI in your app. |
| Floot Storage | File uploads and downloads for your users — documents, photos, contracts — served from Floot's CDN. A free account gets 100 MB across all its projects; paid plans have no cap, and storage past the first 100 MB per project per day is metered as hosting usage. A single file can be at most 100 MB on any plan. |
| Send email from your app, one at a time or in bulk, and receive email into it, without signing up for a mail provider. Verify your own sending domain before you go live — see the note below and Email. | |
| Google and Microsoft accounts | Let your users connect their own Gmail, Google Calendar, and Google Drive — or Outlook mail, calendar, and OneDrive — so your app can read and act on them, with no OAuth app of your own to register. Google Drive access covers the files your app created or the user picked; OneDrive access covers all of the user's files. |
| Payments | Checkout, carts, subscriptions, coupons and refunds through Stripe, with no Stripe keys or webhooks to set up. Test in the preview without a Stripe account; to take real money, connect your own Stripe account and publish on Pro or Power. Floot keeps 1% of each live payment on Pro and 0% on Power. See Payments. |
| Floot Realtime | Live updates over WebSockets — presence, collaborative screens, dashboards that move on their own. |
| Scheduled jobs | Run backend work on a cron schedule: nightly cleanups, weekly digests, morning reports. Schedules run in your published app while the project owner is on a paid plan; on a free plan they are saved but do not run. |
| Background jobs | Kick off work that outlives the request. Immediate background tasks and fan-out work on every plan; delayed jobs and schedules your app creates at runtime need the project owner on a paid plan. See Scheduled jobs and background tasks. |
| Push notifications | Send notifications to your users' phones and browsers. Native push in the iOS and Android apps is set up when you connect an app store — see Native app features. |
| Analytics | Built-in visitor tracking: page views, traffic sources, and trends, with no cookies. Opening the analytics dashboard requires a paid plan. See Visitor analytics. |
| Hosting & CDN | Globally distributed hosting with automatic SSL and scaling. Running a published app is metered as hosting usage: a free account has a one-time $3 hosting credit from signup and no recurring allowance, while paid plans include a monthly one. See Reliability and limits. |
Verify a sending domain before you go live
Until your workspace has a verified sending domain, any message your app addresses to someone other than you is delivered to you instead — the subject is prefixed with the intended recipient, and a notice is added to the body explaining why. Nothing errors and nothing bounces, so this is easy to miss: you test a signup email on yourself, it arrives, and no customer ever receives one. Add and verify your domain in the Email tab of your project on floot.com — open the project from your dashboard, or from the preview link your assistant gave you. Adding an email domain requires a paid plan.
You don't have to choose these by name
Describe the outcome — "let users upload a profile photo", "email me when someone books" — and the right service gets reached for.
Agents and chatbots
Your app can have conversational agents of its own: a support bot, an assistant that answers from your data, or a background agent that works on a schedule. Conversation history, tool calling, memory, and streaming responses come with the built-in AI service — describe what the agent should be able to do and it gets wired in. Its usage is billed like any other Floot AI usage: credits from the project owner, unless you connect your own provider key.
Bringing your own services
Built-in does not mean locked in. If you already use Stripe, Twilio, Resend, Mapbox, an external Postgres database, or your own AI provider key, Floot connects to those instead. Browse the full directory on the integrations page.