Deployment and Administration

Deployment Options

   View as Markdown

KanBo can be deployed in four secure configurations.
Each offers full data sovereignty and compliance with enterprise or government standards.

Deployment ModelDescriptionTypical Use Case
Azure Cloud (Microsoft 365)KanBo is installed within your organization’s Azure tenant. All compute, storage, and access control remain under your Azure subscription.Global enterprises using Microsoft 365 or Azure AD-based identity and seeking cloud scalability with complete control.
On-PremisesKanBo runs entirely within your internal infrastructure using Windows Server and SQL Server, optionally integrated with SharePoint (Add-In Model).Highly regulated sectors such as public institutions, healthcare, energy, and defense with strict internal data retention requirements.
GCC High CloudKanBo is hosted within Microsoft’s Government Community Cloud (GCC High) and meets FedRAMP High and DFARS compliance requirements.U.S. Government contractors, aerospace, defense, and federal agencies.
HybridCombines local data residency with cloud collaboration and synchronization.Organizations transitioning to the cloud or operating across multi-region environments.

Core Infrastructure Stack

  • Windows Server (2019+)
  • .NET 8 Runtime
  • Microsoft SQL Server or Azure SQL Managed Instance
  • Azure AD Authentication
  • Optional SharePoint Add-in integration (HighTrust model)

Deployment Blueprint

For Azure installations, KanBo components typically include:

  • Azure App Service (Frontend)
  • Azure Function Apps
  • Azure SQL Managed Instance
  • Azure Storage Account
  • Azure Search or dedicated Elasticsearch VM
  • Optional: Azure Application Gateway + Firewall Premium
    (see help.kanboapp.com)

KanBo’s architecture ensures that no service, log, or data ever leaves your tenant.