JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Deployment case study

Local Laya vs Hosted Jev: Why My Agents Make Typed Decisions on My Mac

James Cruce documents a local Laya router on an M3 Ultra: its Jev-compatible service, eligibility gateway, frozen replay, latency regressions, and the reasons local control mattered more than an untested head-to-head claim.

Original by James CruceEvaluationAs The Geek LearnsOriginal published Source reviewed

Before you dive in

What you’ll find in the original

  1. Filter candidates deterministically for capability, health, data class, context, deadline, and memory before a model ranks them; then validate the returned option and eligibility again.
  2. Load Laya through its published runtime so the custom decision head is present, reject over-budget inputs instead of truncating them, and provide abstention plus a permitted fallback.
  3. Freeze thresholds on a development set before replaying held-out cases, and budget for host-load variance: the author's p95 rose from 143.54 ms to 466.69 ms with the same decisions.
Worth knowing

This is one deployment on an M3 Ultra. The author did not compare Laya and Jev on the same 40 cases; the reported 37/40 result is against a deterministic router, and the cases are correlated.