Skip to main content
Move a Next.js app from Vercel to floo with a Dockerfile and floo.app.toml. Move its env vars, scheduled jobs, database, and domain as you deploy. Requires the app’s code in a GitHub repository, the floo CLI signed in with floo auth login, and the Vercel CLI linked to the project. Without a GitHub repository, floo deploy --hosted deploys from a copy floo hosts; see Deploy without a GitHub repository.

What maps to what

1. Add a Dockerfile

Set output: "standalone" in next.config.js and copy the Next.js Dockerfile. The standalone server reads PORT, and HOSTNAME=0.0.0.0 makes it listen on every interface. Add a .dockerignore with node_modules, .next, and .env*. Move redirects, rewrites, and headers from vercel.json into next.config.js in the same commit. The other vercel.json keys have no effect on floo; delete the file once the cron jobs below are moved.

2. Write floo.app.toml

For a Next.js app with Postgres, team sign-in, a daily job, and a custom domain:
floo.app.toml
Leave out access_mode for a public app; a new app on your GitHub repository starts public. An app floo hosts starts accounts, so set access_mode = "public" there. Deploy a customer-facing app covers a public prod with sign-in on dev and previews. The domain block takes effect with the first prod release (step 7).

3. Import env vars

vercel env pull writes a project’s variables to a file. Exclude Vercel variables and the old database connection strings; floo injects DATABASE_URL and PG* for managed Postgres. Add .env.vercel and .env.import to .gitignore before creating them:
Keep both files outside git. Import .env.import after the first deploy creates the app. floo passes every NEXT_PUBLIC_* variable to the build as a Docker build arg. The Dockerfile’s build stage must declare it with ARG and ENV, or the bundle has undefined baked in. See Build-time env vars. If the app has its own sign-in library, keep it, and add the new floo host to its callback URLs.

4. Move the cron jobs

Vercel calls a cron job’s path with an HTTP GET on the production deployment. floo runs a job’s command in a new container from the service’s image, with the same env vars and no server running. Move the route handler’s logic into a script and point the job at it:
vercel.json
partial
Vercel’s docs now call Cron Jobs a legacy feature moving to Schedules; the mapping is the same. Both platforms read the schedule in UTC. A floo job runs for up to 1,500 seconds and does not retry. Copy scripts/ into the Dockerfile’s final stage; the standalone output includes only the packages the server imports, so a script that needs more must have them in the image too (layer order). Once the script handles the work and nothing else calls the route, remove the cron route and its CRON_SECRET check. Run the job by hand after the first deploy.

5. Deploy to dev

The first floo deploy stops with one link if floo can’t read the repository yet. Install the floo GitHub App on the repository’s owner, then run floo deploy again. It waits until the dev deploy is live, and floo status --app my-app --json shows why if it is not. The first build or startup can fail if it needs variables that have not been imported yet. Once the app exists, import them and rebuild:
New keys are secrets except for build-time prefixes. Review the values before importing them to dev; use test credentials for services that must not receive dev traffic. Keep .env.import until you have imported the prod values in step 7; then delete both files. Test the scheduled job after the deploy:
Invite the people who signed in through Vercel Authentication:
While access_mode = "accounts", floo’s sign-in page sits in front of every request, and only invited people get in.

6. Move the database

The dev deploy creates the managed database. Dump the Vercel-side database with its non-pooled connection string and a pg_dump at least as new as its server, then load the dump into floo’s dev database with psql:
For a Supabase database, add --schema=public to pg_dump; Supabase’s own schemas do not restore elsewhere. floo run sets the PG* variables for the dev database, so psql connects with no connection string. With a custom-format dump, convert it first with pg_restore --clean --if-exists --no-owner --no-privileges --file app.sql app.dump. Restore before you set migrate_command: the dump carries your migration tool’s history table, so the first migration run after it finds nothing to apply. floo run opens a dev session, so these commands load dev. Prod gets its own database with the first release (step 7). After that release, load the same file into prod with prod’s DATABASE_URL:
floo env get needs a write-scoped floo API key, and each read is audited. --reveal-secrets lets it print a connection string, and the command substitution keeps the URL out of your shell history. --clean --if-exists in the dump drops each table before recreating it, so the load also works after the release’s migrate_command has created the schema. To export a managed database, see floo db dump.

7. Move the domain

A custom domain serves prod. Replace owner/repo with your GitHub repository and publish the first release:
Prod env vars apply with the next release, which is why the import sits between two releases. After the first release creates the prod database, restore and verify its data before changing the traffic record. Delete .env.vercel and .env.import after verifying the prod import. floo domains show prints two records: Lower the record’s TTL a day ahead, as Vercel recommends. Publish the certificate record first; it does not change where traffic goes. Then replace Vercel’s traffic record (the A record or CNAME shown in the Vercel project’s Domains settings) with the floo one. For an apex such as example.com, use an ALIAS or ANAME to edge.getfloo.com, or an A record to 34.117.26.37.
Keep the Vercel project until the domain is active. Pointing the traffic record back at Vercel is the move’s rollback.

Roll back on floo

Choose a deploy ID from the list, check its environment, and replace DEPLOY_ID:
A rollback re-points traffic at an earlier image. It does not run migrate_command or revert env vars. See Releases and rollbacks.

Previews

Vercel builds a preview for every branch push and pull request. On floo, previews are off until you turn them on, and each pull request then gets its own URL and its own Postgres branch:
partial
/floo preview on in a pull request comment turns one on for that PR alone. Most apps that move from Vercel need dev and prod first; see Preview environments.

Agent prompt

Paste into your agent from the repository root. Replace my-app, app.example.com, and <owner/repo>.

Where Vercel is stronger

As of November 9, 2026, from Vercel’s documentation:
  • Global delivery. Vercel’s CDN runs 126 points of presence in 51 countries. floo’s edge cache serves Next.js /_next/static/* files for public apps (edge cache); pages render in your app’s container.
  • Next.js without configuration. Vercel maintains Next.js and deploys it with zero configuration. floo needs a Dockerfile.
  • Managed ISR. Vercel’s CDN runs Incremental Static Regeneration caching on every plan. On floo, ISR uses the Next.js server’s own cache inside the container.
  • Previews by default, with comments. Every branch push and pull request gets a preview URL, and Comments on previews are free on all plans. floo previews are opt-in and have no comment toolbar.
  • Image Optimization is a platform service on every Vercel plan. floo has no separate image service.
  • A free plan. Hobby is free for personal, non-commercial projects. floo’s entry plan, Starter, is $4 a month with 4 credits included.

What it costs

One small full-stack app, priced as of November 9, 2026:
  • One Next.js web service with light traffic, deployed by one person.
  • A small Postgres database, about 1 GB.
  • Sign-in so about 5 named people can use the app, and nobody else.
  • One job that runs once a day.
  • Vercel usage stays inside Pro’s included $20 credit. floo’s numbers are the personal-app estimate on getfloo.com/pricing: “a default-size service (1 vCPU, 0.5 GiB) busy about an hour a day, a 1 GiB database and light traffic. Builds and logs are extra.”
floo’s Pro plan is $25 a month with $25 of credits and 5 builder seats; Team is $250 a month with $250 of credits and 50 builder seats. Rates are on getfloo.com/pricing.

Next steps

Build a Next.js app

Dockerfile, NEXT_PUBLIC_* build variables, Prisma migrations, and local development.

App sign-in

Identity headers, app roles, and sign-out.

Production environments

Dev on every push, prod on every release.

Custom domains

DNS records, apex domains, and activation.

Customer-facing apps

A public prod URL with invite-only dev and previews.

A safe backend

Database, sign-in, jobs, and secrets behind your server.