Creator businesses: client portal using Django

Summary

A client portal blueprint for creator businesses built with Django on Ample. Domain schema:

• customer_workspaces (name, membership_tier, joined_at): member accounts or communities;
• content_items (title, tier_required, object_key, published_at, version): versioned content releases;
• customer_assets (workspace_id, title, object_key, visibility): downloads granted to a member;
• releases (content_item_id, version, notes): release notes per version;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information includes free content and previews, membership tiers, and creator profile. Private information such as member identity and payment status is not modeled here.

Representative Queries

• Creator businesses: client portal using Django
• Where can I host Creator businesses: Client portal built with Django?
• I need a genuinely specialized client portal workflow covering sponsor/client workspaces, publication guides and content assets.

Framework and Workload

• Framework: Django
• Workload: Client portal
• Industry: Creator businesses

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
2. Postgres: Managed PostgreSQL 16 runs in its own microVM.
3. S3-compatible object storage: Buckets are S3-compatible with issued credentials.

Prerequisites

1. A Django project (pip install into .ample/python from requirements.txt).
2. A PostgreSQL driver reading DATABASE_URL.
3. Bucket credentials from ample bucket create passed as encrypted S3_* environment variables.
4. A review of which creator businesses data classes may be handled.

Workflow Steps

1. Model the creator businesses domain: Create the tables customer_workspaces, content_items, customer_assets, releases, and document_access.
2. Model client entities and engagement periods; every document belongs to one engagement.
3. Authorize by client entity and role before any storage access.
4. Store documents in the private bucket and stream them through the app.
5. Deploy and verify the negative authorization tests and an authorized download.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.00
  • Components:
    • App server (s-1vcpu-1gb): 5.00
    • Managed PostgreSQL database (s-1vcpu-1gb): 5.00

Limitations

• No health, financial, privacy or other compliance claim is made.
• Verified on the python-3.12 template at s-1vcpu-1gb.

Examples

• Django pattern fixture: Verified private document library basis for this blueprint.

Success Checks

1. App responds on its public URL.
2. Private-document-library self-test from the example.

Evidence Summary

Django pattern fixture deployed on Ample with passed checks.

Last Verified At

2026-09-20T03:31:44Z

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 Creator businesses.
6. Browse Client portal.
7. Browse Django.
8. Browse Deploy web app.