AI work platform
Bahulam
Connected intelligence for real work.
- Who buys it
- Engineering leaders, builders, and teams adopting AI workflows
- The job it addresses
- Bring conversations, coding, tools, and domain workspaces around the task a team needs to complete.
- What you end up with
- Reviewable work — a change, a check, and a human decision — rather than a transcript.
- Where it stops
- Bahulam 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.
Next step
Bahulam connects AI conversations, coding, tools, and workspaces so teams can produce and review real work. Chat, Bahulam Code, workspaces, workflows, mobile, and plugins are surfaces of one platform.
Plans and pricing live on the product site, where they stay current.
The workflow, end to end
Input, action, artifact, human review, outcome — and an honest account of how far the evidence currently goes.
A scoped repository change, reviewed by a person
Bahulam Code CLI — binary `bahulam`, package `@bahulam/code` · inspected 2026-09-26
- 1
Input
A scoped task against a repository the team already owns.
- 2
Action
The agent plans the change, edits files, and runs the repository's own checks.
- 3
Artifact
A diff and the output of the checks that actually ran.
- 4
Human review
An engineer reads the diff and the check output and decides whether to accept it.
- 5
Outcome
An accepted change, or a rejected one with the failure visible.
What this supports
- Bahulam Code exists as a released CLI with a published package name.
- The platform is organised around producing a reviewable artifact rather than a transcript.
What this does not support
- Any success rate, acceptance rate, or time saving.
- That the agent completes tasks without human review.
Recording still owed
A dated 60–90 second recording of one real scoped task: the request, the changed files, the checks that ran, the human review, and the limitations that remained.
What it does today
Status is per operation and per platform, because that is the level at which it actually varies. A route existing in the product is not the same as a product owner releasing it.
| Operation | Platform scope | Status | Limitations |
|---|---|---|---|
| Run a scoped repository task and produce a reviewable change | Bahulam Code CLI (binary `bahulam`, package `@bahulam/code`) | Source-backedreviewed 2026-09-26 |
|
| Work across Chat, Code, Cloud IDE, workspaces, workflows, mobile, and plugins | Bahulam platform surfaces | Source-backedreviewed 2026-09-26 |
|
| Publish agent-task benchmark results with a reproducible methodology | Bahulam evaluation harness | Plannedreviewed 2026-09-26 |
|
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.
The other two products
CoDash
Modernise your BI estate.
Understand what exists across the BI estate, decide what matters, migrate selected assets, and build and validate reporting.
CoDash in detailOneAdmin
Administration with clear authority.
Inspect enterprise administration context and route agent proposals to the administrator who is accountable for the decision.
OneAdmin in detail