PLATFORM

What Ruddiment sees.

From the request at the edge to what executed and changed inside the application — and what happened next. One console, one evidence chain, one governed path to response.

EDGE

What reached the application.

Requests, sessions and origins as infrastructure sees them — the starting point of every chain, never the end of it.

EDGE → RUNTIME → CONSEQUENCE

One path, observed at three points. Evidence links them.

EDGE
RUNTIME
CONSEQUENCE
What reached the application
A request arrives. Infrastructure controls see it here — and stop here.
What executed and changed
Inside the application: the session, the component that ran, the file that changed, the identity that gained privilege.
What happened next
The connection that left, the data that moved, the state that persisted. Linked back to the request by evidence.

RUNTIME

What executed and changed.

The Runtime observes the application from inside: components and versions, files modified outside an update, privileged identities, heartbeat and connection state.

Ruddiment Runtime for WordPress admin page showing Connected, last heartbeat, last inventory reconciliation, runtime version, findings and contextual vulnerabilities, with an Open Ruddiment action.
Runtime for WordPress admin page over fixture data.

CONTEXT

Why it matters here.

Contextual risk is assessed from what the Runtime observes — present, active, recently changed, reachable — not from an advisory score alone.

Ruddiment console: Application Security Overview for app.example.com showing a high contextual risk card with evidence checklist, runtime, inventory, privileged identities, findings, vulnerabilities and activity.
The console as it is in development. Fixture data — RFC 2606 example domains, no customer data.

EVIDENCE

What was observed, where it came from.

Every finding is traceable to the events it was derived from. Observation → context → interpretation → decision, with unverified items shown as not observed.

Ruddiment investigation workspace: evidence path from edge to runtime to consequence with observed and not-observed stages.
Investigation evidence path over fixture data. Stages Ruddiment did not observe are shown as not observed.

INTELLIGENCE

Advisories matched against real inventory.

Security intelligence is only useful when it meets the application. Ruddiment matches advisories against the components and versions the Runtime actually reports, so a vulnerability is a fact about this application — not a headline.

Sources and coverage are described on the Research route as they are confirmed. No coverage figures are claimed.

GOVERNED RESPONSE

Proposed from evidence, reviewed by an operator.

Ruddiment is being designed so that responses stay explicit, scoped, auditable, reversible and operator-governed. The Developer Preview observes, assesses and proposes; it does not execute responses.

PROPOSED
from evidence
REVIEWED
by an operator
VERIFIED
by the Runtime
reversible · auditable at every step

DEVELOPER PREVIEW · WORDPRESS FIRST RUNTIME

See what your application is actually doing.

Ruddiment is being built with a small number of design partners. You will see the product as it is — no counters, no claims.

Early-access requests open with the first design partners. Until an intake route exists, this page does not pretend to have one.