Plans and limits - floo

Every plan runs the same platform with the same runtime limits. Plans differ in how you pay, how many people can build, and a few team features. Prices are on getfloo.com/pricing.

Plans

	Pay as you go	Team	Enterprise
How you pay	Prepaid credits; usage draws them down	$250 a month, including 250 floo credits	Contract
Builder seats	5	50	Unlimited
App users (people who sign in to your apps)	Unlimited	Unlimited	Unlimited
Custom domains and app sign-in	Yes	Yes	Yes
IP allow and deny rules (`[edge]`)	No	Yes	Yes
Full audit log and CSV export	No	Yes	Yes
SSO for floo sign-in	No	No	Yes
Support	Standard	Priority	Dedicated, with an SLA

A new org needs a plan before it can create apps or deploy; run floo billing upgrade to pick one. See Billing and spend caps for how usage is charged and capped, and Team, roles, and API keys for seats.

Platform limits

These apply on every plan.

Limit	Value	Where it is set
CPU per instance	Up to 4	`cpu`
Memory per instance	Up to 16Gi	`memory`
Instances per web or API service	Up to 100 (default 3)	`max_instances`
Concurrent requests per instance	80	Fixed
Request body	10 MB by default, up to 100 MB	`max_request_body_mb`
Deploy duration	10 minutes, then `DEPLOY_TIMEOUT`	Fixed
Cron job run time	Up to 1500 seconds (default 300)	`timeout`
Storage services per app	10	Storage
Consumers per app / keys per consumer	50 / 100	App API keys
Runtime log retention	7 days	Logs
App API key request history	About 7 days	App API keys

Next steps

Billing and spend caps

How usage is charged, and what happens at a spend cap.

Scaling and availability

Instances, warm services, and cold starts.