page:recipes:client portal:rails:tenant workspaces

Host client portal with Rails: tenant-scoped workspaces

Deploy a client portal built with Rails 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 Rails: 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 client portal-specific behavior as your application code.

Representative Queries

• Host client portal with Rails: tenant-scoped workspaces
• Where can I host Client portal built with Rails?
• I need an explicit tenant model and application-enforced tenant isolation tests.

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

Prerequisites

1. A Rails project that builds and starts with the documented commands (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

Workflow Steps

1. Build and start: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rail server reading PORT on the ruby-3.4 template with RAILS_ENV=production. 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. Command: ample deploy . --name <your-app-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. Command: ample logs --kind build then --kind runtime.

Limitations

• Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and Rails major versions are not verified.
• The client 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

• Monthly Amount: $10.00
• Components:
  • App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.