What is Dxn?
Dxn (short for decision) is a hosted decisioning engine with a simple API. You define your business rules — pricing tiers, approval logic, eligibility criteria, routing conditions — and Dxn evaluates them in milliseconds against any data you send it.
No infrastructure to manage. No code required to update your rules. Just an API call.
Dxn is built on top of goRules — an open-source business rules engine used by teams at Fortune 100 companies. goRules provides the evaluation engine and the visual rule editor. Dxn wraps it with a managed API, versioned policy storage, and authentication, so you get enterprise-grade decisioning without any of the infrastructure.
Who It's For
Dxn was built for the people who traditionally had to bolt decisioning onto tools that weren't designed for it.
No-code builders who've run out of if/then branches in their automation tool. Dxn offloads all that conditional logic into a purpose-built system, keeping your workflows clean and readable.
Vibe coders and indie hackers who ship fast and hate coming back to untangle logic buried in old code. Define your rules once in Dxn, call the API from anywhere, and change the rules without touching your codebase.
Entrepreneurs and operators who own the business logic but don't own the codebase. Dxn gives you a no-code editor to build and update your own rules — without filing a ticket or waiting for a developer.
What You Can Do With It
Dxn is a good fit for any decision that follows rules your business controls:
- Pricing logic — tiers, discounts, dynamic quotes
- Eligibility and approvals — loan decisions, access control, waitlist criteria
- Routing and escalation — which team handles this request, which SLA applies
- Scoring and classification — risk tiers, lead quality, customer segments
If the decision can be written as a rule, Dxn can evaluate it.
Start from a Template
You don't have to build from scratch. goRules maintains a library of 80+ ready-made decision templates covering common use cases across industries. Open any template in the goRules editor, customise it to fit your rules, then upload it to Dxn as a policy.
A few examples to give you a feel:
| Template | What it does |
|---|---|
| Dynamic Airline Ticket Pricing | Sets ticket prices based on time to departure, seat availability, and demand |
| Seller Approval Workflow | Evaluates marketplace seller credentials, inventory, and background checks |
| Loan Approval | Scores credit, income, and debt ratios to determine mortgage eligibility |
| Real-Time Fraud Detection | Flags suspicious transactions using location, spend patterns, and behaviour |
| Patient Triage System | Prioritises ER patients based on vital signs and symptoms |
| Insurance Premium Calculator | Prices policies based on driver profile, vehicle specs, and coverage |
Browse the full library at gorules.io/templates.
How It Works
1. Build your rules in the goRules editor
GoRules provides a free visual editor where you model your decision logic as a JDM (JSON Decision Model) — an open standard that represents rules as a graph of nodes: inputs, outputs, decision tables, functions, and more. No code required. Drag components onto a canvas, connect them, and test with real data before you deploy.
You can also write JDM files by hand and upload them directly.
2. Host your rules as a policy
Upload your JDM file to Dxn via POST /policies. Dxn stores it as a versioned policy — a named, callable ruleset with its own ID. Iterate freely, roll back to any previous version, and manage as many policies as you need.
Code
3. Run decisions against it
Send a POST /decisions request with your policy ID and the input data you want to evaluate. Dxn runs the rules and returns the result in milliseconds.
Code
The result comes back as structured JSON — ready to use in your app, automation tool, or workflow.
Code
You can also retrieve any past decision by ID with GET /decisions/{decisionId}, giving you a full audit trail of what inputs produced what outcome.
Why Not Just Use Code, AI, or Automation?
Rules that live in code are hard to change without a deployment. Rules in AI are probabilistic — you can't guarantee the answer. Rules in automation tools turn into unmaintainable chains of branches.
Dxn gives you a dedicated place for rules that need to be deterministic, updatable, and separated from your application logic.
Large enterprises have had dedicated decisioning systems for years. Dxn makes the same capability available to anyone building a product.
See What is Decisioning? for a deeper explanation of how decisioning differs from automation and AI.