page:blueprints:equipment rental:product catalog:django

Equipment Rental: Product Catalog using Django

A product catalog blueprint for equipment rental built with Django on Ample. Domain schema:

• equipment (sku, name, category, day_rate, serial_tracked): rental catalog;
• stock_movements (sku, unit_serial, delta, reason, moved_at): check-outs, returns and maintenance;
• rentals (rental_no, period_start, period_end, status): rentals with status transitions;
• rental_lines (rental_no, sku, unit_serial, rate): rental contents;
• events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

Public information: equipment catalog and rates, availability calendar, deposit and insurance terms. Kept out of scope until handling is reviewed: renter identity documents, payment and deposit details. Identity verification and deposits are outside these flows; only availability and rental status are modeled.
Technical basis verified on Django: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

Representative Queries

• Equipment rental: product catalog using Django
• Where can I host Equipment rental: Product catalog built with Django?
• I need a genuinely specialized product catalog workflow covering asset serial numbers, availability windows and return status.

Resource 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.
• S3-compatible Object Storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Workflow Steps

1. Model the equipment rental domain: Create the tables equipment, stock_movements, rentals, rental_lines, events. Rental catalog lives in equipment; keep the sensitive classes (renter identity documents, payment and deposit details) out of this schema.
2. Model the SKU catalog with versioned updates.
3. Record every catalog change as an event in the same transaction.
4. Reject stale concurrent updates.
5. Deploy and verify history and conflict handling.
6. Deploy: Run the synchronous deploy once and read the result.

   ample deploy . --name --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=..."
   

7. Verify: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the equipment rental workflow.

   ample logs --kind build
   

Limitations

• The technical basis (transactional workflows on Django) was verified with the pattern fixture; the equipment rental schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made.
• Verified on the python-3.12 template; region, request-duration limits and other sizes are unknown or unverified.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App Server: 1 x s-1vcpu-1gb ($5.00)
  • Managed PostgreSQL Database: 1 x s-1vcpu-1gb ($5.00)
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Success Checks

• App responds on its public URL.
• Transactional-workflows self-test from the example.