Skip to main content
Floo is easiest to understand if you keep four objects straight: apps, services, deploys, and releases.

​
Apps

An app is the top-level unit in Floo. It owns:
  • your default live URL
  • GitHub connection state
  • deploy history
  • app-level access mode
  • service graph, managed services, domains, env vars, and billing usage
When you run floo apps list or open the Apps page in the dashboard, you are looking at apps.

​
Services

A service is one runnable component inside an app. Floo has two service categories:
  • Deployable services:
    • web for browser-facing HTTP traffic
    • api for HTTP backends
    • worker for background jobs with no public ingress
  • Managed services:
    • Postgres for relational data
    • Redis for cache and queue workloads
    • Storage for uploads and generated assets
Deployable services are the units built and rolled out from your repo. Managed services are platform-owned backing resources declared in floo.app.toml.

​
Deploys

A deploy is a specific build of your app. Deploys are immutable snapshots of:
  • the app configuration Floo resolved
  • the detected runtime/framework
  • the services included in that rollout
  • the resulting live URL and status
Use deploys when you care about build output, rollout state, or rollback targets: 
floo deploy
floo deploy list --app my-app
floo deploy logs <deploy-id> --app my-app
floo deploy watch --app my-app

​
Releases

A release is a promoted label on top of a deploy. Releases are useful when you want a human-friendly promotion history instead of only deploy IDs. Use releases when you want to:
  • mark a live deploy with a versioned tag
  • promote the current live state to production history
  • inspect named release metadata in the dashboard or CLI
floo releases list --app my-app
floo releases show <release-id> --app my-app
floo releases promote --app my-app

​
How They Fit Together

ObjectWhat it answersMain surfaces
App”What system am I operating on?”floo apps, Apps page
Service”Which component runs this code?“config files, app detail view, floo services
Deploy”What rollout happened?”floo deploy*, build logs, deploy history
Release”What version did we promote?”Releases tab, floo releases*

​
Typical Flow

  1. Create config for an app.
  2. Define one or more services inside it.
  3. Deploy from a connected GitHub repo.
  4. Watch deploy history as changes ship.
  5. Promote a release or roll back to a previous deploy when needed.

Configuration

See how Floo picks config files and resolves services.

Releases and Rollbacks

Learn when to use a release versus a rollback.