# B2B SaaS: asset library using Django

## Summary
A asset library blueprint for b2b saas built with Django on Ample. Domain schema:

- **customer_workspaces** (name, plan, seat_count, created_at): customer tenants;  
- **workspace_members** (workspace_id, email, role): members and roles per workspace;  
- **doc_versions** (product_version, title, object_key, published_at): versioned product documentation;  
- **customer_assets** (workspace_id, title, object_key, visibility): assets scoped to one customer;  
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

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 application-enforced and no security certification is claimed.

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).

## Representative Queries
- B2B SaaS: asset library using Django
- Where can I host B2B SaaS: Asset library built with Django?
- I need a genuinely specialized asset library workflow covering customer workspaces, versioned product docs and customer-specific assets.

## 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.
- **S3-compatible object storage:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which b2b saas data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the b2b saas domain:** Create the tables customer_workspaces, workspace_members, doc_versions, customer_assets, uploads. Keep the sensitive classes (customer data inside workspaces, usage and billing records, support attachments) out of this schema.
2. **Model assets linked to their owning group or workspace.**
3. **Validate uploads and store them in the private bucket; link each object to its row.**
4. **Authorize downloads by membership.**
5. **Deploy:** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
6. **Verify:** Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the b2b saas workflow.

## Success Checks
- App responds on its public URL; expect: `ample canary django patterns`
- Run the browser-file-uploads self-test from the example; expect: `see the pattern fixture checks`.

## Limitations
- 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 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.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.

## Example
### Django pattern fixture
- **Description:** Verified browser file uploads basis for this blueprint.
- **Source Reference:** tests/deploy-canaries/django-patterns

## Evidence Summary
- **Kind:** canary_run  
- **Summary:** Django pattern fixture deployed on Ample; the browser file uploads checks passed: content-type and size validation that rejects disallowed files.  
- **Observed At:** 2026-09-20T03:31:44Z  
- **Implementation Revision:** 03b6402b1b3e19178985f08ea4033804521d85d4-dirty  
- **Expires At:** 2027-03-19T03:31:44Z  
- **Scope:** checks: ["/p/browser-file-uploads"], pattern: ["pattern:browser-file-uploads"], template: ["python-3.12"]

## Formats
- [HTML Version](/content/blueprints/b2b-saas/asset-library/django/index.html)
- [Markdown Version](/content/blueprints/b2b-saas/asset-library/django.md)
- [JSON Version](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Ab2b-saas%3Aasset-library%3Adjango)