page:blueprints:b2b saas:asset library:laravel

B2B SaaS: Asset Library Using Laravel

A asset library blueprint for B2B SaaS built with Laravel 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:
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 Laravel:
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 Laravel
• Where can I host B2B SaaS: Asset library built with Laravel?
• 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 Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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.
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  --public --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  --kind build
   

Success Checks

• App responds on its public URL: **/ **: (expect: ample canary laravel patterns)
• Browser-file-uploads self-test from the example: /p/browser-file-uploads (expect: see the pattern fixture checks)

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Components:
  • App server: size s-1vcpu-1gb, quantity 1, monthlyAmount 5.00
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1, monthlyAmount 5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.