B2B SaaS: asset library using Django · Ample Computer

B2B SaaS: asset library using Django

An asset library blueprint for b2b saas built with Django on Ample. Domain schema:

Public information: product documentation by version, pricing and plan comparison, status and changelog. Kept out of scope until handling is reviewed: customer data inside workspaces, usage and billing records, support attachments. Customer workspace data is tenant-scoped; isolation is enforced in the application. Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

  1. python3 -m pip install --target .ample/python -r requirements.txt
  2. sizes-1vcpu-1gb
  3. PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
  4. templatepython-3.12

Steps

  1. Model the b2b saas domain. Create the tables customer_workspaces, workspace_members, doc_versions, customer_assets, uploads. Customer tenants lives in customer_workspaces; keep the sensitive classes (customer data inside workspaces, usage and billing records, support attachments) out of this schema.

  2. Workflow step 1. Model assets linked to their owning group or workspace.

  3. Workflow step 2. Validate uploads and store them in the private bucket; link each object to its row.

  4. Workflow step 3. Authorize downloads by membership.

  5. Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload.

  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

    $ ample deploy . --name <app-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/browser-file-uploads) and your own acceptance checks for the b2b saas workflow.

    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

- ✓ app responds on its public URL· http get/ → “ample canary django patterns”
- ✓ browser-file-uploads self-test from the example· http get/p/browser-file-uploads → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run 
   
   Django pattern fixture deployed on Ample (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 browser file uploads checks passed: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The blueprint's B2B SaaS schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified browser file uploads basis for this blueprint.

## What it doesn’t cover

- The technical basis (browser file uploads on Django) was verified with the pattern fixture; the b2b saas schema and workflow are an original design for this blueprint, built on that basis.
- Customer workspace data is tenant-scoped; isolation is enforced in the application.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.