Phase 2

Hosted workspace onboarding, starter trials, and billing foundations are now in the product.

SimplyWarmup now supports confirmed-email signup, workspace creation, invitation-based access, starter trials, and billing-provider hooks. The warmup runtime remains available under the App area, but it now sits behind a real control plane instead of opening anonymously.

Confirmed email onboarding Starter trial automation Workspace-aware runtime

Product Positioning

Commercial onboarding is no longer theoretical

Signup, confirmation, starter trials, plan catalog seeding, and workspace provisioning are now part of the codebase instead of roadmap placeholders.

Routing Strategy

Anonymous traffic lands on marketing, authenticated traffic lands in the control plane

The marketing area stays public while the App area now assumes a signed-in workspace member and resolves runtime state from that workspace.

Current Runtime

The warmup engine now runs inside workspace boundaries

Operational data, settings, mailbox imports, and background worker loops are now tied to workspaces instead of a single global runtime bucket.

Next Phase

Tenant runtime hardening and hosted data platform work

Phase 3 can now focus on deeper tenant-runtime auth, roles, and SQL Server migration because the control-plane and workspace model are in place.

Path To Launch

What follows this foundation

  1. Lock down the tenant runtime with stricter authz, session handling, and SQL Server-hosted persistence.
  2. Move worker loops into durable job infrastructure and add mailbox OAuth support.
  3. Expand support surfaces, observability, and end-to-end test coverage.
  4. Push the hosted control plane through pilot onboarding and first paid clients.