Host project tracker with FastAPI: relational workspace data

Deploy a project tracker built with FastAPI on Ample using the relational records pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on FastAPI: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

Representative Queries

• Host project tracker with FastAPI: relational workspace data
• Where can I host Project tracker built with FastAPI?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. Compute: 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: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Framework

FastAPI

Workload

Project tracker

Prerequisites

• A FastAPI project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install: python3 -m pip install --target .ample/python -r requirements.txt
• Start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Workflow Steps

1. Build and start: pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template. The server must bind 0.0.0.0 on PORT.
2. Implement the pattern on PostgreSQL: The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Deploy: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op. Command: ample deploy . --name --public --start "python3 run.py"
4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime. Command: ample logs --kind build

Examples

• FastAPI pattern fixture: Multi-pattern FastAPI app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. App responds on its public URL
   • Kind: http_get
   • Path: /
   • Expect: ample canary fastapi patterns
2. Relational-records self-test
   • Kind: http_get
   • Path: /p/relational-records
   • Expect: records=ok transitions=true isolation=true

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and FastAPI major versions are not verified.
• The project tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server (s-1vcpu-1gb): $5.0
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.0

Evidence Summary

• Kind: canary_run
• Summary: FastAPI pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.
• Observed At: 2026-09-21T01:14:18Z

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints