Legacy BRMS are slow to change.
A risk team writes a rule. Engineering writes a JIRA. Six weeks later, an appliance ships. By then the policy is wrong, the consultant is paid, and the deal is dead.
Cerebra is a modern BRMS — author business rules as visual decision graphs, version them like code, and serve them from a managed API at single-digit-millisecond latency. The decision engine your risk team and your engineers both like.
A risk team writes a rule. Engineering writes a JIRA. Six weeks later, an appliance ships. By then the policy is wrong, the consultant is paid, and the deal is dead.
The policy doc says one thing. The Python service does another. The Excel sheet underwriters actually use does a third. No one knows which one decided.
“Why did you decline this customer on March 4th?” The honest answer involves a deploy log, a deleted branch, and a developer who left in May.
Compose SwitchRules, decision tables, and Compute nodes in the browser. CEL expressions for predicates – sandboxed, fast, familiar to anyone who has touched Kubernetes.
Cerebra compiles the graph to an in-memory program, hashes it with SHA-256, and writes the result to an append-only registry. A reviewer signs off. The pointer flips.
Your service POSTs JSON. Cerebra resolves the live registry, runs the program lock-free, returns a decision and the exact node path that produced it. Every call is recorded.
| Capability | Cerebra | IBM ODM | FICO Blaze | DIY service |
|---|---|---|---|---|
| Authoring | Visual graph + CEL | Eclipse-based BOM tooling | Excel + proprietary DSL | Whatever you can ship in a quarter |
| Deployment | Managed SaaS, multi-region | WAS appliance | On-prem appliance | Your monorepo |
| Versioning | SHA-256, atomic swap | Project import/export | Manual snapshots | git tag, fingers crossed |
| Audit trail | Per-call, append-only | Add-on module | Add-on module | You’ll get to it |
| P99 latency | ~4 ms | up to 250 ms | up to 80 ms | Depends on the intern |
| Runtime | Rust, no JVM | JVM, proprietary | JVM, proprietary | JVM, proprietary |
| Pricing posture | SaaS · usage-based · $499/mo | $1M+ & consultants | $500K+ license & SI | Headcount |
| First rule shipped | An afternoon | Two quarters | One quarter | “Q3, maybe Q4” |
Lending, KYC, fraud, claims, eligibility. The decisions auditors care about most are the ones engineers have the least time to instrument.
Single static binary. No JVM, no proprietary runtime, no agent.
Battle-tested, replicated, point-in-time recoverable. The boring choice, on purpose.
One POST /api/evaluate .JSON in, decision out. Drop in.
Multi-region by default. Dedicated single-tenant regions on Enterprise. No infra for you to run.
Map your existing groups to author / reviewer / publisher.
Programs are in-memory; evaluations are lock-free atomic reads.
A SwitchRule is a SwitchRule whether it routes a loan or a claim. Pick an industry — see the graphs Cerebra is built to run.
Pull bureau and income, tier the applicant, route to instant-approve or manual review. 47 rules. One graph. Underwriters edit it themselves.
Velocity, device, geo, merchant category, and a model score. Six branches, two outcomes — pass or hold for review. Every threshold is a version.
Geography, age, occupation, coverage limits. The graph reads like the underwriting manual — because the underwriting team wrote it.
No SDK to vendor. No DSL to learn. No agent to install. POST a payload, read a decision. The reverse-loop is the same — push a graph, get back a version hash.
docker run cerebra/dev on your laptop.
$ curl -X POST https://api.cerebra.io/v1/evaluate \
-H "Authorization: Bearer $CEREBRA_KEY" \
-H "Content-Type: application/json" \
-d '{
"graph": "policy.loan.origination",
"input": {
"applicant": { "income": 92000, "dob": "1989-04-12" },
"bureau": { "fico": 742, "delinq_24m": 0 }
}
}'
{
"decision": "approve",
"tier": "prime",
"fired_node": "tier.route#3",
"node_path": ["applicant", "tier.route", "approve"],
"version": "3.14",
"program_sha": "9f4ea201bc54…",
"latency_ms": 3.4
}
No per-seat tax on your risk team. No five-figure procurement to ship one rule. Pay for evaluations and graphs — the things that actually scale with your business.
For teams shipping their first decisions in production.
For production at scale, with the controls auditors ask for.
For regulated workloads, dedicated regions, and named support.
All plans · SOC 2 Type II · OpenTelemetry on every call · Region: us-east, eu-west, ap-south
A 30-minute call. We bring a real graph. You bring a hard one. We’ll show you exactly what you’d build, deploy, and instrument by Friday.
cerebra@cerebra.io · SOC 2 Type II · ISO 27001 (in progress)