B2B SaaS: asset library using Next.js · Ample Computer
B2B SaaS: Asset Library Using Next.js
An asset library blueprint for B2B SaaS built with Next.js 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 enforced in the application. Technical basis verified on Next.js: 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 5, 2026
What it runs on
Compute Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
Postgres 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 storage 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 Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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
- build npm run build --if-present
- install npm install
- runtime node
- sizes 1vcpu-1gb
- start npm run start
- template node-22
Steps
Model the B2B SaaS domain. Create the tables customer_workspaces, workspace_members, doc_versions, customer_assets, uploads. 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 assets linked to their owning group or workspace.
Workflow step 2. Validate uploads and store them in the private bucket; link each object to its row.
Workflow step 3. Authorize downloads by membership.
Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload.
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 --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/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 next js patterns”
✓ browser-file-uploads self-test from the example · http get/p/browser-file-uploads → “see the pattern fixture checks”
Evidence
- November 5, 2026 · canary run
Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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
- Next.js pattern fixture. Verified browser file uploads basis for this blueprint.
What it doesn’t cover
- The technical basis (browser file uploads on Next.js) 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 node-22 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.