tenant workspaces.md

Host partner portal with Laravel: tenant-scoped workspaces

Summary

Deploy a partner 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 partner portal-specific behavior as your application code.

Infrastructure requirements

Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)

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

Exact 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

Steps

Build and start. 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.
Implement the pattern on PostgreSQL. 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.
Deploy. 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.
```
ample deploy . --name <app-name> --public
```
Verify. 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 <deployment_id> --kind build then --kind runtime.
```
ample logs <deployment_id> --kind build
```

Tested examples

Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Multi-pattern Laravel app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success checks

app responds on its public URL (/ on the live URL, expect ample canary laravel patterns)
multi-tenant-relational-data self-test (/p/multi-tenant-relational-data on the live URL, 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 partner 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

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

app server x1 s-1vcpu-1gb: 5.00 USD
managed PostgreSQL database x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c): 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); checks passed for multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). (expires 2027-03-19T20:36:21Z)
canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c): The same Laravel app deployed with a --release-command migration; the marker it created was readable after activation. (expires 2027-03-19T20:36:21Z)

Last verified: 2026-09-20T20:36:21Z

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read.