Plurai vs Statewright

Plurai launched today as Product Hunt's #1 product with a deceptively simple pitch: describe how you want your AI agent to behave, and the platform automatically generates training data, validates it, and deploys a custom evaluation model — no labeled datasets, no annotation pipelines, no prompt engineering. They call it "vibe coding, but for evals and guardrails." Under the hood, Plurai builds on published BARRED methodology research, running small language models fine-tuned for your specific use case rather than calling GPT-4 for every eval check. This delivers sub-100ms latency at 8x lower cost than GPT-based evaluation approaches. The company claims a 43% reduction in agent failure rates across early customers, and the always-on monitoring goes beyond sampling to evaluate every single interaction. This hits a real and growing problem: as AI agents proliferate in production, the gap between "it works in the demo" and "it works reliably for real users" is where most teams are bleeding. Traditional eval approaches either require expensive human labeling or depend on another LLM to judge the first one — both brittle. Plurai's approach of training lightweight specialized models from natural language descriptions could be a genuine step change for teams that aren't ML experts.

Statewright takes a provocative stance on AI agent reliability: instead of making models smarter, restrict what they can do. The framework lets you define explicit state machines that determine which tools an agent can access at each phase of a workflow. During planning, agents get read-only tools. During implementation, edit tools unlock. During validation, only test commands are available. The philosophy is captured in a single line from the README: "Agents are suggestions, states are laws." The core engine is written in Rust for deterministic, zero-LLM evaluation of state transitions. Plugin layers integrate with agents via MCP (Model Context Protocol), enforcing tool restrictions at the protocol level across most major platforms. The framework is Apache 2.0 for its core engine, with FSL licensing for extended features (converting to Apache 2.0 in 2029, self-hosting allowed for developers and teams now). The team published SWE-bench results showing models jumping from 2/10 to 10/10 success rates on five tasks when Statewright constraints were applied—a striking claim that has the HN crowd both skeptical and intrigued. This is genuinely novel territory: rather than prompt engineering or fine-tuning, it's architectural guardrails enforced at runtime. For production agent deployments where agents interacting with dangerous tools (databases, file systems, APIs) need hard constraints, this fills a real gap. 53 stars so far, but the HN traction suggests it's about to pop.