# Host vendor portal with Spring Boot: tenant-scoped workspaces

## Summary
Deploy a vendor portal built with Spring Boot 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 Spring Boot: 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.

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

## Resource Requirements
- primitive:compute
- primitive:postgres

## 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.

## Framework
Spring Boot

## Workload
Vendor portal

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## Prerequisites
- A Spring Boot project that builds and starts with the documented commands (./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT)
- 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

## Workflow Steps
1. **Build and start**  
   ./mvnw -q -DskipTests package (or the Gradle wrapper) producing one application jar, then java -jar on the jvm-21 template (Temurin JDK 21) with server.port read from PORT. The server must bind 0.0.0.0 on PORT.

2. **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.

3. **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  --public
   ```

4. **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  --kind build` then `--kind runtime`.
   ```
   ample logs  --kind build
   ```

## Limitations
- Verified on the jvm-21 template at s-1vcpu-2gb with the example fixture; other sizes, templates and Spring Boot 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:
   - **App server**  
     - Size: s-1vcpu-1gb  
     - Quantity: 1.0  
     - Monthly Amount: 5.0  
   - **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.

## Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**
- **[Search published recipes by intent, stack and constraints](https://api.ample.computer/v1/catalog/search)**  
  Body: { "limit": 5, "query": "Host vendor portal with Spring Boot: tenant-scoped workspaces" }
- **[Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.computer/v1/catalog/plan)**  
  Body: { "inputs": {}, "projectId": "", "recipeId": "page:recipes:vendor-portal:spring-boot:tenant-workspaces", "recipeRevision": "r1" }
- **[Read the existing agent authentication setup](https://api.ample.computer/mcp/setup)**
- **[Browse Vendor portal](https://api.ample.computer/v1/catalog/nodes/workload%3Avendor-portal)**
- **[Browse Spring Boot](https://api.ample.computer/v1/catalog/nodes/stack%3Aframework-spring-boot)**
- **[Browse Multi-tenant relational data](https://api.ample.computer/v1/catalog/nodes/pattern%3Amulti-tenant-relational-data)**
- **[Browse Deploy web app](https://api.ample.computer/v1/catalog/nodes/intent%3Adeploy-web-app)**

## Evidence Summary
- **Canary Run:**  
  Spring Boot pattern fixture deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets.
  - Observed At: 2026-09-21T02:34:39Z
  - Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
  - Expires At: 2027-03-20T02:34:39Z

- **Canary Run:**  
  The same Spring Boot app deployed with a --release-command migration; the marker it created was readable after activation.
  - Observed At: 2026-09-20T22:49:19Z
  - Implementation Revision: af6f45adea26-dirty (CLI af6f45a)
  - Expires At: 2027-03-19T22:49:19Z