Host crm with FastAPI: relational workspace data · Ample Computer
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). The CRM-specific behavior (your record schema, states and access rules) is your application code on that verified basis.
Verified November 6, 2026
What it runs on
Computeverified Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgresverified Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
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
Exact tested configuration
install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes-1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12
Steps
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.
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.
Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public --start "python3 run.py"
- 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 <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary fastapi patterns”
✓ relational-records self-test· http get/p/relational-records → “records=ok transitions=true isolation=true”
Evidence
November 6, 2026 · canary run
FastAPI pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template); checks passed for relational-records and configuration-secrets. Pattern proof: 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).November 6, 2026 · canary run
The same FastAPI app deployed with a --release-command migration; the marker it created was readable after activation.
Tested examples
- FastAPI pattern fixture. Multi-pattern FastAPI app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture.
The pattern checks verified the platform side; the CRM itself (your record schema, states and access rules) is your application code.
Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.