Multi-Product Business Software
Suite Platform
One gateway for your entire business software stack.
Overview
Growing operators do not want twelve logins, twelve billing relationships, and twelve disconnected tenant models. Suite Platform is the control plane that sits above CRM, POS, Finance, HRM, Inventory, Receptionist, CMS, and every other modular product. It handles identity, org structure, SKU entitlements, service-link registration, and short-lived handoff tokens so operators open the right product portal without re-entering credentials — while each product keeps its own API, portal, contracts, and data store.
Ideal for
Suite operators who provision tenants and entitlements, product owners defining SKU packaging, enterprise buyers needing one identity layer across modular business software, and developers integrating new products via contracts and handoff patterns.
Problems it solves
- ▸Each new module means another URL, another API key, and another onboarding flow — staff forget which portal does what
- ▸Sales sells CRM today and Finance next quarter, but there is no single place to turn SKUs on or off per tenant
- ▸Integrations devolve into hardcoded URLs and shared secrets scattered across env files instead of a registry operators can manage
- ▸Leadership wants one dashboard showing counts and health across products — not five separate admin consoles
Features
- ▸Suite home and federation — federated launcher with remote product metrics
- ▸Identity and membership — org tenants, companies, roles, and permission catalog
- ▸Per-tenant entitlements — enable or disable product SKUs per subscription plan
- ▸Service link registry — sibling API URLs, portal URLs, and link modes
- ▸Auth handoff — short-lived, single-use tokens for portal session open
- ▸Audit and billing surface — operator action logs and plan/SKU exposure
Modules
Suite home and federation
Aggregates platform entity counts and remote product overview metrics into one launcher. Operators open entitled products via handoff without leaving the suite shell.
Identity and membership
Org tenants, companies, member users, roles, and a permission catalog with soft delete. Foundation for multi-product RBAC across the suite.
Per-tenant entitlements
Enable or disable SKUs per tenant: CRM, POS, finance, HRM, inventory, procurement, manufacturing, projects, reports, receptionist, CMS, and more. Billing surface exposes plan and entitled products.
Service link registry
Register sibling API base URLs, API keys, product tenant IDs, portal URLs, and link modes (native / read / sync). Products discover each other through Platform instead of hardcoded env vars.
Auth handoff
Issues short-lived, single-use tokens so Suite Home can open a product portal without re-entering credentials. Clean separation between gateway identity and product sessions.
Audit and billing surface
Audit log list for operator actions. Billing response exposes plan/SKU and entitled products for downstream billing integration.
Benefits
- ▸One login for the entire suite instead of multiplying credentials per module
- ▸15+ entitleable product SKUs with per-tenant toggles — no redeploy when sales closes an upsell
- ▸Zero shared database tables across product boundaries — each module owns its persistence
- ▸Seconds-level handoff token open time from Suite Home to product portal
- ▸Federated operator view across entitled products without five separate admin consoles
- ▸Audit trail for entitlement, service-link, and membership changes
Use cases
- ▸Monday morning: create an org tenant, enable CRM and Receptionist SKUs, register service links, and invite the owner — Suite Home shows both products ready to launch
- ▸Sales closes an upsell: toggle the finance SKU on, register the Finance service link, and the customer's launcher updates immediately — no redeploy
- ▸Staff opens CRM from Suite Home: Platform issues a single-use handoff token; the CRM portal validates it and opens a session without a second login
- ▸Audit review after a config change: operators pull the audit log for entitlement, service-link, and membership changes
Implementation
1. Provision tenant
Create org, companies, and member users in Platform with roles and membership scoped to the tenant.
2. Entitle products
Toggle SKUs on for the tenant's subscription plan — CRM, finance, receptionist, and other modules as sold.
3. Register service links
Point each entitled product's API and portal at Platform's registry with link mode and credentials.
4. Launch from Suite Home
Users open products via handoff; each product runs independently on its own stack with zero shared database tables.
Technologies
FAQ
Does Platform store CRM or Finance data?
No. Platform stores tenants, memberships, entitlements, service links, and audit events. Each product owns its domain tables with prefixed schemas.
Can I run Platform without other products?
Yes. Platform is independently runnable. Products connect when you register service links and entitle SKUs.
How does handoff differ from SSO?
Handoff issues a short-lived, single-use token to open a specific product portal session. It is designed for suite navigation, not enterprise SAML federation (though that can be layered later).
What happens when a product is not entitled?
It disappears from Suite Home. The product API remains independently reachable if you have its credentials — Platform does not block direct access.
Is this the same as a legacy ERP admin module?
Conceptually yes — it evolved from monolithic ERP admin patterns, restructured as a standalone NestJS gateway product with clear product boundaries.
Start with one tenant model across your suite
Stop multiplying logins every time you add a module. Entitle the products you need today and link the rest when your business is ready — one suite home, zero shared-database coupling.
Contact me →