Migrate Netlify Web App: FastAPI

Move FastAPI compute from Netlify web 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: Copy environment variables from Site configuration (or netlify env:list) into an env file kept out of the repository. Not migrated automatically: Netlify Functions, Edge Functions, Forms, Identity and _redirects/_headers rules are not migrated; implement redirects in the app or the framework. Cutover: Add the custom domain with ample domain add, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Representative Queries

• Migrate Netlify web app: FastAPI
• Where can I host FastAPI built with FastAPI?
• I need a component-scoped export/import or reconfiguration procedure for FastAPI, with compatibility checks, verification and rollback.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

1. Compute

   • Status: verified
   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. Postgres

   • Status: verified
   • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Prerequisites

• Authorized access to the Netlify web 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

Workflow Steps

1. Inventory the source
   List what Netlify web app provides beyond the component you are moving. Out of scope here: Netlify Functions, Edge Functions, Forms, Identity and _redirects/_headers rules are not migrated; implement redirects in the app or the framework.

2. Source step 1
   Copy environment variables from Site configuration (or netlify env:list) into an env file kept out of the repository

3. Source step 2
   Translate netlify.toml build settings (command, publish directory) into the repository's own build script; Ample runs the detected build

4. Source step 3
   List Netlify-only features in use: functions, edge functions, forms, identity, redirects and headers rules

5. Deploy on Ample in parallel
   pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template. Pass the exported variables with --env; keep the source running.

   Command: ample deploy . --name --public --start "python3 run.py" --env-file .env.production

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, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify.

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

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Netlify web app's standard tooling and was not executed in this catalog's evidence;
• Verified on the python-3.12 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App server (size: s-1vcpu-1gb) - $5.00
  • Managed PostgreSQL database (size: s-1vcpu-1gb) - $5.00
• Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

• Summary: Destination side verified: the FastAPI pattern fixture deployed on Ample and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered).
• Observed At: 2026-09-21T01:14:18Z
• Last Verified At: 2026-09-21T01:14:18Z

Next Actions

1. Browse the catalog index

   • Method: GET
   • Path: /v1/catalog

2. Search published recipes by intent, stack and constraints

   • Method: POST
   • Path: /v1/catalog/search
   • Parameters: {"limit":5,"query":"Migrate Netlify web app: FastAPI"}

3. Prepare a side-effect-free deployment plan for an authorized project

   • Method: POST
   • Path: /v1/catalog/plan

4. Read the existing agent authentication setup

   • Method: GET
   • Path: /mcp/setup

5. Browse Migrate compute

   • Method: GET
   • Path: /v1/catalog/nodes/intent:migrate-compute