Deploy & operate

How do I run the platform?

Platform and DevOps teams running a CluedIn installation.

Everything a platform team does to a CluedIn installation: choosing a deployment model, installing it, configuring the cluster, upgrading it, backing it up, watching it, and keeping its cost and security in order.

Product administration - users, roles, UI configuration - is Administer.

In this section

  • Architecture overview concept
  • Queues in CluedIn concept
  • Deployment optionssectionCluedIn runs as a managed SaaS service, as a private SaaS or PaaS deployment in your own Azure subscription, or locally for development.
  • Azure deploymentsectionDeploying CluedIn into your own Azure subscription: the cluster, the network, the certificates, the storage, and the Helm release that installs the platform onto them.
  • Azure MarketplacesectionInstalling CluedIn from the Azure Marketplace, including the decisions to make and the checks to run before and after the managed application is deployed.
  • Local deploymentsectionRunning CluedIn on a single machine for development and evaluation, including how to add extension packages and how to upgrade it.
  • ConfigurationsectionConfiguring a deployed installation: how you connect to it, how it authenticates people, how it reaches the network, and how it stores and secures its data.
  • External identity providerssectionCluedIn signs people in through Microsoft Entra, and Entra can federate other identity providers such as Okta, Auth0 or Google Workspace, so people keep using the account they already have.
  • UpgradesectionHow to upgrade a CluedIn installation, and what each release requires.
  • Backup and restoresectionProtecting an installation and getting it back.
  • MonitoringsectionWatching a running installation: the Engine Room shows what the platform is processing right now, and Log Analytics holds the detail when you need to go back through it.
  • SecuritysectionThe security posture of a CluedIn installation, how to restrict access to individual components, and CluedIn's response to publicly disclosed vulnerabilities.
  • Cost and scalingsectionWhat drives the cost of a CluedIn installation and what you can safely turn down or off when you do not need it.
  • Day-to-day operationssectionThe recurring operational tasks: promoting configuration between environments, resetting an instance, migrating the database, and knowing what CluedIn support covers.

Table of contents

  • Architecture overview
  • Queues in CluedIn
  • Deployment options - CluedIn runs as a managed SaaS service, as a private SaaS or PaaS deployment in your own Azure subscription, or locally for development.
  • Azure deployment - Deploying CluedIn into your own Azure subscription: the cluster, the network, the certificates, the storage, and the Helm release that installs the platform onto them.
  • Azure Marketplace - Installing CluedIn from the Azure Marketplace, including the decisions to make and the checks to run before and after the managed application is deployed.
  • Local deployment - Running CluedIn on a single machine for development and evaluation, including how to add extension packages and how to upgrade it.
  • Configuration - Configuring a deployed installation: how you connect to it, how it authenticates people, how it reaches the network, and how it stores and secures its data.
  • External identity providers - CluedIn signs people in through Microsoft Entra, and Entra can federate other identity providers such as Okta, Auth0 or Google Workspace, so people keep using the account they already have.
  • Upgrade - How to upgrade a CluedIn installation, and what each release requires.
  • Backup and restore - Protecting an installation and getting it back.
  • Monitoring - Watching a running installation: the Engine Room shows what the platform is processing right now, and Log Analytics holds the detail when you need to go back through it.
  • Security - The security posture of a CluedIn installation, how to restrict access to individual components, and CluedIn's response to publicly disclosed vulnerabilities.
  • Cost and scaling - What drives the cost of a CluedIn installation and what you can safely turn down or off when you do not need it.
  • Day-to-day operations - The recurring operational tasks: promoting configuration between environments, resetting an instance, migrating the database, and knowing what CluedIn support covers.