Skip to main content
Manage billing, spending limits, and plan upgrades.

spend-cap get

Show current spend cap and usage.
When the cap is exceeded the command adds a warning that deploys are blocked.

JSON output

Values are in cents. spend_cap_cents is null when no cap is set. Use floo billing usage for the plan, the plan maximum, and the per-app breakdown.

spend-cap set

Set monthly spend cap in dollars. Use 0 to remove the cap (no limit).

Arguments

Examples

JSON output

spend_cap is in cents and is null after set 0. policy is the budget-protection mode floo applies when spend reaches the cap: alerts_only, freeze_new_spend, hard_stop, or off when no cap is set. The CLI has no flag for the mode: setting a cap keeps the org’s current mode, or applies freeze_new_spend when protection was off. Change the mode in the dashboard. See Billing and spend caps for what each mode does.

upgrade

Open Stripe billing portal to upgrade plan.

Flags

Plans

Examples

JSON output

For new subscriptions (opens Stripe checkout):
Omit --plan to open the billing portal for an existing subscription. Plan changes take effect at a billing-period boundary so the period keeps one immutable offer and allowance.

usage

Show current plan, usage, and spend cap with visual progress bar.

Flags

One floo credit equals $1 of metered app usage. Pay as you go includes 0 credits and Team includes 250 credits each month.

Warm instance cost

Web and API services scale to zero when min_instances is omitted on every plan and in every environment, including production. A warm instance bills continuously, even while idle. See Pricing for what the default shapes cost under the current rate policy, and Scaling and availability for the arithmetic and the verification commands. Set min_instances = 1 or higher in floo.app.toml to keep instances warm.

JSON output


contact

Print enterprise contact info.

JSON output


Errors