SaaS Tenant Management › Tenant Provisioning & Lifecycle

Tenant Provisioning & Lifecycle

BC-4230.10 Level 2 Software & Technology 129 providers 157 API surfaces 73 rated strong or better

Creation, suspension, decommissioning, and migration of tenants in the multi-tenant fleet.

Tenant Provisioning & Lifecycle (BC-4230.10) is a level-2 business capability under SaaS Tenant Management in the Software & Technology model. The catalog holds 157 API surface(s) from 129 provider(s) that can perform some part of it, 73 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Tenant Provisioning BC-4230.10.10

Creation of new tenants and allocation of associated resources.

no catalog coverage

Tenant Suspension BC-4230.10.20

Suspension of tenants for non-payment, abuse, or contractual reasons.

no catalog coverage

Tenant Decommissioning BC-4230.10.30

Decommissioning of tenants including data deletion or hand-back per contract.

no catalog coverage

Tenant Migration BC-4230.10.40

Migration of tenants between clusters, shards, or regions.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 27 Complete, well-documented, and agent-ready
Strong 46 Solid coverage with minor gaps
LaserDataTenants1 API66.2Spectro Cloudtenants1 API65.9LyticsAccount1 API65.8OpenworkOrganizations1 API65.6GraphiantEnterprises1 API65.2Benchmark EmailSub Account1 API65.1VisierConsolidatedAnalyticsTenantsV1TenantsV23 APIs65.0Logz.ioManage time-based log accounts1 API64.5ValimailAccounts1 API64.5MOLOCOWorkplace1 API64.1Cisco Catalyst SD-WANMultitenant APIs - ProviderTenant ManagementTenant Migration3 APIs63.8Koyeborganization1 API63.6Go1Portals1 API63.5Firma.devWorkspaces1 API63.3HookdeckTenants1 API63.2Cisco UmbrellaProviders1 API62.7Wherobotsorganization1 API62.7Numbers OnlineMSP1 API62.0KentikTenantService1 API61.9ReputationTenants1 API61.9MistMSPs Orgs1 API61.8WorkOSorganizations1 API61.4ThingsBoardtenant-controller1 API61.3PropelAuthOrganizations1 API61.2ArthurAITenant Signup1 API60.3Integration.app (Membrane)OrgWorkspaces1 API60.3Commerce Layerorganizations1 API59.9KnockTenants1 API59.7SynthflowSubaccounts1 API59.7TykOrganisations1 API59.6FusioTenant1 API59.4Tandoor RecipesEnterprise Space1 API59.4Transmit SecurityOrganizations1 API59.3LaterInstanceDeactivationInstanceReactivation2 APIs59.2FronteggAccount HierarchyAccount MigrationAccountsSub-accounts7 APIs58.8Juniper NetworksMSPs Orgs1 API58.7DealHubTenant1 API58.5AppDirectTenant Marketplace Provisioning1 API58.1ChromaTenant1 API57.9HatchetTenant1 API57.9Altimate AICompany1 API57.6FOLIOTenantTenantsproxy-tenanttenant-controller4 APIs57.6Cisco Secure FirewallProvision1 API57.0NileTenants1 API56.1Impossible CloudPartners1 API55.2ParchaAdmin1 API54.5
Developing 41 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 1 Early or largely undocumented
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Tenant Provisioning & Lifecycle. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →