Host crm with Django: relational workspace data

Deploy a crm built with Django 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 Django: 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:
  • Host crm with Django: relational workspace data
  • Where can I host CRM built with Django?
  • I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Postgres: 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

• Django

Workload

• CRM

Release Status

• Published

Execution Status

• Ready

Prerequisites

1. A Django project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases:read

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install Command: python3 -m pip install --target .ample/python -r requirements.txt
• Start Command: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Input Schema

• Properties:
  • env: Encrypted environment variables (bucket credentials, secrets)
  • name: App name
  • path: Project directory or ample.toml service
  • release_command: Migration command run before activation
  • start: Start command (Python apps pass one explicitly)
• Required: name, path, start

Workflow Steps

1. Build and start: pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.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 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: 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 run.py"
4. 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 --kind build then --kind runtime.
   • Command: ample logs --kind build

Examples

• Django pattern fixture: Multi-pattern Django app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary django patterns
• Relational-records self-test
  • Kind: http_get
  • Path: /p/relational-records
  • Expect: records=ok transitions=true isolation=true

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Django major versions are not verified.
• 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.
• 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.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse CRM
6. Browse Django
7. Browse Relational records
8. Browse Deploy web app