### Host crm with FastAPI: relational workspace data

Deploy a crm 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 crm-specific behavior as your application code.

#### Representative Queries
- Host crm with FastAPI: relational workspace data
- Where can I host CRM built with FastAPI?
- I need a workspace-specific schema, state transitions and access rules.

### 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

### 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`

### 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 crm 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.00 
- **Components:**  
  - **App server:** s-1vcpu-1gb, Quantity: 1, Monthly Amount: $5.00  
  - **Managed PostgreSQL database:** s-1vcpu-1gb, Quantity: 1, Monthly Amount: $5.00 
  - **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### 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`

### Examples
- **Title:** FastAPI pattern fixture  
  **Description:** Multi-pattern FastAPI app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Ref:** tests/deploy-canaries/fastapi-patterns

### Success Checks
- **Check:** App responds on its public URL  
  **Expect:** `ample canary fastapi patterns`

- **Check:** Relational-records self-test  
  **Expect:** `records=ok transitions=true isolation=true`