Skip to main content

Deployment Options

Witboost offers flexible deployment models that keep you in full control of your infrastructure and data.

Deployment Architecture​

Witboost is a container-based microservices platform deployed on Kubernetes. All components run within the customer's own infrastructure.

Requirements​

ComponentRequirement
Container OrchestrationKubernetes (any distribution: AKS, EKS, GKE, OpenShift, Rancher, vanilla K8s)
DatabasePostgreSQL
Source ControlGit (GitLab, GitHub, Azure DevOps, Bitbucket)
Identity ProviderOAuth2/OIDC compliant (Entra ID, Okta, Keycloak)
AI Backend (optional)OpenAI-compatible API endpoint (Azure OpenAI recommended)

Deployment Models​

On-Premises​

┌─────────────────────────────────────────────────┐
│                 Customer Data Center            │
│                                                 │
│  ┌──────────────┐  ┌──────────────────────────┐ │
│  │  Kubernetes  │  │  Customer Data Platform  │ │
│  │  ┌─────────┐ │  │  (Snowflake, Databricks, │ │
│  │  │Witboost │ │  │   Spark, etc.)           │ │
│  │  │Platform │◄├──┤                          │ │
│  │  └─────────┘ │  └──────────────────────────┘ │
│  │  ┌─────────┐ │  ┌──────────────────────────┐ │
│  │  │  Tech   │ │  │   Identity Provider      │ │
│  │  │Adapters │ │  │   (Entra ID / Okta)      │ │
│  │  └─────────┘ │  └──────────────────────────┘ │
│  └──────────────┘                               │
│                                                 │
│              No outbound traffic                │
└─────────────────────────────────────────────────┘
  • Complete data sovereignty — Everything runs within your network perimeter
  • Air-gapped support — Container images can be mirrored to an internal registry
  • No external dependencies — Platform operates without any internet connectivity

Private Cloud​

Same architecture, deployed in the customer's cloud tenant (Azure, AWS, GCP):

  • Customer controls the region and availability zone
  • Integration with cloud-native services (managed PostgreSQL, Key Vault, etc.)
  • Network policies and firewalls managed by the customer

Hybrid​

  • Witboost Control Plane in one location
  • Tech Adapters deployed close to the target technologies
  • External communication between deployment boundaries is protected with TLS 1.2+

No Agile Lab Infrastructure​

Unlike SaaS platforms, Witboost requires no Agile Lab-hosted infrastructure:

  • No Agile Lab servers
  • No Agile Lab databases
  • No Agile Lab-managed network endpoints
  • Everything runs on your infrastructure, under your control

Installation & Upgrades​

PhaseDetails
Initial InstallationHelm charts or Kubernetes manifests
UpgradesNew container images deployed via standard Kubernetes rolling updates
PatchesSecurity patches available outside the regular release cycle
RollbackStandard Kubernetes rollback procedures apply

Upgrade Compatibility​

Releases follow compatibility principles designed to minimise upgrade disruption:

  • Minor and patch releases are designed to avoid breaking changes
  • API contracts follow semantic versioning — no breaking changes within a major version
  • Customer-specific configurations are preserved or migrated through provided tooling when upgrade steps are required
  • Breaking changes, deprecations, and manual migrations are documented with support guidance

Infrastructure Security​

The customer's infrastructure team manages:

  • Network segmentation and firewall rules
  • Kubernetes cluster hardening
  • Node OS patching
  • Storage encryption configuration
  • Backup and disaster recovery

Agile Lab provides best-practice guidance for secure Kubernetes deployment and can assist during initial setup.