One platform for the internal apps your agent builds
Your agent builds the app. floo hosts it and gives it invite-only sign-in, Postgres, cron jobs, storage, and API keys for agents. You write no auth code, keep one config file in git, and pay one bill.
The same app on floo and on Vercel + Supabase
An inventory tool for a 3-person team: invite-only sign-in, a Postgres table, a daily low-stock job, and an API key for an agent. Each column follows that vendor's own docs.
| Vercel + Supabase | floo | |
|---|---|---|
| Vendors | 2, or 3 with an SMTP provider for invites | 1 |
| Sign-in code | 11 template files, about 448 lines | None. Your code reads the signed-in user from a request header. |
| Invite-only access | Disable sign-ups, edit the invite email, write an invite script that holds the secret key | access_mode = "accounts", then floo apps invite <email> |
| Database | Supabase Postgres, with row-level security on every exposed table | Managed Postgres from one config section. DATABASE_URL is injected. |
| Scheduled jobs | Supabase Cron (SQL), or Vercel Cron plus a route and a CRON_SECRET | [cron.<name>] in config, run in the app's own container |
| API key for an agent | A secret key with full project access that bypasses row-level security, or custom code | A key per agent, scoped to the routes you declare, rate-limited, revocable, with request history |
| Config | Two dashboards | floo.app.toml in your repo |
| Cheapest commercial plans that never pause | About $45 a month (Vercel Pro + Supabase Pro) | $0 monthly commitment. You pay for usage. |
Sources and the full trace are in floo vs Vercel + Supabase for internal tools.
The whole app in one file
A team-only app with a database and a daily job. Your agent writes this file, and every push deploys it to a dev URL. A GitHub release sends it to production.
[app]
name = "stock-room"
access_mode = "accounts"
[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"
[managed.default]
type = "postgres"
[cron.low-stock]
schedule = "0 7 * * *"
command = "node scripts/low-stock.js"
service = "web"Apps running on floo
- Inventory for a Lego business
Replaced about $10k a year of legacy inventory software with an app its agent built.
- A live dashboard for a financial desk
Daily Claude jobs costing about $10 a day became software that runs for under $1 a day.
- Our own CRM
Reads product data, runs an hourly job, and sends the next actions to Slack. No auth code.
When to pick something else
- A public, frontend-heavy site. Vercel's global CDN is built for it, and floo runs in one region.
- You need Supabase's realtime, its auth providers for customer sign-up, or a scheduled SQL statement with no app code.
- The app must reach a private VPC, VPN, or on-prem network. Hosts on a Tailscale tailnet work today; other private networks are planned.
Guides
Questions
- Is floo a replacement for Vercel and Supabase?
- For internal apps, yes: floo hosts the app and gives it sign-in, Postgres, cron jobs, storage, and agent API keys from one config file. For a public, frontend-heavy site that needs a global CDN, Vercel is still the better host.
- Do I need to write auth code?
- No. access_mode = "accounts" puts floo's hosted sign-in in front of the app. Your code reads the signed-in user from request headers such as X-Floo-User-Email.
- Can an agent use the app too?
- Yes. Declare which routes accept machine access, then create a key for each agent with a scope and a rate limit. Revoking it signs no one out.
- What does it cost?
- Pay as you go has no monthly commitment; you buy credits and usage draws them down. Sign-in for people and agents is included. Plan details are on the pricing page.
- Which agents work with floo?
- Claude, Codex, Muse, Grok, and any agent that can run a CLI or make HTTP requests.