Vengtoo Agent
Authorization decisions in under 5ms. On your infrastructure.
The Vengtoo Agent runs next to your app, pulls your policies from the cloud and evaluates every authorization request in-memory. No network round-trip, no latency tax.
Under 5ms p95
Policy evaluation happens in-memory, locally. No round-trip to the cloud on the hot path.
Data stays local
Decision inputs — subjects, resources, context — never leave your network. Evaluated entirely on your infrastructure.
Graceful degradation
The agent caches your policy bundle to disk. If the cloud is unreachable, it keeps serving decisions from the last known-good bundle.
Deploy
One container. No code changes.
Add the agent to your Docker Compose or Kubernetes deployment. Point your SDK at localhost:8181 instead of the cloud. That's it — the evaluation API is identical.
- ✓Binary, Docker, or Go install
- ✓Prometheus metrics at /metrics
- ✓Health and readiness probes at /healthz and /readyz
- ✓Audit log forwarding to cloud (configurable)
services:
vengtoo-agent:
image: vengtoo/agent:latest
environment:
VENGTOO_API_KEY: ${VENGTOO_API_KEY}
VENGTOO_CACHE_DIR: /var/lib/vengtoo/bundles
volumes:
- vengtoo-cache:/var/lib/vengtoo/bundles
ports:
- "8181:8181"
volumes:
vengtoo-cache:// Go
client := vengtoo.NewClient("",
vengtoo.WithBaseURL("http://localhost:8181"))
// Node.js
const vengtoo = new Vengtoo({ baseUrl: 'http://localhost:8181' })
// Python
client = Vengtoo(base_url="http://localhost:8181")SDKs
Switch to the agent in one line.
All SDKs accept a baseUrl override. Change it to point at the agent and every evaluation call routes locally — no other code changes required.
What runs locally
Most features evaluate fully in-memory on the agent. A small number require live cloud state.
| Feature | Local agent | Cloud endpoint |
|---|---|---|
| RBAC / ABAC / direct grants | ✓ | ✓ |
| Policy modifiers (time window, IP allowlist) | ✓ | ✓ |
| Agent-to-agent delegation | — | ✓ |
| Human-in-the-loop approval | — | ✓ |
| Rate limiting | — | ✓ |