Deployability

Does the BDB Platform have support for multi-tenant deployments in a Customer managed SaaS environment?

Yes, the BDB platform supports multi-tenant deployment in a Customer managed SaaS environment.

Does the BDB Platform support private cloud and on-premises deployments?

Yes, the BDB platform is cloud agnostic and can be deployed on private clouds and on-premises.

Does the BDB Platform support full white-label deployments with Customer branding?

BDB Platform supports white-labeled deployments. Branding can be applied on Images/Icons (Logo image, Favicon, Carousel images, Background images), text (description, App title, Copy Right, etc.) Styles (Icon color, Text color, Border color, and Fonts ).

Does the BDB Platform, when deployed in a multi-tenant manner support white labelling on a per-tenant basis?

This can be achieved via deploying different UI containers for tenants and routing.

Is the BDB Platform 100% web-based? Please describe any functions that would require a desktop application to either configure or perform.

Yes. BDB platform is 100% web based. It doesn’t have any thick client therefore it doesn’t require a desktop application.

What web browsers are currently supported?

BDB platform is certified on Google Chrome, Microsoft Edge, and Safari.

Describe what the OS (operating system) requirements are for the BDB Platform.

BDB Platform is fully containerized and deployed on Kubernetes.

Please describe deployment capabilities and APIs that support automation of deployment and scaling (Dockerization and Kubernetes support).

BDB Platform is fully containerized and deployed on Kubernetes. Deployment is done via helm chart and automated with flux cd and terraform. Scaling is achieved using Kubernetes's HPA.

Does the BDB Platform support Black Hole deployment (installation without an internet connection)?

Yes, the BDB Platform can be installed without internet support. Container images can be shipped as tar files using docker save.

Describe the automation capabilities for the automatic deployment of pre-configured dashboards to tenants with different data sources. Explain the process for connecting a pre-defined dashboard to a new data source and if this can be automated.

We provide API support to pull the dashboard metadata from the pre-configured Git location and push it to a new tenant with new data source information, or data source information can be pulled from Kubernetes secrets configured for the tenant. This process can be entirely automated via scripting.

Please describe the BDB Platform monitoring and management capabilities including operational logging and alerting capabilities.

BDB Platform provided centralized logging and monitoring Via FluentD as middleware.

Please describe if porting the Data Model and other Configurations to other Tenants/Environments is Possible. If Yes, Please elaborate on the high-level steps.

We have a migration feature in the platform using which metadata can be migrated from one tenant to another or from a tenant in Dev/QA instance to one or more tenants in the Production instance. This is achieved via a common Git Branch. We provide the ability to push Visualization and associated dependencies like data connectors and data service in a single click to a Git Branch and from there it can be migrated/pulled to multiple tenants. The entire process can be automated via APIs & scripts.

What are the hardware deployments for both a single-tenant premise deployment and a multi-tenant cloud deployment?

Below is the minimum hardware requirement for BDB Visualization (Dashboard + Self Services Reporting)