previews

floo previews manages isolated preview sandboxes for pushed GitHub branches: a real deploy URL before a pull request exists, plus inspection and cleanup of existing previews. Previews created here follow the same isolation contract as pull request previews. Source comes from the app’s connected GitHub repository; local uncommitted files are not uploaded.

up

Create or refresh a preview sandbox from a remote branch.

git push origin feat/foo
floo previews up --app my-app --branch feat/foo
floo previews up --app my-app --branch feat/foo --wait --json

--wait polls the returned deploy for up to 10 minutes and exits non-zero if it fails or times out.

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--branch`	required	Remote GitHub branch to deploy into the preview sandbox
`--runtime`	`auto`	Runtime hint for the deploy request
`--commit-sha`	none	Exact remote commit SHA to deploy
`--ref`	none	Remote Git ref to record on the deploy
`--wait`	off	Wait until the preview deploy finishes

JSON output

{
  "success": true,
  "data": {
    "app": {
      "id": "app_123",
      "name": "my-app"
    },
    "preview": {
      "slug": "feat-foo-abcde",
      "source_branch": "feat/foo"
    },
    "source_branch": "feat/foo",
    "deploy_id": "deploy_123",
    "status": "LIVE",
    "url": "https://my-app-preview-feat-foo-abcde.getfloo.app",
    "expires_at": "2026-06-30T18:30:00Z",
    "database_branches": [],
    "dev_prod_untouched": true
  }
}

Every preview command except logs --follow emits one JSON object.

list

List active preview sandboxes for an app.

floo previews list --app my-app
floo previews list --app my-app --json

status

Show one preview sandbox.

floo previews status --app my-app feat/foo
floo previews status --app my-app https://my-app-preview-feat-foo-abcde.getfloo.app --json

The preview identifier is an exact slug, preview URL, source branch, or #123 when that PR number matches exactly one preview. If it is ambiguous, pass the exact slug from floo previews list.

logs

Read logs for the latest deploy associated with a preview.

floo previews logs --app my-app feat/foo
floo previews logs --app my-app feat/foo --follow --tail 200

Flags

Flag	Default	Description
`--follow`, `-f`	off	Stream deploy logs while the preview deploy is active
`--tail`	`100`	Number of runtime log lines to fetch when not streaming

delete

Delete a preview sandbox and its preview-owned resources.

floo previews delete --app my-app feat/foo
floo previews delete --app my-app feat/foo --yes --json

Delete tears down preview-owned services, managed resources, gateway routes, and env vars. Dev and prod resources are untouched.

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--yes`	off	Skip the confirmation prompt

resources list

List the preview-owned Postgres, Redis, and Storage branches backing one preview.

floo previews resources list feat/foo --app my-app
floo previews resources list feat-foo-abcde --app my-app --json

  Resource     Type   Source  Status  Hydration  Provider ID  Expires  Reset
  redis:cache  redis  dev     ready   clone-dev  db_123       -        eligible

Provider ID is the database ID for Redis and the bucket name for Storage; Postgres branches show -.

JSON output

{
  "success": true,
  "data": {
    "app": { "id": "app_123", "name": "my-app" },
    "preview": { "slug": "feat-foo-abcde", "source_branch": "feat/foo" },
    "managed_resource_branches": [
      {
        "id": "b1c2d3e4-...",
        "resource_type": "redis",
        "name": "cache",
        "resource_key": "redis:cache",
        "source_env": "dev",
        "preview_slug": "feat-foo-abcde",
        "resource_status": "ready",
        "hydration_mode": "clone-dev",
        "database_id": "db_123",
        "expires_at": null,
        "reset_eligible": true,
        "reset_blocked_reason": null
      }
    ],
    "total": 1,
    "dev_prod_untouched": true
  }
}

The response includes all managed resource types and never includes plaintext credentials. Select one Postgres branch with --resource postgres:default on resources show.

resources show

Show one preview managed-resource branch by its type:name key.

floo previews resources show feat/foo --app my-app --resource redis:cache
floo previews resources show feat/foo --app my-app --resource storage:uploads --json

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--resource`	required	Resource key shaped `type:name`, such as `postgres:default` or `redis:cache`

JSON output carries the same app, preview, and dev_prod_untouched fields as list, with the branch under managed_resource_branch.

resources reset

Clear a preview Redis database or the live objects in a preview Storage bucket, then reapply the preview data policy. The resource identity and injected credentials remain stable. Dev and prod resources are untouched.

floo previews resources reset feat/foo --app my-app --resource redis:cache --preflight --json

Reset is tier 2 because it destroys preview-only data: interactive mode prompts y/N, and non-interactive callers must pass --yes. Providers that do not support reset fail closed with the API’s named blocker, which list shows in the Reset column and reset_blocked_reason field. Postgres preview branches are not reset-eligible.

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--resource`	required	Resource key shaped `type:name`
`--yes`	off	Skip the confirmation prompt
`--preflight`	off	Preview the reset without applying it

JSON output

{
  "success": true,
  "data": {
    "app": { "id": "app_123", "name": "my-app" },
    "preview": { "slug": "feat-foo-abcde", "source_branch": "feat/foo" },
    "managed_resource_branch": { "resource_key": "redis:cache", "resource_status": "ready" },
    "destructive": true,
    "data_loss": true,
    "tier": 2,
    "scope": "preview",
    "dev_prod_untouched": true
  }
}

Failure handling

Symptom	Meaning	What to do
The preview deploy uses an old commit	The branch was not pushed before `up` ran	Push the branch or pass a remote commit/ref
`PREVIEW_MANAGED_SERVICE_ISOLATION_UNAVAILABLE`	floo could not provision preview-owned managed resources	Fix the managed-service state and retry
Identifier is ambiguous	More than one preview matched the branch, URL, or PR identifier	Use the exact slug from `floo previews list`
`--wait` exits non-zero	The returned deploy failed or timed out	Inspect `floo previews status ... --json` and `floo previews logs ...`

CLI

Config

API

up

Flags

JSON output

list

status

logs

Flags

delete

Flags

resources list

JSON output

resources show

Flags

resources reset

Flags

JSON output

Failure handling

​up

​Flags

​JSON output

​list

​status

​logs

​Flags

​delete

​Flags

​resources list

​JSON output

​resources show

​Flags

​resources reset

​Flags

​JSON output

​Failure handling

​Related

up

Flags

JSON output

list

status

logs

Flags

delete

Flags

resources list

JSON output

resources show

Flags

resources reset

Flags

JSON output

Failure handling

Related