What we can evidence, and what needs an agreement
Controls, data boundaries, and deployment scope differ by product and by configuration. This page states which commitments exist today and which ones are made per engagement, so nobody plans against an assumption.
Read this before you plan around it
- No portfolio-wide SOC 2, ISO, or HIPAA certification is claimed for Bahulam, CoDash, or OneAdmin. Where a scoped attestation exists for a product, the technical review names it and its scope.
- Data residency, single sign-on, private-cloud deployment, training-data exclusion, and immutable audit are deployment-specific. They are agreed per engagement, not promised across the portfolio.
- The three products are siblings under one company. That relationship does not establish shared authentication, interoperable product state, a common runtime, or universal governance between them.
- Model providers differ by product and configuration. Which providers process which data is stated for the configuration you are evaluating.
- Capability status on this site distinguishes what exists in the product source from what a product owner has released. Ask for the current matrix before planning against it.
Scope by product
Bahulam
Full capability matrixBahulam includes BI domain workspaces. CoDash is the specialist offer for modernising a BI estate. They are sibling products; no shared runtime, authentication, or product state is claimed between them.
Not available today
- PlannedPublish agent-task benchmark results with a reproducible methodology
CoDash
Full capability matrixMigration is directional and asset-scoped. CoDash does not convert any BI platform to any other; each supported path states its source, target, asset types, and unsupported constructs.
Not available today
- PlannedDeploy as a dedicated hosted tenant or into a customer cloud
- PlannedManage the whole estate as a governed asset portfolio
OneAdmin
Full capability matrixInspection and request preparation are implemented against admitted assets and uploaded snapshots. The approval and execution interaction on this site and on the product site is a simulated preview; unified execution across systems is planned, not shipped.
Simulated, not enforced
- Interactive preview — simulated executionInspect a proposal and exercise approval, rejection, hold, and policy denial
Not available today
- PlannedApprove once and execute across connected systems
- PlannedTrace dependencies across connected systems
What a technical review covers
Capability and scope
The product capability matrix, supported inputs and outputs, the limits, and when each capability was last demonstrated.
Data flow
Source systems, application services, model providers, artifacts, logs, and retention boundaries for the specific configuration.
Identity and permissions
Tenant and environment scope, secrets handling, and which responsibilities stay with a person for each product.
Deployment
The supported configurations, and who operates backups, upgrades, monitoring, and incidents in each of them.
Evaluation and rollout
The evaluation plan, acceptance measures, sample artifacts, rollout and handover plan, and the support scope that follows.
Documents
The contractual and security documents that exist, each with a named owner and its actual status.
How to read the status labels
- Source-backed
- The implementation exists in the inspected product source. It has not been demonstrated end to end here.
- Demonstrated
- A dated end-to-end run supports this capability, with environment, inputs and outputs recorded.
- Available
- A product owner has approved this capability for a stated customer scope and operating model.
- Interactive preview — simulated execution
- An illustrative interface or synthetic simulation. No live backend behaviour is implied.
- Planned
- Roadmap work. A component, route or partial API may already exist; the capability does not.