page:recipes:crm:flask:relational workspace

Host crm with Flask: relational workspace data

Deploy a crm built with Flask 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 Flask: 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.

Summary

Representative Queries

  1. Host crm with Flask: relational workspace data
  2. Where can I host CRM built with Flask?
  3. I need a workspace-specific schema, state transitions and access rules.

Prerequisites

Resource Requirements

Infrastructure Requirements

  1. Compute

    • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
    • Status: verified
  2. Postgres

    • 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.
    • Status: verified

Tested Configuration

Workflow Steps

  1. Build and start

    • Body: 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

    • Body: 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

    • Body: 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

    • Body: 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

  1. 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.
  2. 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.
  3. Region, compliance attestations and request-duration limits are unknown and not claimed.
  4. Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
  5. Managed PostgreSQL 16 only; extensions, connection limits, and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

Components

  1. App server

    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 5.0
  2. Managed PostgreSQL database

    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: 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.