Private beta · 30 days · 1 authorised WordPress site · No card required

PLATFORM

What Ruddimentsees.

Connect a WordPress website and see its software, recent changes and connection health in one place. Review findings against the available evidence. Edge intelligence and broader response are roadmap work.

Several polished metal rings resting on a dark surface, one lit from within in signal green.
  • What is installed and changed

    Components, versions and connection state, observed from inside the application.

  • Why it matters here

    Contextual risk assessed from what the Runtime observes, not an advisory score alone.

  • Where it came from

    Every finding traceable to the events it was derived from.

RUNTIME

What is installedand changed.

The Runtime observes the application from inside: components and versions, 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.
Actual Ruddiment Packages view: four plugins and three themes reported by the disposable WordPress Runtime, with versions and active states.
Actual accepted staging inventory, captured 30 September 2026. Disposable WordPress site; no customer data. The preserved demo uses Runtime 0.1.2-v0. This is a dated screenshot, not a live security assurance.

CONTEXT

Why it matters here.

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

EVIDENCE

What was observed,where it came from.

Every finding is traceable to the events it was derived from. Observation, context, interpretation and decision are kept distinct, 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 possible match can be reviewed in context. A match alone is not proof of exploitation.

  • Matched to the application

    Advisories are compared with the components and versions the Runtime reports for this website.

  • Assessed in context

    A match is weighted by whether the component is present, active and recently changed.

  • Shown with evidence

    Each finding links back to the observations it was derived from.

The current demo uses a controlled advisory source to demonstrate matching. It is not comprehensive vulnerability coverage. No findings does not mean a website is secure.

GOVERNED RESPONSE

Proposed from evidence,reviewed by an operator.

Ruddiment is being designed so that responses stay explicit, scoped, auditable, reversible and operator-governed. Managed plugin updates have bounded local test evidence but are disabled in the hosted beta. Future execution requires explicit human approval. Automatic remediation and Protection are not available.

EDGE

What reached the application.

Edge context is part of Ruddiment’s long-term direction. The current private alpha begins with WordPress Runtime inventory, connection state and application changes.

30 DAYS. A CLEARER PICTURE.

Start with oneWordPress website.

Arrange founder-assisted access, complete account security and connect one authorised WordPress website.