Roadmap
Ordo started as a fast rule engine. The direction now is a business rule layer: people or AI write the rules, and Ordo tests them and shows what a change affects.
Phase 1: Foundation
v0.1 → v0.2 Completed- Core Rule Engine (Rust)
- HTTP & gRPC API Server
- Visual Rule Editor (Vue 3 + React)
- WASM Browser Execution
- Execution Tracing & Debugging
- JIT Compilation (Cranelift)
- Audit Logging & Version History
- Distributed Deployment (NATS JetStream)
Phase 2: Intelligence
v0.3 → v0.4 Completed- Data Filter API (SQL / JSON / MongoDB push-down)
- Partial Evaluation Engine
- Compiled Ruleset (.ordo binary format)
- Multi-tenant QPS Isolation
- Enterprise Plugin System
Phase 3: Rules people and AI can write
Shipped Completed- Ordo Guard: deterministic guardrails for coding agents
- Exact decimal type for money
- Declared input schema (invalid input is rejected)
- Expression strings in assignments and outputs
- Engine-native decision tables (first / collect hit policies)
- ordo impact: see which decisions an edit changes
- MCP server so agents can test and check their own edits
Phase 4: Ecosystem
Next In Progress- Reusable rule packs (credit approval, promo stacking, fraud scoring)
- Decision table steps in the Studio visual editor
- Sharing rule packs between teams
- Published Go / Python / Java SDKs
- Collaborative editing
- Kubernetes native operator
Start from a ready-made example
Jev refund routing, credit approval, promo stacking and fraud scoring, already written. Copy one and change it to your own policy.