Ujex Ingress — No-signup tunnels for AI agents
Ujex Ingress is the tunnel subsystem of Ujex. Three tiers; pick the right one for the job.
| Tier | Tech | URL | Use case |
|---|---|---|---|
| Quick | bore (embedded) | Random subdomain | 5-minute test, no setup |
| Standard | cloudflared | *.trycloudflare.com | Local dev, persistent |
| Stable | Your CF Tunnel | Your domain | Production agent endpoints |
Why three tiers
Quick is for "I just need a URL right now." Standard is for "I want it stable through my session." Stable is for "production endpoint on my domain." Same CLI, three flags.
CLI
ujex ingress run --expose 3000 # Quick
ujex ingress run --expose 3000 --standard # Standard
ujex ingress run --expose 3000 --stable hooks.myagent.dev # StableAuth via agent identity
Each Ujex agent has a device key with scopes. Inbound requests can be required to include a valid agent token; the relay rejects un-authed requests at the edge. Useful for agent-to-agent webhooks within an org.
Audit
Every request lands in the hash-chained audit log: timestamp, source IP, agent token (if any), bytes, response code.
Compared to alternatives
- Cloudflare Tunnel vs ngrok vs Ujex Ingress
- Hookdeck vs Ujex Ingress
- Seven ways to receive a webhook on a local agent
FAQ
Does this replace ngrok?
For agent-shaped use cases, yes. For pure local dev tunnels with rich event inspection, Hookdeck is better.
Can I use my own Cloudflare account?
Yes — Stable tier uses your CF Tunnel. Quick and Standard tiers use Ujex's relays.