page:recipes:inventory manager:flask:relational workspace

Host inventory manager with Flask: relational workspace data

Deploy an inventory manager 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 inventory manager-specific behavior as your application code.

Summary

• Representative Queries
  • Host inventory manager with Flask: relational workspace data
  • Where can I host Inventory manager built with Flask?
  • I need a workspace-specific schema, state transitions, and access rules.

Resource Requirements

• primitive:compute
• primitive: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.

Execution Status

• Framework: Flask
• Workload: Inventory manager
• Release Status: published
• Support Status: verified
• Execution Status: ready

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
• 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.
2. Implement the pattern on PostgreSQL: The fixture's module implements relational records. 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.
4. Verify: Fetch the live URL and the pattern self-test route(s).

Success Checks

• App responds on its public URL.
• Relational-records self-test.

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.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  1. App server
     • Size: s-1vcpu-1gb
     • Monthly Amount: 5.0
  2. Managed PostgreSQL database
     • Size: s-1vcpu-1gb
     • Monthly Amount: 5.0

Examples

• Flask pattern fixture: Multi-pattern Flask app whose relational records module was checked live.

Evidence Summary

• Kind: canary_run
  • Summary: Flask pattern fixture deployed on Ample.
• Last Verified At: 2026-09-21T01:14:18Z

Formats

• HTML
• Markdown
• JSON

Next Actions

• Browse the catalog index.
• Search published recipes by intent, stack, and constraints.