Skip to main content
Use this page when you are evaluating Floo as a deployment platform for your stack.

​
What Floo Handles Well

Floo is built for Dockerfile-based deploys. The CLI can still detect common runtimes and frameworks during floo init, but the deployable artifact is the Docker image you define.
App shapeTypical service typeNotes
Next.jswebbrowser-facing app on port 3000
Vite / Reactwebstatic frontend served from a Docker image
Expressapi or webNode.js HTTP service
FastAPIapiPython HTTP API on port 8000
Flask / Djangoapi or webPython web apps with a Dockerfile
Go serviceapi or workerbinary built from go.mod project
Static sitewebsimple asset-serving image
Generic Docker appweb, api, or workeranything you can package into a Dockerfile

​
Deployable Service Types

  • web for browser-facing HTTP traffic
  • api for backend HTTP services
  • worker for background processes with no public ingress
If your app needs a database, cache, or storage bucket, combine those deployable services with Floo-managed Postgres, Redis, and Storage.

​
First Tutorial Set

Deploy Next.js on Floo

Dockerfile, config, and first deploy for a Next.js app.

Deploy FastAPI on Floo

Dockerfile, config, and first deploy for a Python API.

Deploy Vite on Floo

Dockerfile, config, and first deploy for a frontend app.

​
What To Reach For Next

Builds and Dockerfiles

See Dockerfile requirements and Floo cached base images.

Configuration

See exact floo.app.toml and floo.service.toml examples.