Skip to content
ivren
Docs navigation

The console

Ivren serves a local web console from the binary itself, bound to 127.0.0.1 only. It never binds a public interface and makes no external network requests.

Screens

  • Overview — a health summary of the whole estate.
  • Interfaces — every mapped interface, with a detail panel for source, destinations, protocol, and impact.
  • Live status — current state of anything Ivren is running.

Findings, not errors

When Ivren can’t fully process something — a malformed export, a truncated file — it surfaces a located finding rather than failing silently or aborting the whole import. A finding tells you exactly what and where; the rest of the import proceeds.

Credential stripping

Passwords found inside imported engine exports are stripped at import time and reported so they can be rotated. They never render in the console.

Explore with sample data

A one-click option loads bundled synthetic sample interfaces, so the whole product can be seen without supplying a file of your own.

Stay updated

Release notes, written for the person who reads diffs.

What shipped, what changed, and the occasional write-up on interface engineering. A handful of emails a year, no marketing cadence.

Release notes and interface engineering write-ups. No cadence, no selling.