The Console is where security engineers, platform teams, and compliance officers do their day-to-day work with RenLayer. It is a Next.js application that talks only to the Platform API, no direct database access, and exposes every governance primitive the proxy enforces.
What the console gives you
- Dashboard: at-a-glance health: trace counts, top agents, denied/flagged action counts, DLP findings.
- Sessions: drill into individual agent runs, request bodies, responses, latencies, and DLP findings.
- Agents: register agents, mint API keys, configure upstreams, set per-agent rate limits.
- Policies: author, version, and test the rules the proxy enforces inline.
- DLP: manage detectors, custom patterns, allow lists, and review findings over time.
- Audit log: immutable record of who did what in the console (created an agent, edited a policy, rotated a key).
Who logs in
The console supports two roles out of the box:
- Admin: full read/write across the tenant, including key rotation and policy edits.
- Member: read-only by default; write access can be granted per-resource.
Single sign-on (SAML / OIDC) integration is available; OTP-based login works in standalone deployments.
Multi-tenant from the ground up
The console is multi-tenant, with strict isolation enforced by the Platform API. Operators see only data for tenants they belong to. There is no global console, even the dashboard’s high-level numbers are tenant-scoped.
Layout
The shell follows a familiar dashboard pattern:
- Top bar with tenant switcher, search, and the user menu.
- Left sidebar with the eight primary sections (Dashboard, Agents, Policies, DLP, Sessions, Audit log, Settings, Docs).
- Main pane for content; deep-linkable URLs throughout.
Pages are designed for keyboard navigation; common actions have shortcuts.