page:recipes:member portal:flask:tenant workspaces

Host member portal with Flask: tenant-scoped workspaces

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

Representative Queries

Resource Requirements

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.

Framework

Flask

Workload

Member portal

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

Tested Configuration

Input Schema

{"additionalProperties":false,"properties":{"env":{"description":"Encrypted environment variables (bucket credentials, secrets)","items":{"pattern":"^[A-Z][A-Z0-9_]*=.*$","type":"string"},"maxItems":50,"type":"array"},"name":{"description":"App name","maxLength":63,"minLength":1,"pattern":"^[a-z0-9-]+$","type":"string"},"path":{"description":"Project directory or ample.toml service","maxLength":512,"minLength":1,"type":"string"},"release_command":{"description":"Migration command run before activation","maxLength":512,"type":"string"},"start":{"description":"Start command (Python apps pass one explicitly)","maxLength":512,"type":"string"}},"required":["name","path","start"],"type":"object"}

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. 
    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. 
    ample logs  --kind build

Examples

Success Checks

  1. App responds on its public URL
    • Kind: http_get
    • Path: /
    • Expect: ample canary flask patterns
  2. Multi-tenant-relational-data self-test
    • Kind: http_get
    • Path: /p/multi-tenant-relational-data
    • Expect: tenant_isolation=ok

Limitations

Cost Estimate

Evidence Summary

  1. Kind: canary_run
    Summary: Flask pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template); checks passed for multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok).
    Observed At: 2026-09-21T01:14:18Z
    Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
    Expires At: 2027-03-20T01:14:18Z
    • Scope:
      • Checks: /p/multi-tenant-relational-data
      • Pattern: pattern:multi-tenant-relational-data
      • Template: python-3.12
  2. Kind: canary_run
    Summary: The same Flask app deployed with a --release-command migration; the marker it created was readable after activation.
    Observed At: 2026-09-20T01:54:51Z
    Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
    Expires At: 2027-03-19T01:54:51Z
    • Scope:
      • Pattern: pattern:multi-tenant-relational-data

Last Verified At

2026-09-21T01:14:18Z

Unknowns

Next Actions

  1. Action ID: browse-catalog
    Label: Browse the catalog index
    Method: GET
    Path: /v1/catalog
    Requires Authentication: false
  2. Action ID: search-recipes
    Label: Search published recipes by intent, stack and constraints
    Method: POST
    Path: /v1/catalog/search
    Requires Authentication: false
  3. Action ID: plan:page:recipes:member-portal:flask:tenant-workspaces
    Label: Prepare a side-effect-free deployment plan for an authorized project
    Method: POST
    Path: /v1/catalog/plan
    Requires Authentication: true
  4. Action ID: auth-setup
    Label: Read the existing agent authentication setup
    Method: GET
    Path: /mcp/setup
    Requires Authentication: false
  5. Action ID: browse:workload:member-portal
    Label: Browse Member portal
    Method: GET
    Path: /v1/catalog/nodes/workload%3Amember-portal
    Requires Authentication: false
  6. Action ID: browse:stack:framework-flask
    Label: Browse Flask
    Method: GET
    Path: /v1/catalog/nodes/stack%3Aframework-flask
    Requires Authentication: false
  7. Action ID: browse:pattern:multi-tenant-relational-data
    Label: Browse Multi-tenant relational data
    Method: GET
    Path: /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data
    Requires Authentication: false
  8. Action ID: browse:intent:deploy-web-app
    Label: Browse Deploy web app
    Method: GET
    Path: /v1/catalog/nodes/intent%3Adeploy-web-app
    Requires Authentication: false