## Host vendor portal with Flask: tenant-scoped workspaces

### Summary
Deploy a vendor portal built with Flask on Ample using the multi-tenant relational data 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 Flask: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the vendor portal-specific behavior as your application code.

### Representative Queries
- Host vendor portal with Flask: tenant-scoped workspaces
- Where can I host Vendor portal built with Flask?
- I need an explicit tenant model and application-enforced tenant isolation tests.

### Resource Requirements
- Compute
- 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
- A Flask project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress from app.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 waitress from app.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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). 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 app.py"
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) 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 Flask major versions are not verified.
- The vendor portal itself (your tenant model, membership and per-tenant authorization) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  1. **App server**: 5.0
  2. **Managed PostgreSQL database**: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Success Checks
1. **App response on public URL**: Expect `ample canary flask patterns`
2. **Multi-tenant-relational-data self-test**: Expect `tenant_isolation=ok`

### Examples
- **Title**: Flask pattern fixture
  - **Description**: Multi-pattern Flask app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - **Source Ref**: tests/deploy-canaries/flask-patterns

### Evidence Summary
- Deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets.

### Last Verified At
- 2026-09-21T01:14:18Z

### Next Actions
- **Browse the catalog index**: `GET /v1/catalog`
- **Search published recipes by intent, stack and constraints**: `POST /v1/catalog/search` 
- **Prepare a side-effect-free deployment plan**: `POST /v1/catalog/plan`
- **Read existing agent authentication setup**: `GET /mcp/setup`
- **Browse Vendor portal**: `GET /v1/catalog/nodes/workload:vendor-portal`
- **Browse Flask**: `GET /v1/catalog/nodes/stack:framework-flask`
- **Browse Multi-tenant relational data**: `GET /v1/catalog/nodes/pattern:multi-tenant-relational-data`
- **Browse Deploy web app**: `GET /v1/catalog/nodes/intent:deploy-web-app`