How is this different from existing agent-side guards?

It judges inbound requests at the gateway before they reach the backend, while machine-side guards judge what an agent is about to do; the audiences and positions differ.

What happens when the judging API is slow or down?

Traffic flows and a log line fires, with a circuit breaker avoiding per-request timeout waits while the judging API is unhealthy.

Which thresholds are safe to ship with on day one?

None is bundled: label a few hundred requests from monitor-mode logs and set block and suspect cutoffs from that data, since accuracy hinges on the deployment description.

What setup catches should I expect installing the gateway module?

OpenResty with the HTTP library plus a CA bundle for provider TLS, a key for live judging, and shared dicts for cache, state, config, and metrics.

Where can jev-edge actually run?

In OpenResty, Apache APISIX or Kong natively, behind Envoy, Istio, HAProxy, Traefik, Caddy and nginx through /_jev/authz, in Cloudflare Workers, Next.js, Node, Hono, Lambda@Edge and Deno Deploy through @jev-edge/js, or inside LiteLLM proxy.

How do I install jev-edge?

With luarocks install lua-resty-jev-edge, opm get kiwi0719/lua-resty-jev-edge, or from source with make install. It needs OpenResty 1.21+ and lua-resty-http 0.17+.

What is the L1, L2, L3 split?

L1 cheap rules add about 20 microseconds and pass most traffic, L2 is a synchronous Jev judgment at about 270-300 ms p50 with an adaptive 400-1000 ms timeout, and L3 is an async side-path that never blocks the response.

CommunityJev Integrations & Adapters

Jev Edge

Gateway-side admission control judging incoming requests with a typed decision model, layering cheap rules, synchronous judgment, and an async side path that never blocks responses.

See highlights

Open github.com

Stars: 41
Language: Lua
License: APACHE-2.0
Published by: Community
Author: kiwi0719
Last verified: Oct 2026

kiwi0719/jev-edge

User repository on GitHub

View on GitHub

Typed-judgment admission control at the traffic edge: three-layer prompt-injection and abuse filter for nginx/OpenResty, powered by TypeSafe Jev. Fail-open, cached, hot-reloadable.

Forks: 1
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

Typed-judgment admission control at the traffic edge.

Quoted from the project's README. Read the full README.

Tagscommunity jevbest catalog-import awesomejev lua

Works forJev for Classification Jev for Moderation

Used inJev for Software & DevTools

Highlights

Three cost-ordered filters mean most traffic never pays for model judgment.
Fail-open behavior plus verdict caching keeps the gateway responsive under load.
Verdict and score headers reach the upstream so apps can make a second decision.
Judge backend is pluggable across the hosted model, self-hosted models, and a mock.

Watch out

No production use is known yet, so start in monitor mode and choose thresholds from your own traffic logs rather than defaults. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

system-one

Provider-neutral TypeScript runtime for System One decisions: write choice, noul, and score code once, then run it on TypeSafe Jev, local Reflex, any compatible /v1/systemone endpoint, or a custom provider.