B2B SaaS: documentation site using Laravel · Ample Computer

B2B SaaS: documentation site using Laravel

A documentation site blueprint for B2B SaaS built with Laravel on Ample. Domain schema:

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 Laravel: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the B2B SaaS domain. Create the tables customer_workspaces, workspace_members, doc_versions, customer_assets, state_transitions. Customer tenants live in customer_workspaces; keep the sensitive classes (customer data inside workspaces, usage and billing records, support attachments) out of this schema.

  2. Workflow step 1. Model versioned documents with a state machine (draft, review, published) scoped to a product version

  3. Workflow step 2. Publish assets for released versions to the CDN bucket

  4. Workflow step 3. Serve only published versions publicly

  5. Workflow step 4. Deploy and verify the version list and a published page

  6. 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=... --env CDN_PUBLIC_URL=...
  1. Verify. Run the pattern self-test(s) from the example (/p/relational-records) 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 laravel patterns”
✓ Relational-records self-test from the example · http get/p/relational-records → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run

Laravel pattern fixture deployed on Ample (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); the relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's B2B SaaS schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover