Skip to content

SaaS service templates

Five ConnectSoft.Saas.<Context>Template repositories implement SaaS bounded contexts on the same submodule + MSBuild layering as other Layer 3 hosts, with additional ConnectSoft.Extensions.Saas.* packages and the canonical feature-flag matrix from SaaS Template Baseline Checklist.

All rows appear in Templates registry.

Tenants

  • Repo: ConnectSoft.Saas.TenantsTemplate
  • Short name: connectsoft-saas-tenants
  • Aggregate: Tenant

Products Catalog

  • Repo: ConnectSoft.Saas.ProductsCatalogTemplate
  • Short name: connectsoft-saas-productscatalog
  • Aggregate: Product

Entitlements

  • Repo: ConnectSoft.Saas.EntitlementsTemplate
  • Short name: connectsoft-saas-entitlements
  • Aggregate: Entitlement

Metering

  • Repo: ConnectSoft.Saas.MeteringTemplate
  • Short name: connectsoft-saas-metering
  • Aggregate: UsageMeter — Orleans grain keys {tenantId, dimension} per domain docs.

Billing

  • Repo: ConnectSoft.Saas.BillingTemplate
  • Short name: connectsoft-saas-billing
  • Aggregate: Subscription — invoices may be modeled as read-model projections per bounded-context docs.

Multitenancy

See multitenancy configuration schema and ADR-0100 (tenant-id metadata on gRPC).

Configuration alignment

Slim Postgres-oriented Persistence.ConnectionStrings in Application appsettings are by design for SaaS hosts — do not force full BaseTemplate monolithic JSON unless an ADR requires it. Acceptance appsettings.Development(.Docker).json must still mirror operational keys used in tests.