Skip to main content
    Back to All Solutions

    iShield Solutions Series, Platform & AI · SaaS Platform

    Multi-Tenant SaaS Enablement

    Tenant lifecycle, isolation, metering, entitlements and per-tenant residency for SaaS builders.

    Talk to Sales
    Overview

    What this solution does

    The tenant control plane for software providers and service providers: provisioning, separation, entitlements, usage metering and a per-tenant audit stream run on Link. Usage can be billed in iShield One and tenant-scoped controls kept in iShieldGRC, depending on how the platforms are implemented and configured.

    Why this composition: ISVs and MSPs need tenant lifecycle, isolation, metering and residency together — not five disconnected services. Link runs the multi-tenant control plane, One bills the meters, and GRC supplies the tenant-scoped audit trail customers ask for on RFPs.

    • Enterprise challenge

      Rebuilding tenancy for every product

      Provisioning, separation, plans and metering are rebuilt by each product team.

    • Enterprise challenge

      Usage that never reaches the invoice

      Metering lives in one system and billing in another, reconciled by hand.

    • Enterprise challenge

      Customers asking for their own audit trail

      Tenant-specific evidence has to be assembled for every customer request.

    How it works

    The tenant lifecycle

    Follow one tenant from provisioning through policy, entitlements and metered usage — to billing in iShield One and a per-tenant audit stream that supports tenant-scoped controls.

    • Integration service
    • Policy check
    • Observability
    • Failure path
    • iShield platform
    • Evidence

    1. 01 Integration serviceTenant lifecycle

      Provision, suspend, offboard

      A tenant is created, suspended or offboarded — self-serve or assisted.

      Who acts, controls and evidence
      Who acts
      Platform administrator
      Evidence
      Lifecycle event
      Module: Tenant Lifecycle (Provision, Suspend, Offboard)

    2. 02 Policy checkRuntime controls

      Separation and region

      The tenant is assigned its boundary and, where available, a region; policy rules apply against cross-tenant access.

      Who acts, controls and evidence
      Decided by
      Rules set by the platform and security teams
      Control
      Tenant boundary and region assignment
      Evidence
      Tenant policy record
      Module: Tenant Isolation & Residency Router

    3. 03 Policy checkRuntime controls

      Entitlements evaluated

      The tenant's plan decides which features are on, with overrides and trials.

      Who acts, controls and evidence
      Decided by
      Product and commercial teams
      Control
      Plans, overrides, trials
      Module: Entitlement & Feature Flags

    4. 04 ObservabilityRuntime controls

      Usage metered

      Usage events are counted per tenant and rate limits are applied.

      Who acts, controls and evidence
      Who acts
      Platform operations
      Control
      Rate limits per plan
      Evidence
      Usage records
      Module: Usage Metering & Rate Limits

      05 Failure path

      Limit reached

      A tenant over its limit is throttled according to its plan, without affecting other tenants' limits.

      Who acts: Platform operations

    5. 06 iShield platformTenant lifecycle

      Usage to billing

      iShield One

      Rated usage can feed subscription billing and invoicing in iShield One, depending on how the platforms are implemented and configured.

      Who acts, controls and evidence
      Who acts
      Finance team

    6. 07 EvidenceEvidence & billing

      Per-tenant audit stream

      Activity is recorded per tenant and can be shared with that customer.

      Who acts, controls and evidence
      Who acts
      Platform operations · customer auditors
      Evidence
      Tenant-scoped audit records
      Module: Per-tenant Audit Stream

    7. 08 iShield platformEvidence & billing

      Tenant-scoped controls

      iShieldGRC

      Audit records can support tenant-scoped controls and audits in iShieldGRC, depending on how the platforms are implemented and configured.

      Who acts, controls and evidence
      Who acts
      Compliance team
    Illustration of a tenant lifecycle — not a product screen, and not a statement of where data is held. Regions and separation models depend on implementation and contract.
    What it does

    Core capabilities

    Tenant lifecycle

    Self-serve and assisted provisioning, suspension and offboarding.

    Entitlements & flags

    Plan-driven entitlement evaluation with overrides and trials.

    Metering → billing

    Usage events into rated subscriptions and invoice runs in iShield One, where implemented and configured.

    Per-tenant residency

    Each tenant can be assigned a region where available, with policy rules against cross-tenant access.

    Per-tenant audit

    Customer-deliverable audit stream scoped to a single tenant.

    Roles

    • ISV or MSP CTO

      Owns the multi-tenant platform

    • Platform administrators

      Provision tenants and set their policies

    • Product and commercial teams

      Define plans and entitlements

    • Finance team

      Bills usage and recognises revenue

    • Compliance team

      Answers tenant audit and control requests

    What it composes

    Modules included across iShield

    This solution composes capabilities from the platforms below. Each module links to its place in the platform's module index.

    Governance & recovery

    Controls, failures and recovery

    Governance and security

    • Administration rights scoped per tenant
    • Plan and policy changes recorded
    • Tenant activity recorded in its own audit stream

    Failures and recovery

    • A tenant exceeds its plan: Its usage is throttled according to the plan and the event is recorded.
    • Usage cannot be passed to billing: Usage records are kept so the billing run can be completed once the exchange is restored.

    Reference frameworks

    Context only — no certification or conformity statement.

    ISO/IEC 27001 and 27002
    Guidance on separating environments and controlling access.
    ISO/IEC 27701
    Privacy-management guidance where tenants hold personal data.
    Cross-platform boundaries

    Who owns what

    • Link runs the tenant control plane; it does not issue invoices.
    • Subscription billing and revenue recognition stay in iShield One; tenant-scoped controls in iShieldGRC.
    • Exchanges between these platforms depend on how they are implemented and configured.
    Business outcomes

    What changes

    • One tenant model reused across products
    • Usage that reaches billing without manual reconciliation
    • Tenant audit evidence ready when customers ask

    Bring Multi-Tenant SaaS Enablement to your enterprise

    Discuss how this solution fits your integration estate, and the phased delivery and deployment options for your environment.

    Your privacy choices

    We use strictly necessary storage to run this website. With your permission we also use first-party analytics to understand which pages are useful. Analytics stays off unless you choose "Accept all" or turn it on in "Manage". You can change your choice at any time from "Cookie settings" in the footer. See our Privacy Policy.