### Host vendor portal with Laravel: tenant-scoped workspaces

Deploy a vendor portal built with Laravel on Ample using the multi-tenant relational data pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Laravel: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the vendor portal-specific behavior as your application code.

#### Summary

- **Family**: Workload recipe
- **Framework**: Laravel
- **Workload**: Vendor portal
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

#### Representative Queries
- Host vendor portal with Laravel: tenant-scoped workspaces
- Where can I host Vendor portal built with Laravel?
- I need an explicit tenant model and application-enforced tenant isolation tests.

#### Resource Requirements
- Compute
- PostgreSQL

#### Infrastructure Requirements
1. **Compute**  
   - **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - **Status**: verified

2. **Postgres**  
   - **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.  
   - **Status**: verified

#### Prerequisites
- A Laravel project that builds and starts with the documented commands (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 at runtime (auto-provisioned when omitted, or supplied with --env)
- An Ample account token with servers:write, databases:read

#### Tested Configuration
- **Template**: php-8.5  
- **Runtime**: php  
- **Size**: s-1vcpu-1gb  
- **Install**: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader  
- **Start**: frankenphp php-server --listen :$PORT --root public

#### Workflow Steps
1. **Build and start**  
   Body: 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 server must bind 0.0.0.0 on PORT.

2. **Implement the pattern on PostgreSQL**  
   Body: The fixture's module implements multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Deploy**  
   Body: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.  
   Command: ample deploy . --name  --public

4. **Verify**  
   Body: Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: ample logs  --kind build

#### Examples
- **Title**: Laravel pattern fixture  
  Description: Multi-pattern Laravel app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  Source Reference: tests/deploy-canaries/laravel-patterns

#### Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary laravel patterns

2. **Multi-tenant-relational-data self-test**  
   - Kind: http_get  
   - Path: /p/multi-tenant-relational-data  
   - Expect: tenant_isolation=ok

#### Limitations
- Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Laravel major versions are not verified.
- The vendor portal itself (your tenant model, membership and per-tenant authorization) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

#### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
  1. App server: size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
  2. Managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.
