## The short version

Move Next.js compute from Fly.io app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Export secrets and env from `fly.toml` \[env\] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values). Not migrated automatically: Multi-region placement, Fly Machines API, volumes and 6PN private networking are not migrated; region is an unknown fact on Ample. Cutover: Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)

## Before you start

- Authorized access to the Fly.io app source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read

## How to do it

1.  **Inventory the source**  
List what Fly.io app provides beyond the component you are moving. Out of scope here: Multi-region placement, Fly Machines API, volumes and 6PN private networking are not migrated; region is an unknown fact on Ample.

2.  **Source step 1**  
Export secrets and env from `fly.toml` \[env\] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values)

3.  **Source step 2**  
Translate `fly.toml` services and the Dockerfile or buildpack into a Node or Python source deploy; Ample builds from source on its templates

4.  **Source step 3**  
Note Fly-only features in use: multi-region placement, machines API, volumes, private networking

5.  **Deploy on Ample in parallel**  
Run the following command:  
```
ample deploy . --name <app-name> --public --env-file .env.production
```
Keep the source running.

6.  **Validate before cutover**  
Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).

7.  **Cut over**  
Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero.

8.  **Rollback**  
Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Tested examples

- **Next.js pattern fixture (destination)** (`tests/deploy-canaries/next-js-patterns`): Verified destination basis: Next.js compute.

## How to know it worked

- Destination app responds on its public URL (`/` on the live URL, expect ample canary next js patterns)
- Configuration-secrets check from the destination example (`/p/configuration-secrets` on the live URL, expect to see the pattern fixture checks)
- Relational-records check from the destination example (`/p/relational-records` on the live URL, expect to see the pattern fixture checks)
- Data or object counts and checksums match the source

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- App server x1 `s-1vcpu-1gb`: 5.00 USD
- Managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes at the destination. Source costs are unknown to Ample.

## Verification evidence

- Canary run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: Destination side verified: the Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Fly.io app is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-20T02:34:39Z)

## Execution binding

No execution binding. This recipe is documentation only; nothing is executed automatically.