Skip to content

Generated SaaS solution pack

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

Generated products are outputs, not Factory components. Each product has its own bounded contexts, stores, migrations, identity audience, tenant model, configuration and package recipe. It must never depend on the Factory control plane to execute ordinary business operations, and a Factory tenant is never the same identity as a product tenant (ADR-0015).

What the pack defines

Area Content
Product domains (BC-30) Bounded contexts, aggregates, APIs, events, stores and migrations generated from MicroserviceTemplate and the SaaS templates; isolated from Factory databases and privileges
Tenant and commercial foundations (BC-31) Tenants, products catalog, entitlements, billing and metering from the five SaaS templates; the product's own tenancy mode under canonical ADR-0100
Product gateway (GW-07) Product-specific ingress and optional BFF with separate audience and tenant semantics
Delivery acceptance Ownership, credential handover, maintainability, dependency upgrades, support and exit are contractual questions (Q-14), not consequences of a successful scaffold
Operations Product SLOs, incidents, drift, recovery owned by the product operator; Factory telemetry may link, never substitute

Current implementation

  • Five SaaS consumer templates exist (Tenants, ProductsCatalog, Entitlements, Billing, Metering; all 2026-09-16) with descriptors, schemas and regenerate.ps1; none dispatches to a generator.
  • ConnectSoft.Saas.MeteringTemplate has real transactional usage/quota logic; the others are scaffolds with aggregates (Tenant, Product, Entitlement, Subscription, UsageMeter).
  • DerechHaLev / Bereshit 2.0 is the one production system built from the template estate: Gateway, AuthServer, Identity plus six domain services, Orleans silos per service, custom BFF (not YARP).
  • No generated product exists other than that hand-built estate; the "Generated SaaS" catalog group is intentionally empty.

Existing pages that belong to this pack

Platform design pages (2026-10-09, design plan P16)

Later capabilities

Folded from the former Generated SaaS Product Platform extension roadmap (no dates, no commitments). Principles retained: extend by template, not by patch; agents own generation; backward compatibility by default (versioned events and APIs); pillars inherited automatically (traceability, tenant isolation, audit, observability); marketplace-first reuse; feedback-driven prioritization.

Candidate Purpose Likely template or owner
Billing/payments connector; fine-grained usage metering and quota enforcement Commercial features ConnectSoft.Saas.BillingTemplate, ConnectSoft.Saas.MeteringTemplate
Data residency manager (per-region tenant placement) Compliance Canonical ADR-0100 ResidencySilo mode; new template
In-product analytics, support/helpdesk surface, API key and developer portal Product surfaces Blazor MFE templates; gateway and identity extensions
Entitlement reconciliation, data retention enforcement, tenant off-boarding (export, anonymize, purge), anomaly detection, webhook retry workers Product operations Product owner; patterns from the SaaS templates
Bulk/admin APIs, webhook management, optional GraphQL aggregation, usage and metering API, governed data export (portability) Product APIs Product templates
Common SaaS spine, vertical accelerators, connectors, dashboard packs and edition templates as marketplace bundles Reuse BC-27
SaaS onboarding, pricing/packaging, compliance, performance/SRE and localization agents Agents generating product configuration Software Factory pack

Additional domains and fleet operations remain directions from the Oct-2026 target; none is implied by this table.

Open questions

Q-14 (delivery and support obligations), Q-22 (decided 2026-10-14, ADR-0025), Q-04 (deployment ownership).