RuleGo

A lightweight, embedded Go rule engine framework that orchestrates business logic through configurable DAG-based rule chains, supporting hot-reload, heterogeneous data source integration, and zero external middleware dependencies.

Evaluated Mar 06, 2026 (0d ago) vlatest
Homepage ↗ Repo ↗ Other go rule-engine workflow orchestration iot edge dag hot-reload low-code
⚙ Agent Friendliness
59
/ 100
Can an agent use this?
🔒 Security
73
/ 100
Is it safe for agents?
⚡ Reliability
70
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
20
Documentation
75
Error Messages
60
Auth Simplicity
78
Rate Limits
65

🔒 Security

TLS Enforcement
85
Auth Strength
72
Scope Granularity
65
Dep. Hygiene
78
Secret Handling
68

Go rule engine framework. Local execution — no remote auth in core. Rule definitions control logic — validate rule sources. Dynamic rule execution can be high risk.

⚡ Reliability

Uptime/SLA
68
Version Stability
72
Breaking Changes
68
Error Recovery
70
AF Security Reliability

Best When

You need a high-performance, dependency-free rule engine embedded in a Go application, especially for edge computing or IoT scenarios where memory and CPU are constrained.

Avoid When

You need a GUI-first, no-code workflow tool or are building in a non-Go language stack without FFI capabilities.

Use Cases

  • Route and transform IoT sensor data at the edge without external middleware
  • Dynamically update business rules (risk scoring, pricing, routing) without application restarts
  • Build low-code workflow automation platforms with reusable component libraries
  • Integrate heterogeneous data sources (HTTP, MQTT, Kafka, TCP) through unified endpoint handling
  • Implement microservice orchestration and API composition pipelines in Go

Not For

  • Teams not working in Go or comfortable embedding a Go library
  • Projects requiring a fully managed cloud rule engine with SLA guarantees
  • Use cases needing complex stateful saga workflows with compensation logic

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
Yes
Webhooks
Yes

Authentication

Methods: none
OAuth: No Scopes: No

No built-in authentication; security is the responsibility of the embedding application. Endpoint integrations inherit whatever auth the upstream data sources require.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

Apache 2.0 open source. Commercial ecosystem (visual editor, server platform) may have separate licensing.

Agent Metadata

Pagination
none
Idempotent
Unknown
Retry Guidance
Not documented

Known Gotchas

  • Not an MCP server — agents interact via embedded Go SDK or REST, not MCP protocol
  • JavaScript transformation components require embedded JS engine with associated overhead
  • Dynamic hot-reload of rule chains can cause in-flight message loss if not handled carefully
  • No built-in auth means deploying as a service requires additional security layers

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for RuleGo.

$99

Scores are editorial opinions as of 2026-03-06.

5178
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered