A backend your AI can set up for you.

Floot is a backend for AI-built apps that gives your coding agent a Postgres database, logins, storage and email through one MCP server, so you don't wire up five services yourself.

What you get

If you build with Codex or Cursor, the code comes fast and the backend is where you get stuck: which database, which auth provider, where the API runs, how email goes out. Floot puts those pieces in one platform with one MCP server, so your agent can add them as it builds.

  1. 01

    Postgres per app

    Each project can have its own Postgres database. The agent creates tables and runs migrations; you can download the whole database on any plan.

  2. 02

    Auth without a separate provider

    Email, Google and Microsoft sign-in, sessions and roles live in the app itself.

  3. 03

    API endpoints and jobs

    Server endpoints, scheduled jobs and background tasks run on Floot, including work that continues with nobody online.

  4. 04

    Storage, email and push

    File uploads, sending and receiving email, and web and phone push notifications are built-in services.

  5. 05

    Payments

    Floot Payments handles checkout and subscriptions, paid out through Stripe.

  6. 06

    One MCP server

    Codex, Cursor, Claude Code, Claude and ChatGPT all reach the same tools, so you can switch agents without moving the app.

See how Floot compares

What mattersFlootSeparate database, auth and hosting services
Accounts to set upOneOne per service
Agent can create tables, logins and deploysYes, as MCP tool callsOnly through each service's own tools
Email, push, storage, paymentsBuilt inSeparate products
Starting price$0/moVaries per service

Read: The simplest backend and hosting for apps you build with Codex or Cursor (2026) · Best backend-as-a-service platforms (2026) · Best MCP servers for building and deploying apps (2026) · Floot vs Supabase: which backend for an AI-built app? (2026)

A backend for every stage of your app

First prototype

Get a database and sign-in on day one instead of mocking data.

First paying users

Add Floot Payments subscriptions, email receipts and a custom domain.

Growing app

Scheduled jobs, background tasks, push notifications and native phone apps.

Everything your app needs, built in

Postgres database
Download the whole database on any plan.
Sign-up and login
Email, Google and Microsoft sign-in for your own users.
Hosting and custom domains
Publishing is free on every plan; Pro includes $10 of hosting a month.
Email in and out
Send and receive email from the app.
Push notifications
On the web and on iPhone and Android.
Scheduled jobs
Work that runs with nobody online.
Payments
Checkout and subscriptions through Floot Payments, paid out via Stripe.
Native phone apps
Built and submitted to the App Store and Google Play, no Mac needed.
Works from your AI
ChatGPT, Claude, Claude Code, Codex and Cursor, through Floot's MCP server.
7-day database restore
Paid plans can put the database back to any moment in the last 7 days.

From people building on Floot

“I think about Floot as an outsourced developer. It has the guardrails, and it doesn’t lie about what can and can’t be done.”

Runs a 12-person candle business, Illinois

“Now I don’t know why I need developers. Getting it right in the first run saves a lot of time and money.”

Consultant to trades businesses, building a SaaS product

Free to start, monthly plans when you grow

Free

$0/mo

Trying Floot out and exploring ideas

  • 100 building actions a day
  • $3 one-time hosting allowance
  • 2 mobile app builds a month

Pro

$25/mo

Building and publishing on the web every day

  • 1,000 building actions a day
  • $10 of hosting included a month
  • 5,000 AI credits a month
  • Custom domains + 1 free domain
  • 12 mobile app builds a month

Power

$100/mo

High-volume building and unlimited app builds

  • 5,000 building actions a day
  • $25 of hosting included a month
  • 15,000 AI credits a month
  • Unlimited mobile app builds

An action is any edit, read or test your AI assistant runs; failed actions never count, and limits reset daily. Publishing to the app stores needs your own Apple and Google developer accounts.

Frequent questions

Is there a service that handles the backend and hosting for apps I build with Codex?

Floot does: it gives the app a Postgres database, logins, endpoints, storage, email and hosting, and Codex drives it through Floot's MCP server.

Can I use Cursor with Floot?

Yes. Add Floot as an MCP server in Cursor and ask it to build on Floot.

Do I need separate accounts for a database, auth and hosting?

No. They are all part of the Floot project.

Can I get my data out?

Yes. Database export is available on every plan; paid plans can also download the code.

Articles

The simplest backend and hosting for apps you build with Codex or Cursor (2026)What a web app built with Codex or Cursor needs on the backend, the main ways to get a database, login and hosting, what each costs, and how to let the agent set it all up through MCP.What is a backend? A plain-English guide for people building with AIWhat the backend of an app actually does, the six jobs it covers, how a single click travels through it, and how to describe one clearly to ChatGPT, Claude, Codex or Cursor.Row-level security explained: keeping each user’s data privateHow row-level security works in Postgres, how to write policies that keep each user’s rows private, how Supabase and Firebase apply the same idea, and the mistakes that leak data.Sign-in options compared: email codes, magic links, passwords, GoogleHow email codes, magic links, passwords and Sign in with Google work, what current NIST and OWASP guidance says about each, and which combination suits a new app.Postgres vs Firebase vs MongoDB for a first appHow Postgres, Firebase’s Firestore and MongoDB store data, what the same small app looks like in each, how their free tiers and billing work, and which to pick for a first project.What is an MCP server, and how coding agents use themWhat the Model Context Protocol is, what an MCP server exposes, how Claude Code, Cursor and Codex connect to one, what a tool call looks like on the wire, and how to use them safely.Webhooks explained: how apps talk to Stripe and other servicesWhat a webhook is, how Stripe and GitHub deliver them, how to verify signatures, handle retries and duplicates, and build a payment webhook handler that doesn’t lose or double-count orders.Background jobs and cron: running work when nobody is onlineWhat background jobs and cron schedules are, how to read a cron expression, how Vercel, GitHub Actions and Supabase run scheduled work, and how to write jobs that survive retries, overlaps and time zones.Best backend-as-a-service platforms (2026)Seven backend-as-a-service platforms compared for people building apps with AI tools: what each does well, what to watch, and what it costs according to its own pricing page.Best MCP servers for building and deploying apps (2026)Eight official MCP servers that let ChatGPT, Claude, Claude Code, Codex and Cursor build, deploy and run real apps, with what each does well, what to watch, and what the underlying service costs.Floot vs Supabase: which backend for an AI-built app? (2026)How Floot and Supabase differ in what they include, how AI agents use them, what they cost and how portable they are, with honest advice on when to pick each.

Build yours this week.