B2B SaaS: client portal using Django · Ample Computer
B2B SaaS: client portal using Django
A client portal 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;
- document_access (document_id, principal_reference, role, granted_at): who may read which document.
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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).
Verified November 6, 2026
What it runs on
Computeverified: Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgresverified: Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
S3-compatible object storageverified: Buckets speak the S3 API with SigV4 credentials Ample Computer issues;
ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- 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 createpassed as encrypted S3_* environment variables - A review of which B2B SaaS data classes may be handled at all; this blueprint models public information only
Exact tested configuration
install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes-1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12
Steps
Model the B2B SaaS domain. Create the tables customer_workspaces, workspace_members, doc_versions, customer_assets, document_access. Customer tenants live in customer_workspaces; keep the sensitive classes (customer data inside workspaces, usage and billing records, support attachments) out of this schema.
Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement.
Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).
Workflow step 3. Store documents in the private bucket and stream them through the app.
Workflow step 4. Deploy and verify the negative authorization tests and an authorized download.
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=...
- Verify. Run the pattern self-test(s) from the example (/p/private-document-library) 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”
✓ private-document-library self-test from the example· http get/p/private-document-library → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
Django pattern fixture deployed on Ample. The private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's B2B SaaS schema and workflow below build on that verified basis.
Tested examples
- Django pattern fixture. Verified private document library basis for this blueprint.
What it doesn’t cover
- The technical basis (private document library 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-urlreturns presigned upload URLs.