Skip to main content
Floo distinguishes between code you deploy and infrastructure the platform manages for you.

​
Deployable vs Managed

  • Deployable services are your web, api, and worker services.
  • Managed services are platform-owned backing resources such as Postgres, Redis, and Cloud Storage.
Managed services are not public ingress targets and do not replace the need for at least one deployable service in a multi-service app.

​
What Ships Today

The backend and dashboard codebase ship managed-service support for:
ServiceTypical env varsNotes
PostgresDATABASE_URLstandard connection string
RedisREDIS_URLstandard Redis URL
Cloud StorageGCS_BUCKET, GOOGLE_CLOUD_PROJECTbucket/project values for storage SDKs

​
Public CLI Surface Today

The public CLI is strongest on consuming managed-service outputs, not managing the full lifecycle. Use the CLI to:
  • read injected env vars with floo env get
  • list masked env vars with floo env list
  • deploy and debug apps that depend on those values
The current CLI reference does not expose a first-class managed-services command. Keep that distinction clear when documenting app setup.

​
Managed Entries in Config

The current CLI config parser can distinguish managed Postgres and Redis entries from deployable services inside floo.app.toml: 
[app]
name = "full-stack"

[services.web]
type = "web"
path = "./web"
port = 3000

[services.api]
type = "api"
path = "./api"
port = 8080

[services.db]
type = "postgres"

[services.cache]
type = "redis"
Treat those as platform-managed dependencies, not as replacements for deployable services. Your application code should still consume them through env vars like DATABASE_URL and REDIS_URL, and the public CLI docs should stay focused on that env-driven workflow unless a dedicated managed-service command surface ships.

​
Storage Caveat

The shipped backend exposes managed Cloud Storage with GCS_BUCKET and GOOGLE_CLOUD_PROJECT. The current public CLI docs focus on consuming those env vars once storage is provisioned, not on a separate CLI provisioning workflow.
  1. Define and deploy your app services.
  2. Treat managed services as injected dependencies.
  3. Read connection details from env vars, not hard-coded hostnames.
  4. Use logs and deploy history to debug dependency issues.

Env Vars

See how injected values show up in the CLI.

Cloud Storage

See the corrected storage env vars and consumption patterns.