Skip to main content

​
access mode

Who can reach your app. public is open and accounts requires each user to sign in. Set with access_mode in floo.app.toml. Routes also accept api_key for program access. See App sign-in and App API keys.

​
agent event

A failed deploy or a runtime error that repeats past its threshold. floo bundles the context and POSTs a signed event to your webhook. Read them with floo events list. See Agent webhooks.

​
agent surfaces

The two equal ways an agent drives floo: the floo CLI, where every command supports --json, or the HTTP API at https://api.getfloo.com/v1, starting from agents.md with every operation in openapi.json. Both sign in through the same device flow; the CLI runs it with floo auth login.

​
app

One deployable unit: a repo, a floo.app.toml, and the services it declares. Apps have a dev and a prod environment.

​
approval policy

An optional guardrail, held by floo outside your repo, that requires an org admin to approve certain changes before they apply: removing a managed service or loosening an app’s access. Off by default, so those changes apply on deploy. A pull request cannot weaken it. Contact support to set one up.

​
attachment

The declaration that a service receives a managed service’s credentials, written as env.managed on that service. When no service declares one, credentials are injected into every service; once any service does, services without one receive none.

​
auto top-up

A prepaid credit refill charged to the org’s saved card when its balance falls below $5. It uses the last credit purchase amount, bounded by the remaining monthly limit. Org admins turn it off or on with floo billing auto-top-up off or floo billing auto-top-up on, or on the dashboard Billing page. See Auto top-up.

​
credit

The unit floo bills metered usage in. Plans, rates, and included credits are on getfloo.com/pricing.

​
deploy

One run of the pipeline for one environment: build the commit’s image, run migrate_command, roll the new revision out, and shift traffic to it. Every push to the connected branch creates a deploy to dev; floo deploys list shows them, and any earlier one is a rollback target. A release is a deploy to prod; see release.

​
edge

The policy layer that runs before traffic reaches your container: route matching, managed auth, and access mode. Inspect it with floo edge routes list.

​
environment

dev, prod, or a preview. Every push deploys to dev, and a release publishes to prod. A preview environment is a short-lived copy for one pull request. Managed data is isolated between them.

​
floo.app.toml

The repo-backed declaration of your app: services, routes, workers, cron, and managed-service intent. It is committed to git, so every change is reviewable in a pull request. See Config file spec.

​
floo.service.toml

An optional per-service config file for the delegated layout, where each service’s settings live beside its code instead of inline in floo.app.toml. A service is inline or delegated, never both. See Config file spec.

​
gateway

floo’s inbound proxy, and the only public path to your container. Your app trusts the identity headers it sets. See Networking and egress.

​
managed service

A stateful primitive floo runs for you: Postgres, Redis, or Storage. Declared with [managed.<name>], provisioned on deploy, and outlives any single deploy. Redis is cache-only and has no backup. See Managed services.

​
org

The organization that owns apps, members, and billing. Members hold an admin, member, or viewer role, and the spend cap is set per org. See Team, roles, and API keys.

​
preflight

Local validation of floo.app.toml and your source. Runs without an account and without deploying. floo preflight.

​
preview environment

A branch-scoped, production-shaped sandbox created for a pull request, with its own isolated managed resources. Torn down when the pull request closes. See Preview environments.

​
promote

Publish a dev-validated build to prod. For your own GitHub repo, publish a GitHub release. For a floo-hosted project or an app with no repo, run floo releases promote. See Environments for image reuse and rebuild rules.

​
release

A prod deploy from a dev-validated commit, recorded with its tag, commit, promoter, and image digest. floo releases list shows them. See Releases.

​
service

A process floo runs from your repo. A web service takes inbound traffic at /, an api service takes it at /api, and a worker runs background work with no inbound traffic. Cron jobs are separate: they run a command on a schedule inside a service’s image.

​
shape

The CPU and memory an instance of a service runs with. The default HTTP shape is 1 vCPU / 512 MiB. Override it with cpu and memory in [resources] or on a service. See Scaling and availability.

​
spend cap

An org-wide dollar limit on metered usage. What happens at the cap depends on the org’s policy: alerts_only emails admins and blocks nothing, freeze_new_spend blocks new deploys and managed services, and hard_stop also scales running services to zero. Set the amount with floo billing spend-cap set and the policy on the dashboard Billing page. Pay as you go always requires a positive hard_stop limit and a funded balance. See Billing and spend caps.