Deterministic step budget · 2 MB scored in ~3.4 ms · 947-byte edge bundle, no database · Blue/green rollback
See how it compares to ODMPlatform/Decision Manager
Decision Manager is the authoring console — decision-table grid, action-rules editor, ruleflow canvas, tree and template editors — where business and engineering design, test, and govern decision logic before it reaches a runtime. Everything it writes lands in the same governed rule repository the other two consoles read.
Business authors open a grid in a meeting; architects keep hit policies, vocabulary and Git review under one repository. Policy changes ship without a release train.
Get started
No credit card · Trial does not auto-convert · Export anytime
Authoring & governance
Where business and engineering design, test, and govern decision logic.
Capabilities
Real surfaces: table grid, action-rules and ruleflow editors, tree/template editors, pipelines and Git review — from blank artifact to published version without leaving the console.
Decision-table grid, action-rules editor and ruleflow canvas, plus tree and template editors for structured artifacts — with hit-policy evaluation and BAL type validation as you edit.
A version lifecycle with structured diff, Git review (commit summary, drift explain) and rule-aware delivery pipelines — so a change is reviewable before it is published.
AI-assisted authoring and dry-run / test-suite runs, so the effect of a rule change is visible before it is promoted. AI never auto-publishes.
Authoring surface
Decision tables with hit policies, multi-stage ruleflows, AI drafts with mandatory human review, BOM vocabulary, governed promotion into the warehouse, and VS Code when engineers prefer disk — one console, one repository.
Author complex grids with ODM-familiar hit policies, compound conditions and BAL type validation as you type — then compile to multi-key indexes so lookups stay fast as tables grow.
Compose multi-stage flows with gateways and branches on a canvas policy owners can read in a review. Structure and task order stay explicit — no hidden orchestration buried in code.
Draft BAL rules, tables and tests from plain language across multi-provider chains with ordered fallback and content-hash cache. AI never auto-publishes; every draft waits for a person.
Authors write business phrases against a versioned vocabulary — the BOM — not raw field paths. Verbalization, sensitivity flags and publishable grammar keep models and rules aligned.
Draft → review → approved → published with separation of duties, structured diff, Git review and rule-aware pipelines. Published versions feed the decision warehouse for post-hoc explanation.
Pull rule projects to disk as plain JSON, edit with the BAL language server and tests, then push back with the dm CLI — same repository the browser console governs.
Built for both sides of the table
Policy owners change a table in the meeting that decides it. Platform architects get hit-policy honesty, vocabulary versioning, SoD and a path into Git — without splitting Decision Center from Rule Designer.
Business authors
Open the grid, ruleflow or action-rule editor, dry-run the change, and send it through review. AI can draft the first pass; you still own every publish.
Architects & leads
Hit policies, BOM vocabulary, content-hash provenance and pipelines sit in one model. Prefer IDE workflows? VS Code and the dm CLI stay on the same governed path — no shadow rulebase.
In the studio
Draft decision tables and action rules from a plain-language brief in the studio, then review in the real editors and promote under governance — nothing auto-publishes.
Audience
Business analysts and rule authors, working alongside the engineers who own the data model. It is the console a policy owner opens; it is not where production traffic is operated — that is Decision Server.
Migration
In an ODM estate, authoring happens in the Eclipse-based Rule Designer desktop application and governance in a separate Decision Center with its own database schemas. Decision Manager is both, in one browser console over one repository — and for teams who prefer to work in an editor, rule projects can be pulled to disk as plain JSON and edited in VS Code.
Bringing an existing estate across starts with the ODM migration assessment, which reads a Rule Designer or Decision Center export in your browser and inventories what is in it.
Authoring is one of three consoles over the same repository.
Next step
Start a free trial with Decision Manager included, run the zero-signup live demo, or book a meeting with an executive seller on your underwriting, claims or eligibility policy.
No credit card · Trial does not auto-convert · Export anytime