Skip to content

SaaS Solution Platform

This page describes the ConnectSoft SaaS Solution Platform—the product-line architecture for building multi-tenant SaaS products from factory templates, shared libraries, and published API contracts. It is written for product managers, enterprise architects, and engineering leads evaluating how ConnectSoft delivers Tenants, Product catalog, Entitlements, Billing, and Metering as first-class services alongside Identity, API Gateway, and Blazor microfrontends.

The SaaS Solution Platform is not a single deployable binary: it is a coherent set of bounded contexts, Git template repositories (ConnectSoft.Saas.*Template), ConnectSoft.Blazor.Shell.Saas, ConnectSoft.Extensions.Saas.* packages, and ServiceModel NuGet surfaces—aligned with the company SaaS framework and factory starters in the ConnectSoft.Documentation repository.

Scope of this platform document

In scope: Core monetization and tenancy path (Tenants, Product catalog, Entitlements, Billing, Metering), template program, shell, MFEs, Extensions.Saas.
Cross-links only: Audit Platform, Notifications Platform, Config Platform—separate platform initiatives with their own documentation.

What This Platform Delivers

  • Bounded-context microservices — One template repository per context (ConnectSoft.Saas.TenantsTemplate, ConnectSoft.Saas.ProductsCatalogTemplate, …) with ConnectSoft.BaseTemplate as a Git submodule.
  • Published contracts — ServiceModel / RestApi / Grpc packages per service; consumers never reference domain layers.
  • Portal UX — ConnectSoft.Blazor.Shell.Saas hosting Blazor MFE modules per context, aligned with Identity / Authorization Server MFE patterns.
  • Shared SaaS infrastructure — ConnectSoft.Extensions.Saas.* (one repo per NuGet package) for tenant context, ASP.NET Core middleware, options, and testing—after templates stabilize.

Core Capabilities

Area Responsibility
Tenants Tenant lifecycle, directories, isolation boundaries
Product catalog Products, editions, features, sellable surfaces
Entitlements What a tenant may use; assignments vs catalog
Billing Subscriptions, invoicing, payment integration
Metering Usage events, quotas, inputs to rating
Front shell Navigation, MFE registry, tenant/edition policy
Libraries Cross-cutting SaaS behavior shared by host and services

Typical Integrations

  • Identity & Access — OIDC via Identity Platform / Authorization Server; claims and policies for tenant and edition.
  • API Gateway — Routes to bounded-context services; propagates identity and tenant headers.
  • Config Platform — Feature flags and non-domain configuration (Config Platform).
  • Billing & Subscription Platform — May overlap domain-wise; this SaaS solution line owns billing/metering bounded contexts for productized templates—align at integration boundaries.
  • Observability — OpenTelemetry across shell, MFEs, and services.

SaaS Consumers by Cycle

  • AI Factory SaaS and horizontal SaaS products consume this platform as generated services and composed UIs.
  • Vertical solutions reuse the same templates and libraries for faster time-to-market.

Relationship to the Factory

  • Templates first — ConnectSoft.Saas.*Template repos establish DDD layout and ServiceModel packaging before freezing Extensions.Saas contracts.
  • Documentation — Canonical epic/feature/task detail: ConnectSoft.Documentation Docs/starters/saas-extensions-and-templates-epics.md; Azure Boards import (when approved) is documented on Epics and program backlog in this Company site.

Epics and program backlog

Detailed Documentation

Agent / integration blueprints:

External factory repo (starters): ConnectSoft Documentation repository — Docs/starters/saas-platform-solution-plan.md, saas-bounded-contexts-and-templates.md, saas-extensions-saas-libraries.md, saas-extensions-and-templates-epics.md.