BILifeCycleTalk to us
Home

Deployment paths

Run BILifeCycle as SaaS or inside your own cloud network.

The product supports two clear adoption models: a dedicated hosted tenant for speed, or a customer-controlled deployment inside Azure, AWS, or GCP for private-network requirements.

2Deployment paths3Major clouds1Lifecycle platform

BILifeCycle hosted SaaS

SaaS tenant

A dedicated BILifeCycle tenant for the client, operated as SaaS with tenant-level isolation, managed updates, and faster onboarding.

Dedicated tenantManaged hostingTenant-scoped access

Best for

Teams that want a faster start, managed platform operations, and a clear tenant boundary without deploying infrastructure in their own cloud.

Included

  • Client-specific tenant, users, roles, workspaces, and operating configuration
  • Managed application updates, platform maintenance, and product release cadence
  • Tenant-level workspace separation for platform analysis, migration, development, and management
  • Secure connectivity pattern for approved BI platforms, databases, and source systems

Customer owns

  • Identity users and approval workflow
  • Source system credentials and connectivity approvals
  • BI estate scope, data access policy, and workspace governance

Deploy inside your network

Client cloud deployment

Run BILifeCycle inside the client's own cloud and network boundary, with deployment options for Azure, AWS, or GCP.

AzureAWSGCPPrivate network

Best for

Organizations that need private-network execution, cloud-account control, regulated data handling, custom network routes, or strict platform ownership.

Included

  • Deployment into the client's cloud account, VPC/VNet, routing model, and security controls
  • Private connectivity to BI platforms, databases, warehouses, source systems, and identity providers
  • Environment-specific configuration for storage, secrets, logs, queues, jobs, and service endpoints
  • Workspace, migration, analyzer, automation, and management services running inside the client boundary

Customer owns

  • Cloud account, network controls, security groups, and private endpoints
  • Identity provider, key management, secrets policy, and audit destinations
  • Infrastructure approval, change management, backup, and compliance process

Decision guide

Pick the path that matches your security and operating model.

The lifecycle capability is the same. The decision is where the application, connectors, logs, secrets, jobs, and network routes should live.

QuestionSaaS tenantClient cloud deployment
Where it runsDedicated BILifeCycle tenant operated as SaaSInside the client's Azure, AWS, or GCP network
Best fitFast onboarding, managed operations, and tenant-level isolationPrivate network, stricter data residency, and cloud-account control
ConnectivityApproved secure connectors to BI platforms, databases, and source systemsPrivate routes, VPC/VNet controls, private endpoints, and local policies
OperationsBILifeCycle manages product updates and platform maintenanceCustomer controls infrastructure, network, audit, and change management

Rollout

Deployment is tied to the first lifecycle pilot.

We do not separate infrastructure from product outcomes. The chosen deployment path is validated by connecting real platforms, running an estate workflow, and proving publish or management follow-through.

SaaS tenant

  1. Provision the dedicated tenant and admin access
  2. Connect identity, BI platforms, databases, and source systems
  3. Configure workspaces, migration paths, and operating roles
  4. Run the first lifecycle pilot and expand by platform or program lane

Client cloud deployment

  1. Confirm cloud target, network topology, security controls, and data residency requirements
  2. Deploy platform services into Azure, AWS, or GCP using the approved environment pattern
  3. Connect BI platforms, data sources, identity, logs, and operating workspaces
  4. Validate end-to-end lifecycle workflows before production rollout

Deployment review

Bring your cloud and security constraints into the first call.

We can map the right path when we know the target platforms, connectivity requirements, identity provider, preferred cloud, and whether BI data must stay inside your own network.

[email protected]Azure - AWS - GCP - SaaS tenant
Contact

Scope a deployment path

Share whether you prefer a dedicated SaaS tenant or a deployment inside your own cloud network.