GoRules Version 2 is here - redesigned, now with managed cloud.GoRules Version 2 is here!
Watch the launch videoWatchEncode your credit policy in visual decision tables, evaluate every application in milliseconds, and return approve, decline, or refer with the exact rules that fired. Keep your loan origination system; GoRules replaces the hard-coded logic inside it.
Watch a morning in a lending team: a strong borrower declined on payment math, a one-cell policy change, a replay over 2,140 declined applications, a signed release - and declines that come back as offers.
scroll to playLN-3092: personal loan, $28,000 over 36 months, income verified, clean file. The payment math is about to decline it.
At 36 months the payment is $912 and DTI hits 0.46 - over the 0.43 cap. At 60 months it would be 0.41. The policy has no way to say so.
The failing rule opens the live policy. On a branch, over-cap applications that fit at a longer term now counteroffer instead of declining - approvals untouched.
Ninety days of declined applications replay against the draft while you watch: 312 come back as counteroffers, zero extra approvals, over-cap-at-every-term still declines.
Priya Shah signs the release, it promotes through staging to production with the full trail recorded. Rollback stays one click away.
LN-3092 flips to a counteroffer: $28,000 over 60 months. Across the queue, affordability declines convert - except the one over cap at every term.
Ask where loan decisioning happens in your stack and you will usually get three answers at once: rules hard-coded inside the LOS, a spreadsheet the credit team maintains, and a vendor scorecard nobody can inspect. Loan decisioning software is supposed to put that logic in one governed place; most lenders never get there. So changing a score floor or a DTI cap means a ticket, an engineering sprint, and a release window - a policy change that should take an afternoon stretches into weeks.
The fix the market offers is worse than the problem. Loan origination software vendors sell better decisioning as the reason to migrate everything, application intake, documents, verification, and funding included, onto their platform. That is a rip-and-replace project to solve what is really a rules problem.
Meanwhile the questions that matter go unanswered. Why did this application decline, specifically? What happens to the approval rate if we tighten the DTI cap to 43%? Who changed the pricing grid last quarter, and who approved it?
When the answers live in code and tribal knowledge, every exam, audit, and policy review is slower and riskier than it needs to be.
GoRules is the loan-specific application of our credit decision engine: application in, priced decision out, every step readable.
Model the whole decision as a graph. Knockout rules run first as a decision table: state eligibility, minimum score, bankruptcy recency, fraud flags. Affordability follows, with DTI and residual-income calculations written in ZEN expressions or typed TypeScript function nodes, then a pricing grid maps score band and DTI to APR. The result is one structured decision: approve with stipulations, counteroffer, decline with reasons, or refer to review.
Clear approvals and clear declines go straight through. Borderline applications route to a human underwriter with the triggering rules attached, so reviewers see exactly why the case referred instead of re-working it from scratch. Conditional approvals carry their stipulations, such as proof of income or employment verification, in the decision payload your LOS consumes.
Credit and risk teams edit decision tables directly, and natural-language rendering makes each rule read the way the policy document does. Git-like versioning, approval workflows, and one-click rollback mean risk signs off before anything reaches production. Run a change through the simulator with real application data before it ships.
No data migration: the LOS keeps owning applications, documents, and funding. GoRules owns the decisions inside that workflow.
Call GoRules over REST from your LOS or point-of-sale flow, or embed the MIT-licensed open-source ZEN Engine in your own service with SDKs for Node.js, Python, Java, Go, C#, and Rust.
Rebuild your policy as decision tables and graphs: knockout screens, affordability math, pricing tiers. Bureau attributes, bank transaction data, and scorecard or ML model outputs enter as plain inputs, so the final decision stays deterministic and reviewable even when a score is not.
Branch a change, test it in the simulator with real application data, and trace execution through every node. Promote through dev, staging, and prod with an approval recorded at each step.
Every evaluation returns the outcome plus the exact rules that fired, ready to feed your adverse action process. Iterate weekly instead of quarterly, and roll back in one click if a change misbehaves.
Loan decisioning software evaluates a loan application against a lender's credit rules and returns approve, decline, or refer to review, with the specific reasons, in real time. It is the decision layer of origination: the LOS manages intake, documents, and funding, while the decisioning engine determines who qualifies, on what terms, and why.
No. A loan origination system (LOS) runs the pre-funding workflow: application intake, document collection, verification, e-sign, and disbursement. GoRules handles only the decisions inside that workflow, from instant prequalification to full loan underwriting, and your LOS calls it over REST wherever a decision is needed.
Every decision returns the exact rules that fired, so a decline arrives with its specific principal reasons rather than an opaque score. You map those reasons to the language in your adverse action notices under ECOA and FCRA. GoRules supplies the traceability; the compliance obligations and notice content remain yours.
Yes. Decision tables are edited visually, natural-language rendering keeps them readable for business users, and GoRules AI can draft rule changes, run tests, and explain decisions. Every change goes through approval workflows and versioned promotion, so nothing reaches production without sign-off, and any change rolls back in one click.
Yes. Deploy GoRules with Docker or Kubernetes inside your own environment, so applications, bureau attributes, and decision logs never leave your network. SSO and role-based access control govern who can view or change rules. GoRules Cloud is available if you prefer managed hosting.
One decision layer serves the whole institution - these use cases run on the same tables, versioning, and audit trail.
Model your first lending ruleset in the visual editor today, or walk us through your loan decisioning stack and we will map the integration.
