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

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

## Representative Queries
- Host partner portal with Spring Boot: tenant-scoped workspaces
- Where can I host Partner 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
1. **Compute**  
   Status: verified  
   Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **Postgres**  
   Status: verified  
   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.

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

## Tested Configuration
- Template: jvm-21  
- Runtime: java  
- Size: s-1vcpu-2gb  
- Build: ./mvnw -q -DskipTests package  
- Start: java -jar $(ls target/*.jar | grep -v -- '-plain' | head -n 1)

## Workflow Steps
1. **Build and start**  
   Command: `./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**  
   Command: `ample deploy . --name --public`  
   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.

4. **Verify**  
   Command: `ample logs --kind build`  
   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`.

## Success Checks
- App responds on its public URL (expect: ample canary spring boot patterns)
- Multi-tenant-relational-data self-test (expect: tenant_isolation=ok)

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

## 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: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: $5.0  
     - Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: $5.0
  
- Note: Always-on monthly price of tested sizes; apps and databases auto-pause when idle.

## Evidence Summary
- **Observation** (Spring Boot pattern fixture deployed on Ample): 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).
- **Implementation Revision**: 1d28ae0-dirty (CLI 0.1.21)  
- **Expires At**: 2027-03-20T02:34:39Z

## Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse Partner portal**
6. **Browse Spring Boot**
7. **Browse Multi-tenant relational data**
8. **Browse Deploy web app**